What is Google Additional Consent?

Google Additional Consent (AC) is a specification that lets cookie banners signal consent to Google Ad Tech Providers (ATPs): advertising technology companies that work with Google but aren’t registered on the IAB Global Vendor List (GVL).

The IAB Transparency and Consent Framework (TCF) is the industry standard for consent signaling in digital advertising. It maintains the GVL, a list of registered ad tech vendors. When your cookie banner collects consent, it communicates those choices to vendors on that list. Google Additional Consent extends that signaling to cover Google’s ATPs, which operate outside the GVL.

Without Google Additional Consent, consent signals wouldn’t reach those providers at all.

Google Additional Consent v1 and v2: what’s the difference?

Google Additional Consent has two versions: v1 and v2. Both signal consent to Google ATPs, but they differ in format and capabilities.

ACv2 updates the format used to signal consent and adds the ability to declare disclosed vendors. It aligns with more recent TCF implementations and Google’s current requirements.

Which version of Google Additional Consent should I use?

Use v2. It’s the current standard and keeps your setup compatible with Google’s advertising ecosystem going forward.

iubenda sets gacVersion to 2 by default. If you haven’t explicitly set a version in your configuration, your setup already uses v2. If you have gacVersion: 1 in your configuration, we recommend switching to 2.

When should I stay on Google Additional Consent v1?

In most cases you won’t need to. But if your setup includes a legacy integration built around the v1 AC string, internal scripts that expect the v1 format, or a complex ad stack where changes need careful testing, you may want to stay on v1 temporarily while you prepare for the switch.

How to configure Google Additional Consent

Using the Privacy Controls and Cookie Solution Configurator

Enable Google Additional Consent from the Privacy Controls and Cookie Solution Configurator, under the IAB TCF settings. To configure the version (v1 or v2), use the configuration script below.

Using the configuration script

To configure Google Additional Consent manually, add both googleAdditionalConsentMode and gacVersion to your _iub.csConfiguration object, before the iubenda Privacy Controls and Cookie Solution script.

googleAdditionalConsentMode: true enables Google Additional Consent. gacVersion sets the version (1 or 2).

To enable Google Additional Consent with v2 (recommended):

<script>
window._iub = window._iub || {};
_iub.csConfiguration = {
googleAdditionalConsentMode: true,
gacVersion: 2
};
</script>

To enable Google Additional Consent and keep v1:

<script>
window._iub = window._iub || {};
_iub.csConfiguration = {
googleAdditionalConsentMode: true,
gacVersion: 1
};
</script>

If you’re using the unified embed code, add this block immediately before the main iubenda script tag.

Need help?

Reach out to us via support if you need any further assistance.

The post Google Additional Consent: what it is and how to configure it appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

We’ve compiled the latest in Data Protection and Privacy news for your convenience below.

1) Newly Published Documentation

France – CNIL Publishes Guidance on Analyzing AI Models Under GDPR
France’s CNIL published guidance helping AI providers assess whether their models store personal data from training and are subject to GDPR, building on the EDPB’s opinion on AI development.

Denmark – Datatilsynet Announces 2026 Supervisory Focus on AI Monitoring Technologies
Denmark’s Data Protection Authority published 2026 priorities focusing on AI monitoring in care settings, patient devices, employee tracking, and website tracking, signaling heightened healthcare and workplace scrutiny (Danish).

European Union – European Commission Publishes DMA Review Consultation Summary with 450+ Responses
The European Commission published all contributions from its Digital Markets Act review consultation, with stakeholders supporting DMA objectives while calling for expanded AI and cloud scope. The review report is due May 3, 2026.

2) Notable Case Law

European Union – EU Commission Orders X to Preserve All Grok Documents Until End of 2026
The European Commission instructed X to retain all Grok-related records through December 31, 2026, as it examines Digital Services Act compliance following criticism over AI-generated harmful imagery.

United Kingdom – UK Prime Minister Starmer Seeks International Coalition Against X Over AI-Generated Abuse Images
UK Prime Minister Starmer is building an international “coalition of decency” after X’s Grok enabled non-consensual imagery creation, with the government supporting potential enforcement action under the Online Safety Act.

3) New and Upcoming Legislation

European Union – European Parliament Confirms Digital Omnibus as 2026 Priority with Potential AI Act Timeline Delays
The European Parliamentary Research Service confirmed the AI Act will fully apply from August 2, 2026, but the proposed Digital Omnibus could delay certain high-risk system deadlines to late 2027 and 2028.

Netherlands – Ministry Delays Cybersecurity Act Entry Into Force to Q2 2026
The Dutch Ministry confirmed NIS2 Directive transposition into the national Cybersecurity Act is delayed until Q2 2026, with the existing Security of Networks and Information Systems Act remaining in effect.

4) Strong Impact Tech

USA – Meta Strikes Nuclear Power Agreements Worth 6.6 GW to Support AI Infrastructure
Meta announced agreements with Vistra, TerraPower, and Oklo to secure up to 6.6 gigawatts of nuclear capacity by 2035, including 20-year deals and funding for eight new advanced reactors.

European Union – EU Antitrust Regulators Set February 10 Deadline for Google’s $32 Billion Wiz Acquisition
EU antitrust regulators will decide by February 10, 2026, whether to approve Alphabet’s $32 billion Wiz acquisition, Google’s largest deal ever, or open a full investigation.

France – Macron Calls for Deepening EU’s Digital Rules in Face of US Pushback
French President Macron urged Europe to defend its Digital Services Act and Digital Markets Act, emphasizing European digital sovereignty as Washington criticized EU tech regulations.

Other key information from the past weeks

Brazil – ANPD Extends Digital ECA Compliance Deadline to February 13
Brazil’s ANPD extended the deadline for 37 tech companies to submit compliance information on the Digital Child and Adolescent Statute, including Amazon, Apple, and Google Brazil (Portuguese).

New Zealand – Privacy Commissioner Confirms Manage My Health Cyber Breach Notification
New Zealand’s Privacy Commissioner confirmed Manage My Health reported a ransomware incident on January 1, 2026, affecting thousands of users’ sensitive health information including discharge summaries and referral letters.

About us

Attorney-level solutions to make your websites and apps compliant with the law across multiple countries and legislations.

www.iubenda.com

The post DPO Newsletter: Global Data Protection & Privacy News (issue #151) appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Google-certified cmp for consent mode

Activate Google Consent Mode. Recover lost data and get up to 18% more conversions.

Cookies rejected. Data gone. Budget wasted. Turn it around with Google Consent Mode. Activate it in minutes with our Google-certified CMP, recover lost conversion data, boost your conversions, and make your campaigns work harder.

Set up Consent Mode Is it active? Check now

Available for all plans, including the Free one!

Google Ads

Google Analytics

GDPR-Ready

Get up to 18% more conversions when you implement Google Consent Mode

A Google Case study shows that businesses using Consent Mode can see up to 18% more conversions. How? Consent Mode, activated with a Google CMP partner like iubenda, uses machine learning to model missing data from users who say no to tracking. That means your analytics stay useful, your campaigns stay optimized, and your revenue doesn’t nosedive. So while your competitors are flying blind, you’re still making smart, data-backed decisions, all without breaching privacy laws.

iubenda is a Google-certified Consent Management Platform that helps you implement and verify Consent Mode effortlessly – whether you’re starting from scratch or optimizing an existing setup.

Get Google Consent Mode in three easy steps

Navigating the maze of international regulations and service provider guidelines is challenging. iubenda makes it simple with powerful features. Focus on your business, confident that your compliance is handled by the best.

STEP 1

Configure your consent banner

Answer a few simple questions, and go with iubenda’s automatic configuration or totally customize banner and consent collection.

STEP 2

Install it on your site

Copy and paste the provided code into your website, implement our Google Tag Manager template, or choose from one of our dedicated plugins. Everything else is automatic, including Google Consent Mode setup.

STEP 3

Model data from non-consented users

Enjoy improved marketing data since Google Consent Mode is built into your iubenda CMP. Google’s advanced algorithms allow you to see conversions and analytics even for users that don’t give you tracking consent, and iubenda helps you get it done with zero effort.

Since you’re using Google services now, don’t forget to add the required clauses and disclosures in your privacy policy, such as Google Analytics 4 and Google Ads conversion tracking.

Already activated Consent Mode?

Make sure it’s up and running with our free scanner

iubenda with Google Consent Mode inside

Geolocation Savvy

Intelligently adapt with geolocation support to improve compliance and personalization right from the start. Understanding your audience, no matter where they’re Browse from.

Flexible Consent Handling

Choose Basic Consent Mode to turn off Google tags until you get user consent or activate Advanced Consent Mode for a smoother experience that preloads Google tags but respects user choices, using cookieless pings if consent is declined.

Missing Cookies? No Problem.

When users say no to cookies, cookieless pings can step in and keep the data flowing. This feature ignores users’ personal details but makes Google’s conversion models even more accurate.

Instantly Adaptable

Get better insight into user behavior in real time. Our tools constantly monitor your users’ consent preferences, and Google Consent Mode adapts to keep you informed.

Beyond the Ads and Analytics

Our Google-certified CMP isn’t just a tool; it’s a global compliance partner. With iubenda, you’ll up your Google Ads game while we help cover all your compliance bases in record time and without the hassle.

Click, Copy, Collect More Data

Set up is a breeze thanks to our integration with Google Tag Manager. Simply apply our GTM template and put any concerns about Google Consent Mode to rest. We also offer options for CMS plugins and direct site code integration.

Available for all plans, including the Free one!

Choose the easy way to get Google Consent Mode

Set up Consent Mode

Victor, N.

CEO

“iubenda stays on top of the laws around the world, so they adjust and add more stuff to help users comply with new laws.”

The post +18% conv w/ CoMo appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Overview

All new apps submitted to the App Store must comply with Apple’s App Tracking Transparency (ATT) guidelines for iOS 14.0+. These guidelines enhance user privacy by requiring explicit consent before tracking. This document outlines the necessary steps to implement ATT when using our CMP SDK.

According to Apple’s official documentation:

Calls to the API only prompt when the application state is UIApplicationStateActive

1. Add the ATT Framework in Xcode

To integrate AppTrackingTransparency.framework, navigate to:

<PROJECT_NAME>.xcproject / <PROJECT_NAME>.xcworkspace -> General -> Frameworks, Libraries, and Embedded Content.

Ensure the framework is correctly embedded to enable ATT functionality.

2. Add NSUserTrackingUsageDescription

Include the following key in your Info.plist file:

<key>NSUserTrackingUsageDescription</key>
<string>Your app description explaining why tracking permission is requested.</string>

This message will be displayed to users in the ATT consent prompt.
3. Request Tracking Authorization

To ensure proper consent handling, request ATT permission on the first app launch. This should only occur if the user’s consent status is unknown.

import AppTrackingTransparency

class AppDelegate: UIApplicationDelegate {
    // IMPORTANT: this is the proper lifecycle event where the request needs to be done
    func applicationDidBecomeActive(_ application: UIApplication) {
        if #available(iOS 14, *) {
            ATTrackingManager.requestTrackingAuthorization { status in
                switch status {
                    case .authorized:
                        print("Tracking enabled")
                    case .denied, .notDetermined, .restricted:
                        print("Tracking disabled")
                }
            }
        }
    }
}

Note: Ensure UI-related logic is executed on the DispatchQueue.main queue, as the completion handler runs on a concurrent queue by default.
4. Monitor Tracking Authorization Status

Use ATTrackingManager.trackingAuthorizationStatus to track consent status changes. The following states are possible:

• .authorized – User granted consent.
• .denied – User denied tracking permission.
• .notDetermined – User has not made a choice yet.
• .restricted – Tracking is restricted (e.g., via MDM).

For consistency, treat restricted as denied unless explicit vendor consent is provided.

5. Handle Consent in Analytics & Third-Party SDKs

If your app uses third-party analytics, update their configuration based on the user’s ATT status:

• Disable analytics tracking for users who deny or restrict tracking.
• Use anonymized tracking if the analytics provider offers an opt-out setting (e.g., mParticle’s optOut mode).
• Review SDK policies regularly to stay compliant with Apple’s privacy requirements.

Example for Firebase:

• If no ad frameworks are linked, Firebase Analytics will not access the advertising identifier.
• If using analytics with ads, ensure compliance with ATT guidelines before submission.

For apps that do not require advanced analytics, App Store Analytics (accessible via App Store Connect) may provide sufficient insights while ensuring compliance.

6. Additional Considerations

• Wrap ATT calls in an iOS version check to avoid crashes on older versions

if #available(iOS 14.0, *) {
    ATTrackingManager.requestTrackingAuthorization { _ in }
}

• Track consent for older iOS versions using backend flags or local storage.
• Comply with ATT promptly, as non-compliance may block app updates, even in cases of critical bug fixes.
• For more information on managing user consent within the app, refer to Apple’s ATT documentation.

The post iubenda SDK v3.5 – IOS – App Tracking Transparency (ATT) appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

The CMPManager class provides methods to manage user consent for data processing and tracking. This documentation covers the main methods available for mobile app integration.

Initialization

UrlConfig()

Sets the URL configuration for the iubenda SDK. Needs to be initialized with the value below, and passed to the getInstance method. 

Parameters:

• id: String – Your site-specific configuration retrieved on the embedding section of your Privacy Controls and Cookie Solution embedding section
• domain: String – The domain for iubenda CDN
• language: String – The language code (e.g., “EN”, “IT”, “DE”, etc)
• appName: String – The name of your app, used only for reporting purposes
• jsonConfig: JSON String – Optional, can be useful to inject a local configuration direcl inside the mobile SDK 

Example:

CMPManager.shared.setUrlConfig(UrlConfig(
    id: "0a000000000a1",	// The Code-ID retrieved from your CMP dashboard
    domain: "cdn.iubenda.com",  // The domain retrieved from your CMP dashboard
    language: "EN",		// Language code, examples: IT, DE, EN, etc. 
    appName: "MyApp"		// The name of your app, used for reporting purposes on your CMP dashboard
))

setWebViewConfig()

Configures the appearance and behavior of the consent WebView. You can set the position where the WKWebiew object displaying the consent layer will appear, like full screen, on the lower half of the screen or its upper half. Also, the background style can be applied, as well as the corner radius, whether it will respect the safe area of the device, as well as whether it will respond to orientation changes or not, in case your mobile works only in one single orientation, which usually happens with games that only use the horizontal configuration of the device’s screen.   

Parameters:

• config: A ConsentLayerUIConfig object with the following properties:
• position: Position – The position of the WebView (e.g., .fullScreen)
• backgroundStyle: BackgroundStyle – The background style (e.g., .dimmed)
• cornerRadius: CGFloat – The corner radius of the WebView
• respectsSafeArea: Bool – Whether to respect the safe area
• allowsOrientationChanges: Bool – Whether to allow orientation changes

Returns: Void

Example:

CMPManager.shared.setWebViewConfig(ConsentLayerUIConfig(
    position: .fullScreen,
    backgroundStyle: .dimmed(.black, 0.5),
    cornerRadius: 10,
    respectsSafeArea: true,
    allowsOrientationChanges: true
))

setPresentingViewController()

Sets the view controller that will present the consent layer. Usually you pass self as the current View Controller. 

Parameters:

• viewController: UIViewController – The view controller to present the consent layer

Returns: Void

Example:

CMPManager.shared.setPresentingViewController(self)

Consent Layer Management

getUserStatus()

Returns a detailed snapshot of the user’s current consent status and preferences. This method provides comprehensive information about the user’s consent choices, including their overall consent status, individual vendor permissions, purpose-specific consents, and relevant consent strings.

Parameters:

• None

Returns:

Return Type: CMPUserStatusResponse object, explained in the code below. 

Example:

let status = CMPManager.shared.getUserStatus()
var message = "Status: \(status.status)\n\n"

message += "\nPurposes:\n"
for (purposeId, state) in status.purposes {
    message += "- \(purposeId): \(state)\n"
}

message += "\nTCF: \(status.tcf)\n"
message += "Additional Consent: \(status.addtlConsent)\n"
message += "Regulation: \(status.regulation)"

print(message)

checkAndOpen()

Checks with the server if consent is required and opens the consent layer if necessary. This will make a network call to our servers via the WKWebView created inside our SDK, consuming one pageview in the process. This network call will send a message to our backend via JavaScript, which will detect whether the device has a valid consent or not, which will in turn determine whether the consent layer needs to be displayed or not.  

Parameters:

• jumpToSettings: A boolean value to determine whether the consent layer displayed will automatically lead to the page where a more granular control over the consents given by the users, allowing them to fine tune their choices (when set to true) or the initial default screen with the buttons (when set to false or suppressed).
• completion: A closure called when the operation completes.

Returns: Void

Example:

CMPManager.shared.checkAndOpen { error in
    if let error = error {
        print("Error: \(error.localizedDescription)")
    } else {
        print("Check completed successfully")
    }
}

forceOpen()

Opens the consent layer. It makes a network call to our backend, consuming one pageview in the process. It will display the consent layer allowing the user to either Accept All or Reject All of the choices, or, depending on the jumpToSettings parameter, allow them to control the consents in a more granular way. 

Parameters:

• jumpToSettings: A boolean value to determine whether the consent layer displayed will automatically lead to the page where a more granular control over the consents given by the users, allowing them to fine tune their choices (when set to true) or the initial default screen with the buttons (when set to false or suppressed).
• completion: A closure called when the operation completes, returning either a sucess or an error.

Returns: Void

Example:

CMPManager.shared.forceOpen { error in
    if let error = error {
        print("Error: \(error.localizedDescription)")
    } else {
        print("Consent layer opened successfully")
    }
}

Consent Status

exportCMPInfo()

Exports the current consent information stored on the device as a string. This method retrieves the consent string from the UserDefaults area of the device and returns it. Usually this information is passed to the importCMPInfo method.

Returns: String – The exported consent information

Example:

let cmpInfo = CMPManager.shared.exportCMPInfo()
print("Exported CMP info: \(cmpInfo)")

getGoogleConsentModeStatus()

Seamlessly integrates with Consent Mode, a Google technology that enables conversion and analytics modeling, allowing Google’s services to fill in data gaps when users do not consent. This function translates the user’s consent from your CMP into a format that Firebase Analytics can understand, so you can simply get the return of this method and pass it along to Firebase .setConsent method.

• It then updates Google Analytics with the user’s current consent status.

Parameters:

• None

Returns: [String: String] – An key value array with the four Google Consent Mode keys: .analyticsStorage, .adStorage, .adUserData and .adPersonalization, and their respective values in terms of .choiceDoesntExist, .granted or .denied.

Example:

showToast(message: "Google Consent Mode Status: \n \(CMPManager.shared.getGoogleConsentModeStatus())")

getStatusForPurpose()

Checks if consent has been given for a specific purpose and this consent is stored on the device. It checks the UserDefaults area for the consents accepted or rejected, and filter the ID passed as a parameter, returning true if the consent was accepted or false otherwise. 

Parameters:

• id: String – The ID of the purpose to check

Returns: UniqueConsentStatus – An enum with the values .choiceDoesntExist if no consent was given, .granted or .denied.

Example:

let purposeStatus = CMPManager.shared.getStatusForPurpose(id: "c53")
var message = "Purpose c53 status: "
switch purposeStatus {
   	case .choiceDoesntExist: message += "No Choice"
    case .granted: message += "Granted"
    case .denied: message += "Denied"
    @unknown default: message += "No Choice"
}

Consent Modification

acceptAll()

Accepts consent for all purposes and vendors, consuming one pageview in the process. It makes a network call to our backend via a message injected on the WKWebView, which will trigger the acceptance of all the consents, according to the CMP configuration. This information will only be available to the other methods after the callback returns a success or failure, which means it was succesfully processed by our backend and persisted on the device. 

Parameters:

• completion: A closure called when the operation completes

Returns: Void

Example:

CMPManager.shared.acceptAll { error in
    if let error = error {
        print("Error: \(error.localizedDescription)")
    } else {
        print("All consents accepted successfully")
    }
}

acceptPurposes()

Accepts consent for specified purposes, consuming one pageview in the process. It makes a network call to our backend via a message injected on the WKWebView, which will trigger the acceptance of the determined purposes passed as a parameter, according to the CMP configuration. This information will only be available to the other methods after the callback returns a success or failure, which means it was succesfully processed by our backend and persisted on the device. 

Parameters:

• purposes: [String] – An array of purpose IDs to accept
• updatePurpose: Bool – Whether to update related purposes
• completion: A closure called when the operation completes

Returns: Void

Example:

CMPManager.shared.acceptPurposes(["2", "3"], updatePurpose: true) { error in
    if let error = error {
        print("Error: \(error.localizedDescription)")
    } else {
        print("Purposes accepted successfully")
    }
}

importCMPInfo()

Imports consent information from a CMP string. This will receive a string containing the consent data, usually obtained through the exportCMPInfo method. This information is persisted in the UserDefaults area of the device, and at the same time is sent to our backend via a message injected in the WKWebView, consuming one pageview in the process. 

Parameters:

• cmpString: String – The CMP string to import
• completion: A closure called when the operation completes

Returns: Void

Example:

let cmpString = "Q1FERkg3QVFERkg3QUFmR01CSVRCQkVnQUFBQUFBQUFBQWlnQUFBQUFBQUEjXzUxXzUyXzUzXzU0XzU1XzU2XyNfczI3ODlfczI3OTBfczI3OTFfczI2OTdfczk3MV9VXyMxLS0tIw"
CMPManager.shared.importCMPInfo(cmpString) { error in
    if let error = error {
        print("Error: \(error.localizedDescription)")
    } else {
        print("CMP info imported successfully")
    }
}

rejectAll()

Rejects consent for all purposes and vendors, consuming one pageview in the process. It makes a network call to our backend via a message injected on the WKWebView, which will trigger the rejection of all the consents, according to the CMP configuration. This information will only be available to the other methods after the callback returns a success or failure, which means it was succesfully processed by our backend and persisted on the device. 

Parameters:

• completion: A closure called when the operation completes

Returns: Void

Example:

CMPManager.shared.rejectAll { error in
    if let error = error {
        print("Error: \(error.localizedDescription)")
    } else {
        print("All consents rejected successfully")
    }
}

rejectPurposes()

Rejects consent for specified purposes, consuming one pageview in the process. It makes a network call to our backend via a message injected on the WKWebView, which will trigger the rejection of the determined purposes passed as a parameter, according to the CMP configuration. This information will only be available to the other methods after the callback returns a success or failure, which means it was succesfully processed by our backend and persisted on the device. 

Parameters:

• purposes: [String] – An array of purpose IDs to reject
• updateVendor: Bool – Whether to update related vendors
• completion: A closure called when the operation completes

Returns: Void

Example:

CMPManager.shared.rejectPurposes(["2", "3"], updateVendor: true) { error in
    if let error = error {
        print("Error: \(error.localizedDescription)")
    } else {
        print("Purposes rejected successfully")
    }
}

resetConsentManagementData()

Resets all consent management data. This completely erases al the UserDefaults area entries related to consents accepted or rejected by the user. It is similar to completely removing the app from the device. 

Parameters:

• completion: A closure called when the operation completes

Returns: Void

Example:

CMPManager.shared.resetConsentManagementData { error in
    if let error = error {
        print("Error: \(error.localizedDescription)")
    } else {
        print("Consent management data reset successfully")
    }
}

Passing consent data to third-party SDKs

updateThirdPartyConsent

This method handles the automatic passing of consent data to third-party SDKs like AppsFlyer, AdJust, Branch, Kochava, Singular, AirBridge and Tenjin. It works via introspection/reflection, so initialize the third-party SDK with your credentials using the usual strategy recommended by the provider, and our CMP SDK will detect the instance of the 3P SDK and invoke the needed methods under the hood. 

CMPManagerDelegate events

getOnClickLinkCallback

The SDK provides a flexible link handling mechanism that allows applications to customize how URLs within the consent layer are handled. By default, all links open within the WebView, but applications can intercept specific URLs to handle them externally when needed.

// Example 1: Handle specific domains in external browser
cmpManager.setLinkClickHandler { url in
    // Handle links to specific domains externally
    if url.host?.contains("google.com") == true || 
       url.host?.contains("facebook.com") == true {
        UIApplication.shared.open(url, options: [:], completionHandler: nil)
        return true // URL handled externally
    }
    
    // Let other URLs load in the WebView
    return false
}

// Example 2: Handle URLs based on scheme
cmpManager.setLinkClickHandler { url in
    // Open mail links in mail app
    if url.scheme == "mailto" {
        UIApplication.shared.open(url, options: [:], completionHandler: nil)
        return true
    }
    
    // Open tel links in phone app
    if url.scheme == "tel" {
        UIApplication.shared.open(url, options: [:], completionHandler: nil)
        return true
    }
    
    // Let all other URLs load in the WebView
    return false
}

didReceiveConsent(consent: String, jsonObject: [String: Any])

This is triggered when the consent layer was closed after the user updating his/her consents OR when invoking methods that cause changes in the consents, like acceptAll, rejectAll, acceptVendors, rejectVendors, etc. It means that the user accepted of rejected some of all of the consents, and that those were correctly saved in the device.

didShowConsentLayer

This is triggered when the consent layer was actually displayed. It means that there was not a consent valid in the device, so a new one should be collected.

didCloseConsentLayer

This is triggered when the SDK checked the need for a consent, but it was not needed and the layer was not displayed. It means that there is already a valid in the device, so a new one is not necessary and tue consent layer will not be displayed.

didReceiveError

This is triggered when the SDK faced any error, returning its code.

The post iubenda SDK v3.5 – IOS – API documentation appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Installation

iubenda SDK is a comprehensive solution for managing user consent in mobile applications. Designed to handle GDPR compliance, user privacy preferences, and ad tracking transparency, this SDK provides a seamless integration for iOS and Android platforms.

Steps – High Level Description

1. Integration and Configuration:
   • Integrate the SDK into your app.
   • Configure the SDK settings according to your needs.
2. Creating an Instance and displaying the Consent Layer:
   • On app startup, create an instance of the CMPManager class. This instance will handle the consent process.
   • The SDK will automatically display the consent screen if needed.
3. Processing user’s consent data:
   • Once consents are collected, info is stored and is available for querying through different properties and methods exposed by our SDK. You’ll have information about rejected or accepted consents, vendors and purposes.

1.1 Integration and Configuration

Option 1: CocoaPods

Add the following line to your Podfile:

pod 'cm-sdk-ios-v3', '3.5.0'

Then run:

pod install --repo-update

Option 2: Swift Package Manager

1. Download the latest XCFramework from our GitHub releases page.
2. On XCode, go to the menu File >  Add Package Dependency.
3. Add the SDK Repository URL above
4. SPM will now fetch the repository and ask you to select a version.
   You can choose to add the package by selecting a version rule:
   – Up to Next Major: This will update the package up to the next major version. It is the recommended option as it adds updates which do not have breaking changes.
   – Up to Next Minor: This will update the package up to the next minor version.
   – Exact: This will lock the package to a specific version. No updates will be installed.
5. Import the SDK by inserting in the top of the classes implementing the SDK’s methods the line below:

import cm_sdk_ios_v3

In your target’s settings, go to “General” > “Frameworks, Libraries, and Embedded Content” and ensure the framework is set to “Embed & Sign”.

1.2 Creating an instance and displaying consent layer

In your app’s viewDidLoad, follow these steps to set up the CMP SDK:

1. Create a CMPManager instance using the getInstance method.
2. Define two configuration objects:
   • UrlConfig: Contains settings like your iubenda embedding code and the language of the banner.
   • ConsentLayerUIConfig: Defines the appearance of the consent screen shown in a WKWebView.
3. Set the current ViewController by calling setPresentingViewController.
4. Call checkAndOpen()
   • This checks with the server to decide if the consent screen should appear.
   • If needed, the SDK automatically shows the consent layer inside a WKWebView, using your configurations.
   • The SDK then collects and saves consent info to NSUserDefaults, enabling targeted ads as appropriate.Assign the delegate to handle CMP events

import cm_sdk_ios_v3

class YourViewController: UIViewController, CMPManagerDelegate {
	override func viewDidLoad() {
	super.viewDidLoad()

	let cmpManager = CMPManager.shared

    cmpManager.setUrlConfig(UrlConfig(
    id: "your_id_here",                   	// example: a000aaaaa1a 
    domain: "cdn.iubenda.com",				// usually, cdn.iubenda.com 
    language: "your_language_here",			// example: IT
    appName: "Your App Name"))				// example: testApp

    cmpManager.setWebViewConfig(ConsentLayerUIConfig(
    position: .fullScreen,
    backgroundStyle: .dimmed(.black, 0.5),
    cornerRadius: 5,
    respectsSafeArea: true,
    allowsOrientationChanges: true))

    cmpManager.setPresentingViewController(self)
    cmpManager.delegate = self

    cmpManager.checkAndOpen { error in
        if let error = error {
            print("Error initializing consent: \(error)")
        } else {
            print("ConsentManager initialized and consent received and stored on the device's NSUserDefaults.")
        }
    }
}

1.3 Processing users’ consent data

Checking users’s consents

Our SDK offer a unified method to check and retrieve consent information, getUserStatus():

let status = CMPManager.shared.getUserStatus()
var message = "Status: \(status.status)\n\n"

message += "Vendors:\n"
for (vendorId, state) in status.vendors {
    message += "- \(vendorId): \(state)\n"
}

message += "\nPurposes:\n"
for (purposeId, state) in status.purposes {
    message += "- \(purposeId): \(state)\n"
}

message += "\nTCF: \(status.tcf)\n"
message += "Additional Consent: \(status.addtlConsent)\n"
message += "Regulation: \(status.regulation)"

print(message)

For further information about the other methods, please refer to our full API Documentation. 

Reopening the Consent Layer to check the users’ choices

In order to allow the user to verify or change their choices, you can simply call forceOpen()

cmpManager.forceOpen()

Importing/Exporting consent information to other sources

In some cases an native app might contain webviews in order to display information, like advertising or content. In order to transmit the consent information from the SDK to the webview, you can retrieve the consent string using:

consentData = cmpManager.exportCMPInfo()

This will export the consent information and all further data that is needed by the CMP. You can then pass this information to the CMP that is in your webview by adding it to the URL that is called in the webview.

If, otherwise, you need to import the consent string using the SDK, you can use the example below:

let consentStringToImport = "Q1FERkg3QVFERkg3QUFmR01CSVRCQkVnQUFBQUFBQUFBQWlnQUFBQUFBQUEjXzUxXzUyXzUzXzU0XzU1XzU2XyNfczI3ODlfczI3OTBfczI3OTFfczI2OTdfczk3MV9VXyMxLS0tIw"
cmpManager.importCMPInfo(consentStringToImport)

Integration with Apple Tracking Transparency (ATT)

In case you are using tracking or analytics in your app, we recommend to read the guide on ATT implementation here.

Creating a custom layout

To create a customized view of the WKWebView, like changing its positioning or background, for example, you can change the configuration passed to the ConsentLayerUIConfig object like below:

ConsentLayerUIConfig(
    position: .halfScreenTop,
    backgroundStyle: .dimmed(.grey, 0.75),
    cornerRadius: 20,
    respectsSafeArea: false,
    allowsOrientationChanges: true)

Logging

When using our iOS SDK, you may find the need to debug or analyze log information for various purposes. The logs generated by our SDK are tagged under “CMP”, allowing you to easily filter and view only the relevant logs.

The post iubenda SDK v3.5 Integration – IOS  appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

The CMPManager class provides methods to manage user consent for data processing and tracking. This documentation covers the main methods available for mobile app integration.

Initialization

UrlConfig()

Sets the URL configuration for the iubenda SDK. Needs to be initialized with the value below, and passed to the getInstance method. 

Parameters:

• id: String – Your site-specific configuration retrieved on the embedding section of your Privacy Controls and Cookie Solution embedding section
• domain: String – The domain for iubenda CDN
• language: String – The language code (e.g., “EN”, “IT”, “DE”, etc)
• appName: String – The name of your app, used only for reporting purposes
• jsonConfig: JSON String – Optional, can be useful to inject a local configuration direcl inside the mobile SDK 

Example:

val urlConfig = UrlConfig(
    id = "your_site_specific_id",
    domain = "cdn.iubenda.com",
    language = "EN",
    appName = "CMDemoAppKotlin"
)

setActivity()

Sets the Activity that will present the consent layer. It should be a ComponentActivity. 

Parameters:

• ComponentActivity – The Activity where the consent layer will be presented.

cmpManager.setActivity(this)

Consent Layer Management

getUserStatus()

Returns a detailed snapshot of the user’s current consent status and preferences. This method provides comprehensive information about the user’s consent choices, including their overall consent status, individual vendor permissions, purpose-specific consents, and relevant consent strings.

Parameters:

• None

Returns:

Return Type: UserConsentStatus object, explained in the code below. 

Example:

val status = cmpManager.getUserStatus()
  Log.d("CMPDemo", "User Status: ${status.hasUserChoice}")
  Log.d("CMPDemo", "TCF: ${status.tcf}")
  Log.d("CMPDemo", "Additional Consent: ${status.addtlConsent}")
  Log.d("CMPDemo", "Regulation: ${status.regulation}")

  Log.d("CMPDemo", "---- Purposes Status ----")
   status.purposes.forEach { (purposeId, choice) ->
    Log.d("CMPDemo", "Purpose $purposeId: $choice")
                    }

checkAndOpen()

Checks with the server if consent is required and opens the consent layer if necessary. This will make a network call to our servers via the Webview created inside our SDK, consuming one pageview in the process. This network call will send a message to our backend via JavaScript, which will detect whether the device has a valid consent or not, which will in turn determine whether the consent layer needs to be displayed or not.  

Parameters:

• jumpToSettings: A boolean value to determine whether the consent layer displayed will automatically lead to the page where a more granular control over the consents given by the users, allowing them to fine tune their choices (when set to true) or the initial default screen with the buttons (when set to false or suppressed).
• completion: A closure called when the operation completes, with the result, either true or false.

Returns: None

Example:

cmpManager.checkAndOpen(false, result -> {
     if (result.isSuccess()) {
         showToast("Check and Open operation completed");
     } else {
         showToast("Error: " + result.exceptionOrNull());
     }
         return null;
     });

forceOpen()

Opens the consent layer. It makes a network call to our backend, consuming one pageview in the process. It will display the consent layer allowing the user to either Accept All or Reject All of the choices, or, depending on the jumpToSettings parameter, allow them to control the consents in a more granular way. 

Parameters:

• jumpToSettings: A boolean value to determine whether the consent layer displayed will automatically lead to the page where a more granular control over the consents given by the users, allowing them to fine tune their choices (when set to true) or the initial default screen with the buttons (when set to false or suppressed).
• completion: A closure called when the operation completes, returning either a sucess or an error. 

Returns: None

Example:

cmpManager.forceOpen(false, result -> {
   if (!result.isSuccess()) {
      Log.e(TAG, "Error opening consent layer", result.exceptionOrNull());
      showToast("Error opening consent layer");
   }
   return null;
});

Consent Status

exportCMPInfo()

Exports the current consent information stored on the device as a string. This method retrieves the consent string from the SharedPreferences area of the device, and returns it. Usually this information is passed to the importCMPInfo method.

Returns: String – The exported consent information

Example:

val cmpString = cmpManager.exportCMPInfo()
Log.d("CMPDemo", "CMP String: $cmpString")

getGoogleConsentModeStatus()

Seamlessly integrates with Consent Mode, a Google technology that enables conversion and analytics modeling, allowing Google’s services to fill in data gaps when users do not consent. This function translates the user’s consent from your CMP into a format that Firebase Analytics can understand, so you can simply get the return of this method and pass it along to Firebase .setConsent method.

• It then updates Google Analytics with the user’s current consent status.

Parameters:

• None

Returns: Map<String, String> – An key value array with the four Google Consent Mode keys: .analyticsStorage, .adStorage, .adUserData and .adPersonalization, and their respective values in terms of .choiceDoesntExist, .granted or .denied.

Example:

val settings = cmpManager.getGoogleConsentModeStatus()
Log.d("CMPDemo", "Google Consent Mode Settings: $settings")
toastMessage = buildString {
  append("Google Consent Settings:")
  settings.forEach { (key, value) ->
	  append("\n$key: $value")
  }
}

getStatusForPurpose()

Checks if consent has been given for a specific purpose and this consent is stored on the device. It checks the UserDefaults area for the consents accepted or rejected, and filter the ID passed as a parameter, returning true if the consent was accepted or false otherwise. 

Parameters:

• id: String – The ID of the purpose to check

Returns: ConsentStatus – An enum with the values CHOICE_DOESNT_EXIST if no consent was given, GRANTED or DENIED.

Example:

val hasPurpose = cmpManager.getStatusForPurpose("c53")
toastMessage = "Has Purpose: $hasPurpose"

Consent Modification

acceptAll()

Accepts consent for all purposes and vendors, consuming one pageview in the process. It makes a network call to our backend via a message injected on the WebView, which will trigger the acceptance of all the consents, according to the CMP configuration. This information will only be available to the other methods after the callback returns a success or failure, which means it was succesfully processed by our backend and persisted on the device. 

Parameters:

• completion: A closure called when the operation completes, returning failure or success.

Returns: None

Example:

cmpManager.acceptAll { result ->
    result.onSuccess {
	    toastMessage = "All consents accepted"
  	}.onFailure { error ->
		toastMessage = "Error: ${error.message}"
	}
}

acceptPurposes()

Accepts consent for specified purposes, consuming one pageview in the process. It makes a network call to our backend via a message injected on the WebView, which will trigger the acceptance of the determined purposes passed as a parameter, according to the CMP configuration. This information will only be available to the other methods after the callback returns a success or failure, which means it was succesfully processed by our backend and persisted on the device. 

Parameters:

• purposes: List<String> – A list of purpose IDs to accept
• updatePurpose: Boolean – Whether to update related purposes
• completion: A closure called when the operation completes, returning either a failure or a success

Returns: None

Example:

cmpManager.acceptPurposes(listOf("2", "3"), true) { result ->
	  	result.onSuccess {
	  	toastMessage = "Purposes enabled"
  	}.onFailure { error ->
  		toastMessage = "Error: ${error.message}"
    }
}

importCMPInfo()

Imports consent information from a CMP string. This will receive a plain string containing the consent data, usually obtained through the exportCMPInfo method. This information is persisted in the SharedPreferences area of the device, and at the same time is sent to our backend via a message injected in the WebView, consuming one pageview in the process. 

Parameters:

• cmpString: String – The CMP string to import
• completion: A closure called when the operation completes, returning either a failure or success

Returns: None

Example:

val cmpString = "Q1FERkg3QVFERkg3QUFmR01CSVRCQkVnQUFBQUFBQUFBQWlnQUFBQUFBQUEjXzUxXzUyXzUzXzU0XzU1XzU2XyNfczI3ODlfczI3OTBfczI3OTFfczI2OTdfczk3MV9VXyMxLS0tIw"
cmpManager.importCMPInfo(cmpString) { result ->
	result.onSuccess {
		toastMessage = "CMP String imported!"
	}.onFailure { error ->
		toastMessage = "Error: ${error.message}"
	}
}

rejectAll()

Rejects consent for all purposes and vendors, consuming one pageview in the process. It makes a network call to our backend via a message injected on the WebView, which will trigger the rejection of all the consents, according to the CMP configuration. This information will only be available to the other methods after the callback returns a success or failure, which means it was succesfully processed by our backend and persisted on the device. 

Parameters:

• completion: A closure called when the operation completes

Returns: None

Example:

cmpManager.rejectAll { result ->
	result.onSuccess {
		toastMessage = "All consents rejected"
	}.onFailure { error ->
		toastMessage = "Error: ${error.message}"
	}
}

rejectPurposes()

Rejects consent for specified purposes, consuming one pageview in the process. It makes a network call to our backend via a message injected on the WebView, which will trigger the rejection of the determined purposes passed as a parameter, according to the CMP configuration. This information will only be available to the other methods after the callback returns a success or failure, which means it was succesfully processed by our backend and persisted on the device. 

Parameters:

• purposes: List<String> – A list of purpose IDs to reject
• updateVendor: Boolean – Whether to update related vendors
• completion: A closure called when the operation completes

Returns: None

Example:

cmpManager.rejectPurposes(listOf("2", "3"), true) { result ->
    result.onSuccess {
      toastMessage = "Purposes disabled"
    }.onFailure { error ->
      toastMessage = "Error: ${error.message}"
	}
}

resetConsentManagementData()

Resets all consent management data. This completely erases al the SharedPreferences area entries related to consents accepted or rejected by the user. It is similar to completely removing the app from the device. 

Parameters:

None

Returns: None

Example:

cmpManager.resetConsentManagementData()

Passing consent data to third-party SDKs

updateThirdPartyConsent

This method handles the automatic passing of consent data to third-party SDKs like AppsFlyer, AdJust, Branch, Kochava, Singular, AirBridge and Tenjin. It works via introspection/reflection, so initialize the third-party SDK with your credentials using the usual strategy recommended by the provider, and our CMP SDK will detect the instance of the 3P SDK and invoke the needed methods under the hood. 

CMPManagerDelegate events

setOnClickLinkCallback

The SDK provides a flexible link handling mechanism that allows applications to customize how URLs within the consent layer are handled. By default, all links open within the WebView, but applications can intercept specific URLs to handle them externally when needed.

cmpManager.setOnClickLinkCallback { url ->
            if (url.contains("google.com")) {
                // Open Google URLs in external browser
                try {
                    startActivity(Intent(Intent.ACTION_VIEW, Uri.parse(url)))
                    true // Return true to indicate we handled the URL
                } catch (e: Exception) {
                    Log.e("DemoApp", "Error opening URL: $url", e)
                    false
                }
            } else {
                // Let other URLs load in the WebView
                false
            }
        }

didReceiveConsent(consent: String, jsonObject: Map<String, Any>)

This is triggered when the consent layer was closed after the user updating his/her consents OR when invoking methods that cause changes in the consents, like acceptAll, rejectAll, acceptVendors, rejectVendors, etc. It means that the user accepted of rejected some of all of the consents, and that those were correctly saved in the device.

didShowConsentLayer

This is triggered when the consent layer was actually displayed. It means that there was not a consent valid in the device, so a new one should be collected.

didCloseConsentLayer

This is triggered when the SDK checked the need for a consent, but it was not needed and the layer was not displayed. It means that there is already a valid in the device, so a new one is not necessary and tue consent layer will not be displayed.

didReceiveError

This is triggered when the SDK faced any error, returning its code.

The post iubenda SDK v3.5 – Android – API documentation appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

iubenda SDK is a comprehensive solution for managing user consent in mobile applications. Designed to handle GDPR compliance, user privacy preferences, and ad tracking transparency, this SDK provides a seamless integration for iOS and Android platforms.

Steps – High Level Description

1. Integration and Configuration:
   • Integrate the SDK into your app.
   • Configure the SDK settings according to your needs.
2. Creating an Instance and displaying the Consent Layer:
   • On app startup, create an instance of the CMPManager class. This instance will handle the consent process.
   • The SDK will automatically display the consent screen if needed.
3. Processing user’s consent data:
   • Once consents are collected, info is stored and is available for querying through different properties and methods exposed by our SDK. You’ll have information about rejected or accepted consents, vendors and purposes.

1.1 Integration and Configuration

Adding dependency via Gradle

Add the following line to your build.gradle file:

dependencies {
    implementation "net.consentmanager.sdkv3:cmsdkv3:3.2.5"
}

1.2 Creating an instance and displaying consent layer

In your app’s onCreate method, follow these steps to set up the CMP SDK:

1. Create a CMPManager instance using the getInstance method.
2. Prepare two configuration objects:
   • UrlConfig: Includes your CMP settings like your iubenda embedding code and the language of the banner
   • ConsentLayerUIConfig: Sets the appearance of the WebView that will show the consent screen
3. Pass the current Activity using setActivity.
4. Set the delegate to handle CMP events.
5. call the checkAndOpen() function:
   • This will automatically contact the server to determine whether the consent screen needs to be shown.
   • If required, the SDK will automatically present the consent layer inside a WebView, styled according to your configuration.
   • The SDK will then collect and store consent data in the device’s SharedPreferences area, so the app can handle targeted advertising accordingly.

See a full configuration example below

import net.consentmanager.cm_sdk_android_v3.CMPManager
import net.consentmanager.cm_sdk_android_v3.CMPManagerDelegate
import net.consentmanager.cm_sdk_android_v3.ConsentLayerUIConfig
import net.consentmanager.cm_sdk_android_v3.UrlConfig

class MainActivity : ComponentActivity(), CMPManagerDelegate {
    private lateinit var cmpManager: CMPManager

    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        enableEdgeToEdge()

        val urlConfig = UrlConfig(
            id = "<yoursiteID>",
            domain = "cdn.iubenda.com",
            language = "EN",
            appName = "CMDemoAppKotlin"
        )

        val webViewConfig = ConsentLayerUIConfig(
            position = ConsentLayerUIConfig.Position.FULL_SCREEN,
            backgroundStyle = ConsentLayerUIConfig.BackgroundStyle.dimmed(Color.BLACK, 0.5f),
            cornerRadius = 10f,
            respectsSafeArea = true,
            isCancelable = false
        )

        cmpManager = CMPManager.getInstance(
            context = this,
            urlConfig = urlConfig,
            webViewConfig = webViewConfig,
            delegate = this
        )

        cmpManager.setActivity(this)

        checkAndOpenConsentLayer()
    }

    private fun forceOpen() {
        cmpManager.checkAndOpen { result ->
            result.onSuccess {
                showCMPDemoScreen()
            }.onFailure { error ->
                Log.e("DemoApp", "Check and open consent layer failed with error: $error")
            }
        }
    }

    private fun showCMPDemoScreen() {
        setContent {
            MaterialTheme {
                Surface(
                    modifier = Modifier.fillMaxSize(),
                    color = MaterialTheme.colorScheme.background
                ) {
                    CMPDemoScreen(cmpManager)
                }
            }
        }
    }

    override fun onConfigurationChanged(newConfig: Configuration) {
        Log.d("CMP DemoApp", "Configuration changed")
        super.onConfigurationChanged(newConfig)
        cmpManager.onApplicationResume()
    }

	override fun onPause() {
        Log.d("CMP DemoApp", "Activity paused")
        super.onPause()
        cmpManager.onApplicationPause()
    }

    override fun onDestroy() {
        Log.d("CMP DemoApp", "Activity destroyed")
        super.onDestroy()
        cmpManager.onActivityDestroyed()
    }

    override fun didReceiveConsent(consent: String, jsonObject: Map<String, Any>) {
        Log.d("CMP DemoApp", "Consent Layer successfully received consent message.")
        runOnUiThread {
            showCMPDemoScreen()
        }
    }

    override fun didShowConsentLayer() {
        Log.d("CMP DemoApp", "Consent Layer open message received.")
    }

    override fun didCloseConsentLayer() {
        Log.d("CMP DemoApp", "Consent Layer close message received.")
        runOnUiThread {
            showCMPDemoScreen()
        }
    }

    override fun didReceiveError(error: String) {
        Log.e("CMP DemoApp", "SDK error: $error")
    }
}

1.3 Processing users’ consent data

Checking users’s consents

Our SDK offer a unified method to check and retrieve consent information, getUserStatus():

val status = cmpManager.getUserStatus()
Log.d("CMPDemo", "User Status: ${status.hasUserChoice}")
Log.d("CMPDemo", "TCF: ${status.tcf}")
Log.d("CMPDemo", "Additional Consent: ${status.addtlConsent}")
Log.d("CMPDemo", "Regulation: ${status.regulation}")

Log.d("CMPDemo", "---- Purposes Status ----")
status.purposes.forEach { (purposeId, choice) ->
    Log.d("CMPDemo", "Purpose $purposeId: $choice")
}

For further information about the other methods, please refer to our full API Documentation. 

Reopening the Consent Layer to check the users’ choices

In order to allow the user to verify or change their choices, you can simply call forceOpen()

cmpManager.forceOpen()

This method will display the consent layer via the same WebView instance created in the previous steps. 

Importing/Exporting consent information to other sources

In some cases an native app might contain webviews in order to display information, like advertising or content. In order to transmit the consent information from the SDK to the webview, you can retrieve the consent string using:

consentData = cmpManager.exportCMPInfo()

This will export the consent information and all further data that is needed by the CMP. You can then pass this information to the CMP that is in your webview by adding it to the URL that is called in the webview.
If, otherwise, you need to import the consent string using the SDK, you can use the example below:

val consentStringToImport = "Q1FERkg3QVFERkg3QUFmR01CSVRCQkVnQUFBQUFBQUFBQWlnQUFBQUFBQUEjXzUxXzUyXzUzXzU0XzU1XzU2XyNfczI3ODlfczI3OTBfczI3OTFfczI2OTdfczk3MV9VXyMxLS0tIw"
cmpManager.importCMPInfo(consentStringToImport)

Creating a custom layout

To create a customized view of the WKWebView, you can create a wrapper for the ComponentActivity that needs to be passed to the CMP SDK, so you have full control over the appearance and the lifecycle of it. For further information, please refer to the official documentation.

Logging

When using our Android SDK, you may find the need to debug or analyze log information for various purposes. The logs generated by our SDK are tagged under “CMP”, allowing you to easily filter and view only the relevant logs.

Troubleshooting

Class Not Found or NoSuchMethodException:

ProGuard can sometimes obfuscate class names or remove methods that are dynamically referenced via reflection. To fix this, you need to specify the classes and methods that should be kept intact in the ProGuard configuration file using the -keep directive.

Example ProGuard configuration to keep a specific class and its methods:

# Kotlin serialization looks up the generated serializer classes through a function on companion
# objects. The companions are looked up reflectively so we need to explicitly keep these functions.
-keepclasseswithmembers class **.*$Companion {
    kotlinx.serialization.KSerializer serializer(...);
}
# If a companion has the serializer function, keep the companion field on the original type so that
# the reflective lookup succeeds.
-if class **.*$Companion {
  kotlinx.serialization.KSerializer serializer(...);
}
-keepclassmembers class <1>.<2> {
  <1>.<2>$Companion Companion;
}

# If your project uses WebView with JS, uncomment the following
# and specify the fully qualified class name to the JavaScript interface
# class:
-keepclassmembers class * {
    @android.webkit.JavascriptInterface <methods>;
}

-keepattributes JavascriptInterface

-keepclassmembers class net.consentmanager.sdk.common.callbacks.* {
   public *;
}

-keepclassmembers class net.consentmanager.sdk.consentlayer.ui.consentLayer.CmpWebView {
   public *;
}

-keepclassmembers class net.consentmanager.sdk.consentlayer.ui.CmpLayerAppInterface {
   public *;
}
-keep class net.consentmanager.sdk.CMPConsentTool {
                                                      *;
                                                  }

-keepclassmembers class * {
    @android.webkit.JavascriptInterface <methods>;
}

-keepattributes JavascriptInterface

# Serializer for classes with named companion objects are retrieved using `getDeclaredClasses`.
# If you have any, uncomment and replace classes with those containing named companion objects.
#-keepattributes InnerClasses # Needed for `getDeclaredClasses`.
#-if @kotlinx.serialization.Serializable class
#com.example.myapplication.HasNamedCompanion, # <-- List serializable classes with named companions.
#com.example.myapplication.HasNamedCompanion2
#{
#    static **$* *;
#}
#-keepnames class <1>$$serializer { # -keepnames suffices; class is kept when serializer() is kept.
#    static <1>$$serializer INSTANCE;
#}

The post iubenda SDK v3.5 Integration – Android appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

This guide will show you, step by step, how to set up the iubenda plugin and Site Kit so they work smoothly together.

Step 1: Check Google Consent Mode in Site Kit

1. Log in to your WordPress dashboard.
2. Go to Site Kit → Settings.
3. Look for the Consent Mode section.
4. Check if it is enabled.

• If you want iubenda to manage consent:
  Disable Consent Mode in Site Kit. This lets the iubenda plugin control everything.
• If you want Site Kit to manage consent:
  Keep Consent Mode enabled and continue to the next step.

Step 2: Set Up the WP Consent API (If Using Site Kit to Manage Consent)

If you keep Consent Mode enabled in Site Kit, you must install the WP Consent API plugin.

1. Install the WP Consent API Plugin

• Go to Plugins → Add New in your WordPress admin.
• Search for WP Consent API.
• Click Install and then Activate.

2. Check iubenda Settings

• In WordPress, go to iubenda → Privacy Controls and Cookie Solution → Configure.
• Look for the checkbox Integrate with WP Consent API (recommended).
• Make sure this box is checked.
• After enabling the checkbox, click Save settings.

Note: This checkbox will only appear if Site Kit is active and the WP Consent API plugin is installed and activated.

Step 3: Test Your Setup

Once your settings are in place:

1. Reload your website to apply changes.
2. Clear any cache: WordPress caching plugin cache and browser cache
3. Check with Google Tag Assistant to confirm that Consent Mode is working as expected.

Important Notes

• If you disable Consent Mode in Site Kit, iubenda will manage all consent functions.
• If you keep Consent Mode enabled in Site Kit, you must also have the WP Consent API plugin installed and linked to iubenda.
• Always test your configuration after changes to avoid tracking issues.

That’s it! In just a few steps, iubenda and Site Kit can work together to keep your site compliant.

The post How to Integrate the iubenda All-in-one Compliance Plugin with Google Site Kit on WordPress appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Google Consent Mode is a critical component for websites using Google services to maintain compliance with privacy regulations like GDPR. When properly configured, it allows Google’s tags to adjust their behavior based on user consent choices. However, misconfigurations can lead to compliance issues and may affect your ability to use Google’s advertising and analytics services effectively.

This guide will help you identify and resolve common Google Consent Mode configuration issues detected by iubenda’s Site Scanner.

How to Check if Your Google Consent Mode is Properly Configured

The iubenda Site Scanner automatically checks your website for various Google Consent Mode configuration issues. If any problems are detected, you’ll see an “Attention Required” alert in your dashboard. The scanner checks for:

• Correct script placement
• Proper default consent settings
• Multiple consent signals
• Timing of consent updates
• Privacy Controls and Cookie Solution configuration

Common Configuration Issues and Solutions

1. Google scripts fired before user consent is given

Why this issue happens:

When the iubenda Privacy Controls and Cookie Solution script is embedded after Google scripts (like Google Analytics or Google Tag Manager), the Google scripts fire before users can make their consent choices. This can result in default consents being passed as “granted” without user consent, leading to GDPR non-compliance

How to fix it

For WordPress sites:

Use the iubenda WordPress plugin, which automatically places the Privacy Controls and Cookie Solution script before any Google scripts.

For manual implementation:

Access your website’s HTML code
Locate the <head> section of your pages where scripts are embedded.

Identify the iubenda Privacy Controls and Cookie Solution script
Look for code similar to:

<script type="text/javascript" src="https://cs.iubenda.com/autoblocking/[YOUR-SITE-ID].js"></script>

Identify Google-related scripts
Look for scripts like:

• gtag.js (Google Analytics)
• googletagmanager.com (Google Tag Manager)

Reorder the scripts
Move the iubenda Privacy Controls and Cookie Solution script BEFORE any Google scripts.

Example of INCORRECT script order:

<!-- WRONG: Google Analytics script placed BEFORE Privacy Controls and Cookie Solution -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXXXXX');
</script>
<!-- iubenda Privacy Controls and Cookie Solution placed AFTER Google scripts -->
<script type="text/javascript">
var _iub = _iub || [];
_iub.csConfiguration = {
  "askConsentAtCookiePolicyUpdate":true,
  "cookiePolicyInOtherWindow":true,
  "countryDetection":true,
  "enableGdpr":true,
  "floatingPreferencesButtonDisplay":"bottom-right",
  "siteId":3258456,
  // ... rest of configuration
};
</script>
<script type="text/javascript" src="https://cs.iubenda.com/autoblocking/[YOUR-SITE-ID].js"></script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/gpp/stub.js"></script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>

Example of CORRECT script order:

<!-- CORRECT: iubenda Privacy Controls and Cookie Solution placed FIRST -->
<script type="text/javascript">
var _iub = _iub || [];
_iub.csConfiguration = {
  "askConsentAtCookiePolicyUpdate":true,
  "cookiePolicyInOtherWindow":true,
  "countryDetection":true,
  "enableGdpr":true,
  "floatingPreferencesButtonDisplay":"bottom-right",
  "siteId":3258456,
  // ... rest of configuration
};
</script>
<script type="text/javascript" src="https://cs.iubenda.com/autoblocking/[YOUR-SITE-ID].js"></script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/gpp/stub.js"></script>
<script type="text/javascript" src="//cdn.iubenda.com/cs/iubenda_cs.js" charset="UTF-8" async></script>
<!-- Google Analytics placed AFTER iubenda -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
  gtag('config', 'G-XXXXXXXXXX');
</script>

2. Google Consent Mode is not correctly activated via code configuration

Why this issue happens:

The Privacy Controls and Cookie Solution is intentionally configured via code with Google Consent Mode disabled, even though your website requires it for compliance with Google’s requirements and privacy regulations.

How to fix it

1. Update to the latest Privacy Controls and Cookie Solution script
   • Go to your iubenda dashboard
   • Copy the latest script version
   • Replace the old script on your website
2. Ensure you’re using a supported script type:

With Autoblocking enabled

<script type="text/javascript" src="https://cs.iubenda.com/autoblocking/[YOUR-SITE-ID].js"></script>

With Sync.js (Autoblocking disabled)

<script type="text/javascript" src="https://cs.iubenda.com/sync/[YOUR-SITE-ID].js"></script>

Unified script (latest version)

<script type="text/javascript" src="//embeds.iubenda.com/widgets/[YOUR-WIDGET-ID].js"></script>

3. Check your script configuration
   • Ensure "googleConsentMode": true is set in your configuration
   • Remove any instances of "googleConsentMode": false

3. Missing Autoblocking feature or Sync.js

Why this issue happens:

Your Privacy Controls and Cookie Solution is installed but isn’t using either the autoblocking feature or Sync.js, which are required for Google Consent Mode to function properly.

How to fix it

Update from outdated scripts: 

If you’re using an outdated version of the Privacy Controls and Cookie Solution script, replace it with one of these updated versions that support Google Consent Mode:

Option 1 – With Autoblocking (Recommended)

<script type="text/javascript" src="https://cs.iubenda.com/autoblocking/[YOUR-SITE-ID].js"></script>

Option 2 – With Sync.js

<script type="text/javascript" src="https://cs.iubenda.com/sync/[YOUR-SITE-ID].js"></script>

Option 3 – Unified script

<script type="text/javascript" src="//embeds.iubenda.com/widgets/[YOUR-WIDGET-ID].js"></script>

4. Consent purpose is granted by default before explicit user action

Why this issue happens:

One or more consent purposes are set to “granted” by default before users make an explicit choice. This violates the principle of obtaining consent through explicit, positive action and doesn’t align with best practices.

How to fix it

If using Google Tag Manager (GTM):

1. Using iubenda’s GTM template
   • Open your GTM container
   • Find the “iubenda Privacy Controls and Cookie Solution” tag
   • Review the Consent Default settings
   • Change any value set to “Granted” to “Denied”
2. Check for conflicting GTM templates
   • Ensure you’re not using another template that configures Google Consent Mode (e.g., Simo Ahava template)
   • Use only one consent management template

Check for third-party tools or plugins:

Plugins or external apps might be setting consent defaults incorrectly. This is especially common with tools that add pixels or configure Google services.

WordPress + Site Kit:

• Google Site Kit plugin can manage Google Consent Mode
• Since Consent Mode should be managed by iubenda’s CMP, disable any overlapping consent features in Site Kit

Shopify + Google & YouTube app:

• The official Google & YouTube app may automatically set Google Consent Mode signals
• Follow the Privacy Controls and Cookie Solution for Shopify guide

Remove manual gtag consent code:

If you previously manually set consent defaults using gtag, remove that code. Look for and remove code like this:

<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
// REMOVE THIS CODE - it overrides default consent
gtag('consent', 'default', {
  'ad_storage': 'granted',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'analytics_storage': 'denied'
});
</script>

After removing this code, iubenda’s CMP will handle the default consent configuration, provided you have autoblocking or Sync.js enabled.

5. Multiple default consent signals sent due to conflict on the cookie banner

Why this issue happens:

Multiple default consent signals are being sent because there are multiple cookie banners (from different CMPs) installed on the website. This can happen when using platforms like Shopify or when plugins are double-managing Google Consent Mode. When our solution and other plugins both launch Google Consent Mode signals, it causes incompatibility and multiple signals.

How to fix it

1. Check for conflicting GTM templates

If you’re using the iubenda GTM template, ensure you’re not simultaneously using another template that configures Google Consent Mode (e.g., Simo Ahava template).

2. Identify and resolve third-party tool conflicts

Plugins or external apps might be setting consent defaults incorrectly. This is especially common with tools that add pixels or configure Google services.

WordPress + Site Kit:

• The Google Site Kit plugin allows managing Google Consent Mode
• Since Consent Mode is managed by iubenda’s CMP, disable any overlapping consent features from such plugins

Shopify + Google & YouTube app:

• If using the official Google & YouTube app, Shopify may automatically set the Google Consent Mode signal
• Follow the Privacy Controls and Cookie Solution for Shopify guide

3. Remove manual setup in site code (gtag):

If you previously manually set consent defaults using gtag, remove that code as it will override the CMP configuration.

Example of code to remove:

<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
// This code overrides default consent – REMOVE IT
gtag('consent', 'default', {
  'ad_storage': 'granted',
  'ad_user_data': 'denied',
  'ad_personalization': 'denied',
  'analytics_storage': 'denied'
});
</script>

After removing this code, iubenda’s CMP will be the sole handler of consent configuration.

How to debug multiple consent events:

To check your DataLayer for anomalies:

1. Open your browser’s developer console
2. Type dataLayer and press Enter
3. Look for multiple consent events
4. Check if certain purposes are not behaving as expected

6. Consent preference is updated before user made a choice on the cookie banner

Why this issue happens:

A user’s consent preference (either Accept or Reject) is sent to Google before the user has explicitly made a choice on the banner. As a result, when the user eventually interacts with the cookie banner, their preference is no longer taken into account by Google, since a consent signal has already been sent earlier.

This often occurs when the Privacy Controls and Cookie Solution is configured with enableGdpr: false, meaning the user has unintentionally enabled US legislation and/or Swiss legislation even though the site should comply with GDPR legislation.

How to fix it

1. Correct Privacy Controls and Cookie Solution configuration

• Enable GDPR legislation if it’s disabled in the Privacy Controls and Cookie Solution configurator
• Ensure enableGdpr: true is set in your configuration if your site serves EU users

2. Check for third-party interference

The same third-party tools mentioned in Issue #4 and 5 can cause this problem:

WordPress + Site Kit:

• Google Site Kit plugin can manage Google Consent Mode
• Disable any overlapping consent features since iubenda should handle all consent management

Shopify + Google & YouTube app:

• The official app may automatically set Google Consent Mode signals
• Follow the Privacy Controls and Cookie Solution for Shopify guide

Special Considerations for US Users

If you enable US Law in the Privacy Controls and Cookie Solution configurator, the default behavior for US users differs from GDPR:

• Privacy Controls and Cookie Solution sets all Google Consent Mode purposes to ‘granted’ by default for US users
• When users opt out of specific purposes under US Law, settings adjust accordingly

Note: If you’re on a Free plan, this applies only if you disable GDPR and apply only US Law. To apply GDPR for EU users and US Law for US users, you need at least an Advanced plan.

How US opt-out works:

ad_storage is granted when the user hasn’t opted out of:

• Sale of personal information (purpose s)
• Sharing of personal information (purpose sh)
• Processing of personal information for targeted advertising (purpose adv)

analytics_storage is granted when the user hasn’t opted out of:

• Sale of personal information (purpose s)

Debugging Google Consent Mode

To verify your configuration is working correctly:

1. Use Google Tag Assistant
   • Install the browser extension
   • Navigate to your website
   • Check for Consent Mode events in the dataLayer
2. Check the dataLayer
   Open your browser’s console and type “dataLayer”; look for consent-related events and verify they match user interactions.
3. Monitor consent signals
   • Default consent should show all purposes as “denied” (for GDPR)
   • After user acceptance, relevant purposes should update to “granted”
   • Ensure only one set of consent signals is sent

Best Practices

1. Always place iubenda scripts first – Before any Google or tracking scripts
2. Use the latest script version – Check your dashboard regularly for updates
3. Test after changes – Use the Site Scanner to verify your configuration
4. One consent solution only – Avoid conflicts by using only iubenda for consent management
5. Contact support when needed – These issues can be technical; our Support Team is here to help

Need Help?

If you’re experiencing difficulties resolving these issues:

• Contact our Support Team for personalized assistance
• Include your Site Scanner results in your support request
• Provide details about your website platform (WordPress, Shopify, custom, etc.)

Remember, Google requires proper Consent Mode implementation for continued use of their advertising and analytics services. Ensuring correct configuration is essential for both compliance and maintaining your Google services functionality.

The post Google Consent Mode Troubleshooting Guide appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Overview

For our clients that integrate our CMP SDK along with one of the following 3rd-party SDKs, we’ve composed this document where you’ll find individual guides that will demonstrate how consents collected using our CMP SDK are passed to these SDKs. Our CMP is fully compatible with TCF v2.2, and it collects DMA consent data and stores it in SharedPreferences. Some of the SDKs below can fetch this data automatically, and some require some code. Please check below the individual use cases.  

On some SDKs from providers like AppsFlyer, AdJust and Branch you’ll need to either (a) invoke our updateThirdPartyConsent() method, which will automatically pass the collected consents to these SDKs via introspection/reflection, or (b) use their own methods and properties to do it manually. In case you’re using our CMP SDK to automatically handle the pass of the consent data, here’s an example of implementation: 

import net.consentmanager.cm_sdk_android_v3.CMPManager
import net.consentmanager.cm_sdk_android_v3.CMPManagerDelegate
import net.consentmanager.cm_sdk_android_v3.ConsentLayerUIConfig
import net.consentmanager.cm_sdk_android_v3.UrlConfig

public class AppsflyerBasicApp extends Application {
@Override
public void onCreate() {
super.onCreate()

   // Initialize your third-party SDK. Replace the code below by your respective third-party init code 
   // according to the instructions along this document
    String yourClientToken = "YOUR-CLIENT-TOKEN"
    YourThirdPartySdk yourThirdPartySdk = YourThirdPartySdk.getInstance()
    yourThirdPartySdk.init(yourClientToken)

    // Initializing our CMP SDK
    val urlConfig = UrlConfig(
        id = "YOUR_CODE_ID_HERE",
        domain = "cdn.iubenda.com",
        language = "EN",
        appName = "CMDemoAppKotlin"
    )

    cmpManager = CMPManager.getInstance(
        context = this,
        urlConfig = urlConfig,
        webViewConfig = webViewConfig,
        delegate = this
    )

    cmpManager.setActivity(this)

    // Here our CMP SDK will automatically display the consent layer if there is no consent
    // or the consent is expired. The didReceiveConsent() callback below will be triggered
    // once user consent is collected, which happens right after the users accepts/rejects
    // and all IAB TCF data is persisted to the SharedPreferences area
    checkAndOpen()

}

  override fun didReceiveConsent(consent: String, jsonObject: Map<String, Any>) {
    Log.d("CMP DemoApp", "Consent Layer successfully received consent message.")
    // Here we'll automatically handle the passing of the consent from our
    // CMP SDK to the 3P SDK
    cmpManager.updateThirdPartyConsent()
  }
}

For further information, proceed to the respective third-party instructions below.

AppsFlyer

This SDK searches for TCF string stored inside the SharedPreferences area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

1. Initialize the AppsFlyer SDK and enable TCF data collection. On the code presented on the Overview section of this document, replace the third-party initialization part with:

AppsFlyerLib.getInstance().init(<YOUR_DEV_KEY>, null, this);
		AppsFlyerLib.enableTCFDataCollection(true);

1. Initialize our CMP SDK
2. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
3. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
4. Get confirmation from the CMP that the user has made their consent decision, and the data is available in SharedPreferences. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
5. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by AppFlyer’s start() method. In the latter case, replace the line inside our didReceiveMessage callback by the the line below: 

AppsFlyerLib.getInstance().start(this);

AdJust

This SDK does not retrieve consent data stored inside the SharedPreferences area of the device, so you have two ways of achieving this feat: (a) automatic, which will be completely handled by our CMP SDK; and (b) manual, where you’ll use both SDKs features to achieve this. Please follow the instructions below: 

1. Initialize the AdJust SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in SharedPreferences. There are different ways of doing this with our CMP SDK. In the example below, we’re using the didReceiveConsent() callback to illustrate. 
6. As a last step, you can either (a) invoke the updateThirdPartyConsent() method from our CMP SDK, which will automatically pass the data to AdJust’s SDK via introspection/reflection or replace it by the code below:

override fun didReceiveConsent(consent: String, jsonObject: Map<String, Any>) {
        Log.d("CMP DemoApp", "Consent Layer successfully received consent message.")
        // Retrieve Google Consent Mode data...
        val consentData = cmpManager.getGoogleConsentModeStatus();

		// ... and parse it to pass to AdJust SDK
		val adStorageConsent = consentSettings["ad_storage"] == "granted" ? "1" : "0"
        val adPersonalizationConsent = consentSettings["ad_personalization"] == "granted" ? "1" : "0"

		val adjustThirdPartySharing = AdjustThirdPartySharing(true)
        adjustThirdPartySharing.addGranularOption("google_dma", "eea", "1");
        adjustThirdPartySharing.addGranularOption("google_dma", "ad_personalization", adPersonalizationConsent);
        adjustThirdPartySharing.addGranularOption("google_dma", "ad_user_data", adStorageConsent);
        Adjust.trackThirdPartySharing(adjustThirdPartySharing)        
    }

Branch

This SDK does not retrieve consent data stored inside the SharedPreferences area of the device, so you have two ways of achieving this feat: (a) automatic, which will be completely handled by our CMP SDK; and (b) manual, where you’ll use both SDKs features to achieve this. 

1. Initialize Branch using your app token
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in SharedPreferences. There are different ways of doing this with our CMP SDK. In the example below, we’re using the didReceiveConsent() callback to illustrate. 
6. As a last step, you can either (a) invoke the updateThirdPartyConsent() method from our CMP SDK, which will automatically pass the data to AdJust’s SDK via introspection/reflection or replace it by the code below: 

override fun didReceiveConsent(consent: String, jsonObject: Map<String, Any>) {
        Log.d("CMP DemoApp", "Consent Layer successfully received consent message.")
        // Retrieve Google Consent Mode data...
        val consentData = cmpManager.getGoogleConsentModeStatus();

		// ... and parse it to pass to AdJust SDK
		val adStorageConsent = consentSettings["ad_storage"] == "granted"
        val adPersonalizationConsent = consentSettings["ad_personalization"] == "granted" 

        // Example for an EEA resident
        Branch.getInstance().setDMAParamsForEEA(true,adPersonalizationConsent,adStorageConsent)

        // Example for an non-EEA resident
        Branch.getInstance().setDMAParamsForEEA(false,adPersonalizationConsent,adStorageConsent)
          
        // For further information, check:
        // https://help.branch.io/developers-hub/docs/ios-advanced-features#user-data
}

Kochava

This SDK searches for TCF string stored inside the SharedPreferences area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

1. Initialize the Kochava SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in SharedPreferences. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
6. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by Kochava’s startWithAppGuid() method. In the latter case, replace the line inside our didReceiveMessage callback by the the line below: 

Tracker.getInstance().startWithAppGuid(applicationContext, "YOUR_ANDROID_APP_GUID")

Singular

This SDK searches for TCF string stored inside the SharedPreferences area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

1. Initialize the Singular SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in SharedPreferences. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
6. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by Singular’s trackingOptIn() method. In the latter case, replace the line inside our didReceiveMessage callback by the the line below: 

Singular.trackingOptIn();

AirBridge

This SDK searches for TCF string stored inside the SharedPreferences area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

1. Initialize the AirBridge SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in SharedPreferences. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
6. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by AirBridge’s startTracking() method. In the latter case, replace the line inside our didReceiveMessage callback by the the line below: 

Airbridge.startTracking()

Tenjin

This SDK searches for TCF string stored inside the SharedPreferences area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

1. Initialize the Tenjin SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in SharedPreferences. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
6. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by Tenjin optIn()/optOut() methods.

The post iubenda mobile SDK | Android | 3rd Party App Attribution Partners (AAPs) appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

For our clients that integrate our CMP SDK along with one of the following 3rd-party SDKs, we’ve composed this document where you’ll find individual guides that will demonstrate how consents collected using our CMP SDK are passed to these SDKs. Our CMP is fully compatible with TCF v2.2, and it collects DMA consent data and stores it in UserDefaults. Some of the SDKs below can fetch this data automatically, and some require some code. Please check below the individual use cases. 

On some SDKs from providers like AppsFlyer, AdJust and Branch you’ll need to either (a) invoke our updateThirdPartyConsent() method, which will automatically pass the collected consents to these SDKs via introspection/reflection, or (b) use their own methods and properties to do it manually. In case you’re using our CMP SDK to automatically handle the pass of the consent data, here’s an example of implementation: 

@main
class AppDelegate: UIResponder, UIApplicationDelegate, CMPManagerDelegate {
var window: UIWindow?
var cmpManager: CMPManager!

func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
    // Initialize your third-party SDK. Replace the code below by your respective third-party init code
    // according to the instructions along this document
    let yourClientToken = "YOUR-CLIENT-TOKEN"
    let yourThirdPartySdk = YourThirdPartySdk.shared()
    yourThirdPartySdk.initialize(withToken: yourClientToken)

    // Initializing our CMP SDK
    let urlConfig = UrlConfig(
        id: "YOUR_CODE_ID_HERE",
        domain: "cdn.iubenda.com",
        language: "EN", 
        appName: "CMDemoAppSwift"
    )

    let webViewConfig = ConsentLayerUIConfig()

    cmpManager = CMPManager.shared
    cmpManager.delegate = self
    cmpManager.setUrlConfig(urlConfig)
    cmpManager.setWebViewConfig(webViewConfig)

    // Set the root view controller for consent UI presentation
    if let rootViewController = window?.rootViewController {
        cmpManager.setPresentingViewController(rootViewController)
    }

    // Here our CMP SDK will automatically display the consent layer if there is no consent
    // or the consent is expired. The didReceiveConsent() callback below will be triggered
    // once user consent is collected, which happens right after the users accepts/rejects
    // and all IAB TCF data is persisted to the UserDefaults area
    checkAndOpenConsent()

    return true
}

func checkAndOpenConsent() {
    cmpManager.checkAndOpen { error in
        if let error = error {
            print("Error checking consent: \(error.localizedDescription)")
        }
    }
}

// MARK: - CMPManagerDelegate Methods

func didReceiveConsent(consent: String, jsonObject: [String: Any]) {
    print("CMP DemoApp: Consent Layer successfully received consent message.")
    // Here we'll automatically handle the passing of the consent from our
    // CMP SDK to the 3P SDK
    let results = cmpManager.updateThirdPartyConsent()
    print("Third-party consent update results: \(results)")
  }
}

AppsFlyer

This SDK searches for TCF string stored inside the UserDefaults area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

• Initialize the AppsFlyer SDK and enable TCF data collection. On the code presented on the Overview section of this document, replace the third-party initialization part with:

AppsFlyerLib.shared().waitForATTUserAuthorization(timeoutInterval: 60)
    AppsFlyerLib.shared().enableTCFDataCollection(true)

1. Initialize our CMP SDK
2. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
3. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
4. Get confirmation from the CMP that the user has made their consent decision, and the data is available in UserDefaults. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
5. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by AppFlyer’s start() method. In the latter case, replace the line inside our didReceiveMessage callback by the the line below: 

AppsFlyerLib.shared().start()

AdJust

This SDK does not retrieve consent data stored inside the UserDefaults area of the device, so you have two ways of achieving this feat: (a) automatic, which will be completely handled by our CMP SDK; and (b) manual, where you’ll use both SDKs features to achieve this. Please follow the instructions below: 

1. Initialize the AdJust SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in UserDefaults. There are different ways of doing this with our CMP SDK. In the example below, we’re using the didReceiveConsent() callback to illustrate. 
6. As a last step, you can either (a) invoke the updateThirdPartyConsent() method from our CMP SDK, which will automatically pass the data to AdJust’s SDK via introspection/reflection or replace it by the code below: 

func didReceiveConsent(consent: String, jsonObject: [String: Any]) {
    print("CMP DemoApp: Consent Layer successfully received consent message.")
    // Retrieve Google Consent Mode data...
    let consentData = cmpManager.getGoogleConsentModeStatus()
    // ... and parse it to pass to Adjust SDK
    let adStorageConsent = consentData["ad_storage"] == "granted" ? "1" : "0"
    let adPersonalizationConsent = consentData["ad_personalization"] == "granted" ? "1" : "0"
    let adjustThirdPartySharing = ADJThirdPartySharing(isEnabled: true)
    adjustThirdPartySharing?.addGranularOption("google_dma", key: "eea", value: "1")
    adjustThirdPartySharing?.addGranularOption("google_dma", key: "ad_personalization", value: adPersonalizationConsent)
    adjustThirdPartySharing?.addGranularOption("google_dma", key: "ad_user_data", value: adStorageConsent)
    Adjust.trackThirdPartySharing(adjustThirdPartySharing)
}

Branch

This SDK does not retrieve consent data stored inside the UserDefaults area of the device, so you have two ways of achieving this feat: (a) automatic, which will be completely handled by our CMP SDK; and (b) manual, where you’ll use both SDKs features to achieve this. 

1. Initialize Branch using your app token
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in UserDefaults. There are different ways of doing this with our CMP SDK. In the example below, we’re using the didReceiveConsent() callback to illustrate. 
6. As a last step, you can either (a) invoke the updateThirdPartyConsent() method from our CMP SDK, which will automatically pass the data to AdJust’s SDK via introspection/reflection or replace it by the code below: 

override fun didReceiveConsent(consent: String, jsonObject: Map<String, Any>) {
        Log.d("CMP DemoApp", "Consent Layer successfully received consent message.")
        // Retrieve Google Consent Mode data...
        val consentData = cmpManager.getGoogleConsentModeStatus();

		// ... and parse it to pass to AdJust SDK
		val adStorageConsent = consentSettings["ad_storage"] == "granted"
        val adPersonalizationConsent = consentSettings["ad_personalization"] == "granted" 

        // Example for an EEA resident
        Branch.getInstance().setDMAParamsForEEA(true,adPersonalizationConsent,adStorageConsent)

        // Example for an non-EEA resident
        Branch.getInstance().setDMAParamsForEEA(false,adPersonalizationConsent,adStorageConsent)
          
        // For further information, check:
        // https://help.branch.io/developers-hub/docs/ios-advanced-features#user-data
}

Kochava

This SDK searches for TCF string stored inside the UserDefaults area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

1. Initialize the Kochava SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in UserDefaults. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
6. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by Kochava’s startWithAppGuid() method. In the latter case, replace the line inside our didReceiveMessage callback by the the line below: 

Tracker.getInstance().startWithAppGuid(applicationContext, "YOUR_ANDROID_APP_GUID")

Singular

This SDK searches for TCF string stored inside the UserDefaults area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

1. Initialize the Singular SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in UserDefaults. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
6. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by Singular’s trackingOptIn() method. In the latter case, replace the line inside our didReceiveMessage callback by the the line below: 

Singular.trackingOptIn();

AirBridge

This SDK searches for TCF string stored inside the UserDefaults area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

1. Initialize the AirBridge SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in UserDefaults. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
6. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by AirBridge’s startTracking() method. In the latter case, replace the line inside our didReceiveMessage callback by the the line below: 

Airbridge.startTracking()

Tenjin

This SDK searches for TCF string stored inside the UserDefaults area of the device, providing automatic flow of the consents collected on the device via our CMP SDK to AppsFlyer events. In order to pass consent data to AppsFlyer, please follow the instructions below:

1. Initialize the Tenjin SDK 
2. Initialize our CMP SDK
3. Use our CMP SDK to automatically decide if you need the consent dialog in the current session.
4. If needed, consent dialog will be displayed to capture the user consent choices, be it accept all, reject all or customize choices.
5. Get confirmation from the CMP that the user has made their consent decision, and the data is available in UserDefaults. There are different ways of doing this with our CMP SDK. In the example on the overview, we’re using the didReceiveConsent() callback to achieve this. 
6. The last step can be performed in two ways: (a) you can follow our code chunk from the overview or (b) you can replace it  by Tenjin optIn()/optOut() methods.

The post iubenda mobile SDK – IOS – 3rd Party App Attribution Partners (AAPs) appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Google-certified cmp for consent mode

Avoid losing your conversion tracking – implement Google Consent Mode today

Google is disabling conversion tracking for websites that haven’t correctly implemented Google Consent Mode (CoMo). This privacy requirement is now mandatory to maintain measurement features in Google Ads and Analytics. With iubenda’s certified solution, you can set up Consent Mode correctly – quickly, reliably, and fully compliant.

Set up Consent Mode Is it active? Check now

Available for all plans, including the Free one!

Google Ads

Google Analytics

GDPR-Ready

Google will block conversion tracking and remarketing

Starting March 2024, Google requires websites to implement Consent Mode v2 to continue tracking conversions and using key features in Google services like Ads and Analytics. If your implementation is missing or faulty, Google will block conversion tracking and remarketing, impacting your campaign performance and measurement accuracy.

iubenda is a Google-certified Consent Management Platform that helps you implement and verify Consent Mode effortlessly – whether you’re starting from scratch or optimizing an existing setup.

Get Google Consent Mode in three easy steps

Navigating the maze of international regulations and service provider guidelines is challenging. iubenda makes it simple with powerful features. Focus on your business, confident that your compliance is handled by the best.

STEP 1

Configure your consent banner

Answer a few simple questions, and go with iubenda’s automatic configuration or totally customize banner and consent collection.

STEP 2

Install it on your site

Copy and paste the provided code into your website, implement our Google Tag Manager template, or choose from one of our dedicated plugins. Everything else is automatic, including Google Consent Mode setup.

STEP 3

Model data from non-consented users

Enjoy improved marketing data since Google Consent Mode is built into your iubenda CMP. Google’s advanced algorithms allow you to see conversions and analytics even for users that don’t give you tracking consent, and iubenda helps you get it done with zero effort.

Since you’re using Google services now, don’t forget to add the required clauses and disclosures in your privacy policy, such as Google Analytics 4 and Google Ads conversion tracking.

Already activated Consent Mode?

Make sure it’s up and running with our free scanner

iubenda with Google Consent Mode inside

Geolocation Savvy

Intelligently adapt with geolocation support to improve compliance and personalization right from the start. Understanding your audience, no matter where they’re Browse from.

Flexible Consent Handling

Choose Basic Consent Mode to turn off Google tags until you get user consent or activate Advanced Consent Mode for a smoother experience that preloads Google tags but respects user choices, using cookieless pings if consent is declined.

Missing Cookies? No Problem.

When users say no to cookies, cookieless pings can step in and keep the data flowing. This feature ignores users’ personal details but makes Google’s conversion models even more accurate.

Instantly Adaptable

Get better insight into user behavior in real time. Our tools constantly monitor your users’ consent preferences, and Google Consent Mode adapts to keep you informed.

Beyond the Ads and Analytics

Our Google-certified CMP isn’t just a tool; it’s a global compliance partner. With iubenda, you’ll up your Google Ads game while we help cover all your compliance bases in record time and without the hassle.

Click, Copy, Collect More Data

Set up is a breeze thanks to our integration with Google Tag Manager. Simply apply our GTM template and put any concerns about Google Consent Mode to rest. We also offer options for CMS plugins and direct site code integration.

Available for all plans, including the Free one!

Choose the easy way to get Google Consent Mode

Set up Consent Mode

Victor, N.

CEO

“iubenda stays on top of the laws around the world, so they adjust and add more stuff to help users comply with new laws.”

The post Google Consent mode v2 – certified CMP appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Im Rahmen dieses Engagements orientieren wir uns an der Europäischen Richtlinie über die Barrierefreiheit (EAA) sowie an internationalen Standards wie den Web Content Accessibility Guidelines (WCAG), herausgegeben vom World Wide Web Consortium (W3C). Diese Richtlinien bieten eine Grundlage dafür, Webinhalte für Menschen mit unterschiedlichen Bedürfnissen barrierefrei zu gestalten.

Um bestmögliche Ergebnisse zu erzielen, arbeiten wir mit AccessiWay zusammen.

Dokumentation

Unsere Website bzw. unser Service wurde einer Prüfung unterzogen. Die Ergebnisse stellen wir Ihnen hier in einem barrierefreien Format zur Verfügung:

• Barrierefreiheitskonformitätsbericht für unsere Website

Feedback und kontinuierliche Verbesserung

Wir verstehen Barrierefreiheit als einen fortlaufenden Prozess. Auch wenn wir bestrebt sind, unsere Website und unsere Dienste vollständig barrierefrei zu gestalten, kann es Bereiche geben, die sich noch in der Weiterentwicklung befinden oder durch aktuelle Technologien eingeschränkt sind.

Wir arbeiten kontinuierlich an Verbesserungen – durch neue Funktionen, regelmäßige Aktualisierungen und den Einsatz moderner Technologien, um Barrieren abzubauen.

Wenn Sie auf Barrieren stoßen oder uns Feedback geben möchten, kontaktieren Sie uns gerne:

info@iubenda.com

Ihr Feedback hilft uns, eine inklusivere und barrierefreie Erfahrung für alle zu schaffen.

The post Barrierefreiheit appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

To support this commitment, we work to align our digital assets with the European Accessibility Act (EAA) as well as international standards such as the Web Content Accessibility Guidelines (WCAG), published by the World Wide Web Consortium (W3C). These guidelines provide a framework to make web content more accessible to users with a diverse range of needs.

To support the best possible outcome we have partnered with AccessiWay to make sure we arrive at the best possible results.

Documentation

Our site/service has undergone auditing and we make our results available here for download in an accessible format:

• Accessibility conformance report for our website
• Accessibility conformance report for the Cookie Banner

Feedback and Continuous Improvement

We recognize that accessibility is an ongoing process. While we strive to make all parts of our website and services accessible, there may be instances where certain areas are still undergoing improvements or where current technology limits full accessibility.

We continually strive to improve our accessibility, adding, updating, and enhancing its options and features, and developing and adopting new technologies to remove barriers.

If you encounter accessibility-related issues or would like to share feedback, please contact us at:

info@iubenda.com

Your input helps us improve and ensure a more inclusive experience for everyone.

The post Accessibility appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Important: your compliance tools have been paused

Your iubenda Privacy Controls and Cookie Solution has exceeded the page view quota included in your current plan, so your cookie banner is no longer displaying. Right now, only essential scripts are being loaded.

Fix this now

Let’s get your tools back up and running

Your current plan has exceeded its page view limit, which means your cookie banner has been paused for now. Essential scripts are still running, but to avoid compliance gaps, it’s time to upgrade. Choose the plan that fits your traffic, and we’ll get everything back up and running in no time.

Upgrade your iubenda plan now →

The post Fix your cookie solution overquota issue appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Whether you’re designing a website, writing a blog, or scheduling a social post, adding thoughtful, descriptive alt text makes a real difference to people who rely on screen readers or other assistive tech. 

But writing effective alt text isn’t always straightforward. What do you say about a chart? Do product images need detail? When is it better to leave alt text blank?

In this guide, we’ll cover everything you need to know about alt text best practices – with real alt text examples. In just a few moments, you’ll be better placed to write image descriptions that improve accessibility, boost SEO, and meet key compliance standards.

What is alt text, and why is it important?

Alt text, short for “alternative text”,  is a written description of an image. It usually appears in the HTML code as a visible line of text next to the image, or as a longer description on a separate page accessed through a link. 

Alt text is incredibly important for people who live with visual impairment – it provides essential context that would otherwise be lost to them. It turns visuals into words, making content more inclusive and easier to navigate.

How alt text improves accessibility and SEO

Alt text was originally created to improve digital accessibility, and that remains its most important role today. For blind and low-vision users, screen readers use alt text to describe images aloud, helping them navigate and understand visual content.

But alt text doesn’t only serve assistive technology. When written well, it also contributes to better SEO.

That’s because search engines can’t “see” images. They depend on alt text, alongside file names, to interpret what an image shows. This means relevant alt text, which uses keywords naturally, can improve how your pages rank in image search results.

6 best practices for writing effective alt text

The best alt text is specific, concise, and relevant to the image’s purpose. Here are a few practical tips to guide your writing:

1. Keep it short, but meaningful – Aim for a maximum of one or two clear sentences. You don’t need to include every visual detail, just the elements that matter most.
2. Describe the image in context – Why is this image here? What information is it adding? Your alt text should reflect the role the image plays on the page.
3. Avoid phrases like “image of” or “picture of” – Screen readers already announce that it’s an image, so these intros only create clutter.
4. Use keywords naturally – Never stuff your alt text with keywords. If the image supports your SEO goals, include relevant terms.
5. Don’t add alt text to decorative images – If an image on your page is just there for decorative purposes, it should have a null alt attribute (alt=””), so that screen readers skip it altogether.
6. Add a full stop – Adding a full stop to the end of the alt text helps differentiate it from the rest of the page’s text. It also improves the reading experience for those using screen readers, adding a natural pause.  

By following these best practices, you’ll create alt text that is genuinely helpful for users. To see these principles in action, take a look at the alt text examples below. 

Alt text examples for different types of images

What might surprise you is that not all alt text should be written the same way.

Why? Because different types of images call for different approaches. 

But whether you’re working with graphs, social media content, or product photos, the goal is always the same: describe what matters, in a way that is connected to the context of the image and to support user experience.

Let’s examine how to approach alt copy for each type of image: 

Alt text for informative images

As the name suggests, informative images convey key information that isn’t written elsewhere on the page.

This description focuses on what’s visible and relevant to the context of the image, without overexplaining.

Alt text for decorative images

Decorative images don’t add meaningful content. They’re there purely for aesthetics and should be skipped by screen readers and other assistive technology. 

Use a null alt attribute, like in the example above, so assistive technology can ignore the image and move on.

Alt text for charts and graphs

Charts and graphs convey complex data, which can seem difficult to condense into alt text. 

The answer? Your alt text should simply summarize the key takeaway from the chart or graph.

If there’s more detail, you might want to consider providing a longer description in text nearby or linking to a text alternative.

Alt text for product images

Product images should be described with key visual details that help users understand what’s being sold.

This is especially important for e-commerce accessibility and usability.

Alt text for social media images

Social media is no exception when it comes to writing alt text. When sharing visual content on social channels, include concise but descriptive alt text that describes the image in a way that’s related to the post’s context. 

Most platforms, like X, LinkedIn, and Instagram, now support alt text, so there’s no excuse to skip it – ensuring everyone in the community can access your content. 

Common mistakes to avoid when writing alt text

Even with the best intentions, it’s easy to get alt text wrong. Here are some of the most common pitfalls – and how to avoid them:

1. Writing overly vague descriptions

Alt text like “Image of a graph” or “Photo of a product” offers no useful context. Be specific. What does the graph show? What kind of product is it?

2. Making descriptions too long

Alt text isn’t the place for full-blown essays. Overly detailed descriptions can overwhelm screen reader users and can interrupt flow. Keep it short and sweet – just a few words will work, or two clear, focused sentences at most.

3. Stuffing in keywords

Alt text that’s crammed with keywords and has no real description doesn’t help users or search engines. Remember to focus on clarity first – when the alt text is genuinely useful, you can rest assured that the SEO benefits will follow soon enough. 

4. Repeating surrounding content

If the image caption or nearby text already says the same thing, there’s no need to repeat it in the alt text. Just focus on what the image itself adds.

5. Ignoring functional images

Buttons, icons, and links with images should have descriptive alt text that explains their function, such as “Submit form” or “Download PDF”,  not just “arrow” or “icon.”

6. Forgetting about mobile and social

If you’re managing content across different platforms, make sure the alt text works consistently across the board, including on mobiles and social posts. Accessibility shouldn’t stop at your website.

By avoiding these common mistakes and using the right tools, you’ll get closer to building a more accessible, user-friendly experience.

How to test and optimize alt text for accessibility

Once you’ve written alt text, how do you know it’s working? 

It’s important to test how well your alt text works in practice, both for screen readers and for overall user experience. 

Here’s how to test and improve your image descriptions:

1. Use a screen reader

Try navigating your site with a screen reader like NVDA (Windows) or VoiceOver (macOS). This gives you direct insight into how your alt text is read aloud and whether it makes sense in context.

2. Turn off images in your browser

Disabling images in your browser is a quick way to preview the alt text that appears in place of each visual. It can be a good way to discover descriptions that feel confusing or redundant and need editing.

3. Check for accessibility errors

Use automated tools to help uncover any errors that may affect screen readers, along with other accessibility issues.  

4. Ask real users for feedback

If you have access to testers who use assistive technology, their feedback is the best thing you can get. Ask whether your alt text feels helpful, concise, and consistent – and adjust based on their suggestions. 

5. Review your SEO performance

Once you’ve optimized your alt text, monitor image-related search traffic in Google Search Console. If your images start showing up in relevant results, you’ll know your descriptions are working for search engines too.

Optimizing alt text is an ongoing process, but following these steps will help you stay on track and build a more inclusive digital experience.

Alt text and WCAG compliance guidelines

If you’re aiming to meet accessibility standards, alt text isn’t optional. The Web Content Accessibility Guidelines (WCAG) lay out clear expectations for how images should be handled to support users with visual impairments, including:

• All non-text content must have a text alternative – This is a Level A requirement under WCAG 2.1 (Success Criterion 1.1.1). If an image conveys information, it must include a meaningful text alternative.
• Decorative images should be ignored by assistive tech – If an image doesn’t convey content (such as borders, patterns, or visual embellishments), it should include an empty alt attribute: alt=”” so screen readers skip it entirely, reducing noise.

Meeting these standards helps you create a more inclusive site. And it also could help reduce legal risk, especially for organizations operating in areas where accessibility laws, like the European Accessibility Act, are enforced. 

Small details, big impact

Alt text might be a small detail – but it has a big impact.

It makes your content more inclusive. It helps you meet accessibility standards. It boosts SEO. 

But most importantly, it improves the experience for real people who rely on assistive technology every day. 

By following best practices and avoiding the common mistakes outlined above, you can start making accessibility a natural part of your content process.

The post Using these 6 alt text best practices helps support real accessibility appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Readers with ADHD often face challenges when processing dense text, navigating cluttered layouts, or maintaining focus on long-form content. And while many accessibility conversations focus on visual or mobility impairments, cognitive accessibility is just as essential – and often overlooked.

ADHD-friendly fonts are designed (or selected) with these challenges in mind. They prioritize clarity, reduce visual noise, and help readers stay oriented on the page. The right font won’t “fix” ADHD, of course – but it can support attention, lower cognitive load, and make reading a more comfortable experience.

In this guide, we’ll explore what makes a font ADHD-friendly, the key features to look for, and how to apply best practices in your digital content and designs. Whether you’re a UX designer, developer, educator, or content creator, you’ll learn how to make more inclusive choices that benefit everyone.

How typography affects people with ADHD

Typography plays a surprisingly powerful role in how we absorb and interact with information. For individuals with ADHD, certain typographic choices can either support focus and comprehension or make reading a frustrating experience.

Common reading challenges for people with ADHD

• Difficulty focusing for extended periods: Dense blocks of text, small fonts, or inconsistent layouts can increase mental fatigue.
• Visual crowding: Overly stylized or compact text can blur together and overwhelm the reader, especially in long paragraphs.
• Frequent distraction: If the text lacks clear visual structure, readers with ADHD may struggle to track their place or stay engaged.
• Slower processing: Certain typefaces require more effort to decode, which can increase cognitive load and reduce reading fluency.

Design impacts

• Poor font and layout choices may result in more time spent re-reading, losing a place, or abandoning the content entirely.
• Well-designed typography, on the other hand, can make content easier to scan, follow, and retain – benefiting all users.

Key features of fonts designed for ADHD

While no single font can solve the challenges of ADHD, certain typographic traits can significantly improve readability, reduce distraction, and support sustained attention. 

ADHD-friendly fonts typically share a few important features:

1. Simplicity

Clean, minimal letterforms are easier to process. Avoid overly decorative fonts, which can create unnecessary visual noise.

Helpful fonts: Helvetica, Arial, Calibri
Avoid: Script, cursive, novelty fonts (e.g., Comic Sans, Papyrus)

2. Consistent letter shapes

Fonts that clearly differentiate similar characters (like “I”, “l”, and “1” or “O” and “0”) reduce confusion and help with faster word recognition.

3. Even spacing

Generous letter, word, and line spacing improves clarity and reduces the chance of text appearing too crowded – something that can quickly overwhelm a reader with ADHD.

TIP: Aim for line spacing (leading) of 1.5 or greater for paragraphs of body text.

4. Medium weight

Fonts that are too thin or too heavy can strain the eyes. A medium-weight font – neither too light nor too bold – will offer the best readability.

5. Left-aligned layout

Justified text creates irregular spacing between words, making it harder for the eye to track lines. Left-aligned text maintains consistent spacing and a predictable rhythm.

6. Readable at various sizes

Fonts should be legible even at smaller sizes or when zoomed in – this is important for users who increase text size as a reading aid.

By keeping these features in mind, designers and content creators can begin to create a reading environment that feels calmer, more inviting, and far less cognitively demanding.

Best fonts for ADHD: Top recommendations

Preferences can vary from person to person, but some fonts consistently perform better for readers with ADHD thanks to their clarity, spacing, and simplicity. 

Let’s look at several tried-and-tested options that combine legibility with cognitive friendliness:

1. Verdana

• Designed for on-screen readability.
• Wide spacing and tall lowercase letters improve line tracking.
• Great for body copy and interfaces.

2. Arial

• A clean, sans-serif classic.
• Familiar to most users, with a neutral design.
• Consistent stroke widths reduce visual distraction.

3. Calibri

• The default font used in many digital workspaces.
• Rounded corners and soft curves make it easy on the eyes.
• A good choice for emails, documents, and online reading.

4. Helvetica

• Highly legible, even at smaller sizes.
• Used widely in interface and digital product design.
• Offers clarity without being overly stark.

5. Open Dyslexic

• Designed specifically for people with dyslexia, but helpful for some with ADHD.
• Heavier bottoms on letters reduce flipping and skipping.
• Opinions are mixed, so user testing is important.

6. Lexend

• Scientifically developed to reduce visual stress and improve reading performance.
• Custom spacing and wider letterforms benefit people with ADHD and dyslexia.
• Free to use and available via Google Fonts.

Bonus tip: Use Google Fonts or System Fonts

Stick with web-friendly fonts or those available via Google Fonts. These will ensure consistent rendering across devices and browsers.

Sans-Serif vs. Serif Fonts: Which is better for ADHD?

One of the most common typography questions when designing for cognitive accessibility is whether to use serif or sans-serif fonts. 

While both have their uses, there’s a clear frontrunner when it comes to ADHD-friendly design.

Sans-Serif fonts: the ADHD-Friendly Favorite

Sans-serif fonts – like Arial, Calibri, and Helvetica – tend to be more suitable for people with ADHD. 

Here’s why:

• Cleaner, simpler shapes: Sans-serif fonts lack decorative strokes at the ends of letters, making them less visually complex and easier to process quickly.
• Less visual clutter: The minimalist letterforms reduce distractions on the page.
• Better on screens: Sans-serif fonts typically render more clearly on digital displays, especially at smaller sizes.
• Improved letter recognition: Their straightforward design helps prevent letters from blending together.

Serif Fonts: best used sparingly

Serif fonts – such as Times New Roman or Georgia – include small embellishments or “tails” on the ends of strokes. While they can be elegant and readable in print, they present a few challenges for ADHD readers:

• Increased visual noise: Serifs can add unnecessary complexity, especially in dense paragraphs.
• More difficult tracking: The additional ornamentation can make it harder to follow lines or distinguish similar characters.
• Screen readability issues: On low-resolution screens, serifs can appear blurry or pixelated.

How font size, spacing, and line height impact readability for ADHD

Even the most ADHD-friendly font can fall short if the text layout isn’t thoughtfully designed. Typography isn’t just about which font you choose; it’s also about how you present it. 

For readers with ADHD, spacing and sizing choices can dramatically affect focus, comprehension, and comfort.

Font size: bigger is often better

Small fonts require more concentration and visual effort. For readers with ADHD, this added strain can lead to faster fatigue and frustration.

• Aim for a minimum of 16px for body text on web content.
• Larger fonts (18–20px) are often more readable and reduce cognitive load.
• For headings, use consistent scaling to create clear content hierarchy.

Line height: give the eyes room to breathe

Also known as “leading,” line height determines the vertical space between lines of text. Tight line spacing can make reading feel claustrophobic, while overly wide spacing breaks visual flow.

• Use 1.4 to 1.6x the font size for optimal readability.
• Avoid cramming too many lines into small content areas.

Letter spacing: the unsung hero

Adjusting the space between characters can help with letter recognition and reduce the chance of letters visually merging – especially in readers who are easily distracted or prone to skipping.

• A slight increase in letter spacing (e.g., 0.5px) can improve clarity.
• Avoid fonts with extremely tight or inconsistent kerning.

Paragraph spacing and chunking

Dense blocks of text are overwhelming for many readers, but especially for those with ADHD. Breaking content into smaller, scannable units helps maintain engagement.

• Use clear paragraph breaks to segment information.
• Incorporate bulleted lists, subheadings, and whitespace to support scanning.

TL;DR?

Make it large. Make it spacious. Make it easy to scan. The more mental breathing room your text provides, the easier it will be for ADHD readers to stay focused and absorb your content.

Custom ADHD Fonts: do they really help?

In recent years, several typefaces have been designed specifically to support readers with dyslexia and ADHD. These fonts often feature unique shapes, spacing, and weights meant to improve readability and focus. But do they actually make a difference?

What are ADHD fonts?

ADHD-specific or ADHD-friendly fonts are designed with neurodivergent readers in mind. While there’s more research supporting fonts for dyslexia, many of the same principles (like generous spacing and simplified letterforms) can benefit people with ADHD as well.

Popular examples include:

• OpenDyslexic: Features heavy-weighted bottoms to help prevent letter flipping or confusion.
• Lexend: A font family scientifically designed to reduce visual stress and improve reading performance.
• Read Regular: Designed to improve readability for those with reading challenges, including ADHD.

Do they actually work?

The evidence is mixed. Some studies and user reports suggest that these fonts may reduce reading errors or increase comfort for neurodivergent readers – but others show little measurable impact compared to standard readable fonts like Arial or Verdana.

However, user preference matters. If someone finds a custom ADHD font easier to read, that’s a valid and valuable reason to use it.

Things to consider

• Custom fonts may not always be supported across all devices or browsers.
• Excessive stylization can sometimes create more distractions, not fewer.
• Test custom fonts in real-world settings before committing to them across the site.

Bottom line

Custom ADHD fonts can be helpful, especially when paired with thoughtful formatting and clean design. But they’re not a magic bullet – the key is offering flexibility and using them as part of a broader accessibility strategy.

Best practices for designing ADHD-friendly text

Typography is about the overall reading experience (not just fonts). For people with ADHD, small design decisions can make a big difference in how easily they process and engage with content.

Here are some practical tips to improve readability and reduce cognitive overload:

1. Choose simple, clean fonts

• Use readable sans-serif fonts like Arial, Verdana, or Lexend.
• Avoid ornate or decorative typefaces – they can be distracting and hard to scan.
• Stick to one or two font families throughout your site or document.

2. Use adequate font size

• Aim for a minimum of 16px body text.
• Increase font size for headings and calls to action to create clear visual hierarchy.

3. Adjust line height and spacing

• Set line height (line spacing) to around 1.5x the font size.
• Use generous paragraph spacing to avoid visual clutter.
• Ensure adequate letter and word spacing (tracking) to aid focus.

4. Break Up Text

• Use short paragraphs, bullet points, and subheadings.
• Incorporate white space to give the eyes room to rest.
• Include visual cues (icons, highlights) to guide readers through content.

5. Minimize distractions

• Avoid flashing content, auto-play videos, or fast-moving carousels.
• Use consistent layouts and navigation patterns.
• Reduce clutter and remove non-essential elements from the page.

6. Give users control

• Allow users to adjust font size, contrast, or line spacing if possible.
• Consider offering a “reading mode” or simplified content view.

7. Test with real users

• Whenever possible, test your designs with neurodivergent individuals.
• Collect feedback to refine your content and improve usability.

Conclusion: Designing with ADHD in mind benefits everyone

Typography can be a powerful ally in making content more accessible for people with ADHD. When you prioritize clarity, simplicity, and flexibility, you reduce barriers, not just for neurodivergent users, but for all your readers. 

From font choice and spacing to layout and readability, every design decision can support better focus and comprehension.

By following the guidance in this article, you’ll be one step closer to creating more inclusive, user-friendly digital experiences.

The post Best fonts and text layouts for ADHD appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

But for people with dyslexia, it can feel like navigating a maze. The letters and words are difficult to decipher, and memory, coordination, and organization are affected, too.

Dyslexia affects up to 10% of the population and often makes reading slow, exhausting, and frustrating. Yet one of the simplest ways to support dyslexic readers is often overlooked: 

Font choice.

Typography affects how easily text can be decoded and understood. By choosing dyslexia-friendly fonts and applying thoughtful design practices, you can significantly improve reading experiences for people with dyslexia. 

In a moment, you’ll know why font selection matters, what formatting choices are easier to read, and what the best font for dyslexia is – so your digital content is more accessible. 

What is dyslexia, and how does it affect reading?

Dyslexia is a common neurological difference that affects the way the brain processes written and spoken language. It makes it difficult to recognize, decode, and accurately process words. This means reading, writing, and sometimes speaking can be a struggle.

Dyslexia appears differently in different people. For some, letters and words can appear jumbled, distorted, or upside down. But in general, dyslexics find it difficult to track lines of text and distinguish between similar-looking letters (like b/d or p/q). These obstacles not only reduce comprehension but also make reading mentally draining and frustrating.

Why font choice matters for people with dyslexia

Font choice can be a game-changer for dyslexic readers – making a massive difference to their reading experience. Fonts and typography with certain characteristics can reduce cognitive load, improve readability, and make it easier to distinguish between letters.

By using more accessible fonts, designers, educators, and content creators can remove unnecessary barriers and make their content more accessible.

Key features of dyslexia-friendly fonts

Not all fonts are created equal – especially when it comes to supporting dyslexic readers. Dyslexia-friendly fonts share several key features that minimize confusion and improve readability:

• More spacing – Characters like b/d, p/q, and i/l are easily confused in many fonts. Consistent, even, generous spacing in between letters reduces visual crowding and can help make it easier for dyslexic readers to tell them apart.
• Unique sticks and tails – Because some letters are difficult for dyslexic readers to tell apart, ensuring letters have unique sticks and tails that vary in length helps with recognition.
• Larger size – A larger font size makes letters and words clearer, aiding comprehension.
• Simple, open shapes – Avoiding ornate strokes and unnecessary embellishments prevents letters from blending together or becoming visually overwhelming.
• Weighted bottoms – Adding heavier bottoms to letters helps anchor them on the line.
• Asymmetry – Fonts with asymmetrical letters make it easier to distinguish between commonly confused characters.
• Longer extenders – Extenders are the parts of a letter that extend above or below the line that letters sit on (e.g., p or b). Lengthening them makes each letter more distinct for easier recognition. 

Sans-serif vs. serif fonts: which is better for dyslexia?

When it comes to dyslexia-friendly typography, sans-serif fonts are generally the better choice. Sans-serif fonts –  like Arial, Verdana, and Open Sans – have clean, straightforward lines without the small decorative strokes (serifs) found in serif fonts. This minimalist design helps letters stand out more clearly from one another.

Serif fonts, on the other hand, can make reading harder for dyslexic individuals. The extra details in serifs often cause letters to blur together, increasing the likelihood of confusion and fatigue. 

How font size, spacing, and line height impact readability

Beyond font choice, how you format your text can make a big difference for dyslexic readers. Proper font size, spacing, and line height all help reduce visual stress,  making text easier to process:

• Font size – Larger text, typically 12 to 14 point,  improves readability by making letters more distinguishable.
• Letter spacing (tracking). Increasing the space between letters helps dyslexic readers avoid the crowding effect, where letters seem to run together. Aim for 35% of the average letter width, but be careful not to overdo it, as this can make text less easy to read.
• Word spacing. Slightly increasing the distance between words helps separate them visually, improving comprehension.
• Line height (leading). Increasing line spacing helps readers keep track more easily.
• Paragraph spacing. Adding space between paragraphs breaks text into manageable sections, improving comprehension and navigation through longer content.

Thoughtful adjustments to size and spacing don’t just benefit dyslexic readers; they improve readability and accessibility for everyone, creating a more inclusive and user-friendly experience.

Best fonts for dyslexia: top recommendations

So, what are the best fonts for dyslexia? Dyslexia manifests differently depending on the person, which means no one font will be perfect for everyone. 

That being said, some fonts are more likely to make the reading experience just that little bit easier for them. 

 Below you’ll find a list of recommended options:

• Arial – A clean, widely available sans-serif font with simple letterforms and generous spacing, making it easier to read than many serif fonts.
• Helvetica – A classic sans-serif font with clean, uniform strokes and minimal ornamentation, which can improve legibility for dyslexic readers. However, some find its tight spacing less ideal for longer pieces of text.
• Open Sans – Designed to be legible across different screen resolutions and sizes, Open Sans features clear letterforms and balanced spacing, making it easier for dyslexic readers to distinguish similar characters.
• Verdana – Like Open Sans, Verdana was designed for screen readability, especially for smaller screen resolutions and sizes. Its distinct letters and loose spacing are well-suited to dyslexic readers.
• Tahoma – Similar to Verdana but slightly narrower, Tahoma offers distinct letter shapes that improve character recognition, and is especially suited to formats where a lot of words need to fit into a smaller space.
• Calibri – With rounded, clear letters and generous spacing that can aid legibility, Calibri was designed to make longer pieces of text more readable.
• Century Gothic – A rounded sans-serif font with slightly larger aspects of lettering, it reduces the chances of letter confusion.
• Comic Sans – While often criticized for its informal appearance, Comic Sans’ irregular, clear letter shapes can actually benefit some dyslexic readers.
• Trebuchet – Also designed for easy screen readability, Trebuchet has strong, wide, distinct letterforms and clean lines for greater clarity. 

Custom dyslexia fonts: Do they really help?

Custom fonts designed specifically for dyslexia,  like OpenDyslexic and Dyslexie, aim to make the reading experience easier for those with the condition. 

These fonts use weighted bottoms to stabilize letters, exaggerated character shapes to enhance differentiation, and wider spacing to reduce visual crowding. 

But research on custom dyslexia fonts suggests they might not be effective, with some studies concluding that they offer no significant advantage over well-chosen, standard sans-serif fonts like Arial or Verdana. 

However, because of the highly subjective nature of dyslexia, individual preferences do seem to play a key role: what works well for one dyslexic reader might not help another.

Best practices for designing dyslexia-friendly text

As well as picking a legible font, there are some best practices to keep in mind which can help make text more dyslexia-friendly:

• Avoid all caps – Blocks of uppercase letters are harder to read and can slow comprehension for dyslexic readers.
• Limit italics and underlining – These styles distort letter shapes and can blur words, making them harder to decode.
• Choose high-contrast color schemes – Avoid low-contrast color combinations or busy backgrounds.
• Use left-aligned text – Avoid justified text, which creates uneven spacing that can disrupt reading flow.
• Keep structure clean and clear – Make sure your layouts are clean and uncluttered, avoiding columns, using consistent headings, adding plenty of white space, and including a table of contents for clear navigation.
• Use bullet points and short paragraphs – Breaking information into small, digestible chunks helps readers process and retain content.
• Write for clarity – Use simple language with shorter sentences in the active voice, and avoid double negatives. 
• Provide adjustable text – Where possible, allow users to customize font size, spacing, and color schemes to suit their individual needs. You can do this with our Accessibility Widget.

How to test and optimize fonts for dyslexic readers

When it comes to dyslexia, typography isn’t one-size-fits-all. The best approach is to test different fonts to ensure your design supports the needs of dyslexic users. 

Here’s how to approach testing:

• Gather feedback from dyslexic users – The most valuable insights come directly from people with dyslexia. Share prototypes or sample pages and ask about their reading comfort, speed, and comprehension.
• Run readability tests – Readability testing tools can help you assess overall text complexity, but remember that these don’t evaluate font choice. Pair them with user testing for a complete picture.
• Use screen readers and assistive technology – Test your design with popular assistive tools to ensure compatibility and a smooth experience for all users.
• Continuously improve – Apply feedback and test results to refine your typography and layouts, balancing accessibility with your brand’s style.

By actively testing and optimizing your content, you demonstrate a genuine commitment to accessibility, giving dyslexic readers the support they need to engage confidently with your content.

From frustration to comfort

The right typography can make the difference between a frustrating reading experience and a comfortable one. By understanding how dyslexia affects reading, choosing supportive fonts, and applying best practices when setting out your content, you can create an experience that’s inclusive, accessible, and more enjoyable for your audience.

Designing with dyslexic users in mind is a commitment to cognitive accessibility, benefiting millions of people worldwide. And, given that it will widen your audience reach,  it’ll benefit your business too. 

The post Best font for dyslexia: How to choose fonts that empower every reader appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

But millions of people still face barriers when interacting with digital tools due to physical, sensory, or cognitive impairments. This is where assistive technology comes in – a powerful category of tools and devices designed to bridge the gap and empower users of all abilities to engage with content, communicate, and participate fully in digital spaces.

From screen readers and braille displays to speech recognition software and ergonomic keyboards, assistive technologies come in many forms. Some support users with permanent disabilities, while others assist people with temporary or situational limitations, like recovering from surgery or navigating a noisy environment.

As global awareness of digital inclusion grows, so does the importance of understanding how assistive technology works and how it can be integrated into websites, classrooms, workplaces (and beyond). 

In this article, we’ll break down:

• What assistive technology is and how it benefits users
• Real-world examples across a range of disabilities
• Use cases in education and employment
• Emerging trends to watch
• How to choose the right tools for your audience or organization

Let’s dive in – and explore how technology can be a force for inclusion.

How assistive technology helps people with disabilities

Assistive technology (AT) is about independence, dignity, and equal opportunity. These tools enable people with disabilities to perform functions that might otherwise be difficult or impossible, improving quality of life and opening access to education, employment, and online services.

Empowering independence

Whether it’s a blind person using a screen reader to shop online, or someone with mobility limitations navigating a website via voice control, assistive technology enables users to complete tasks on their own – often without needing additional help.

Enhancing communication

Tools like speech-generating devices (SGDs), real-time captioning, and hearing aids allow people with communication barriers to engage in conversations, both in person and online. This is crucial in educational and workplace settings where clear communication is make or break.

Leveling the playing field

In both education and employment, AT helps make sure that people with disabilities can compete and collaborate on equal footing. For example, students with dyslexia may benefit from text-to-speech software, while an employee with limited dexterity may rely on adaptive keyboards or eye-tracking technology.

Supporting digital access

As more services move online, it’s vital that digital environments accommodate assistive tech – from compatibility with screen readers to customizable text sizes and keyboard-friendly navigation. AT can only be effective if web content and digital tools are designed with inclusion in mind.

Adapting to changing needs

Assistive technology can also support people with temporary injuries, age-related impairments, or situational challenges – such as using captions in a noisy space. In this way, AT benefits a much broader population than many realize.

Examples of assistive technology for visual impairments

People with visual impairments – from low vision to complete blindness – rely on a wide range of tools to interact with digital content. These technologies translate visual information into formats that can be heard, touched, or enlarged.

Screen readers

Screen readers convert on-screen text into synthetic speech or braille output. Popular options include:

• JAWS (Job Access With Speech) – widely used in professional environments.
• NVDA (NonVisual Desktop Access) – a free, open-source alternative.
• VoiceOver – built into macOS and iOS.
• TalkBack – available on Android devices.

Braille displays

These devices render text as tactile braille characters. Dynamic refreshable displays allow users to “read” digital content line by line, often working alongside screen readers.

Magnification software

For users with low vision, screen magnifiers (like ZoomText or native tools like Windows Magnifier) enlarge parts of the screen. 

Features often include:

• Adjustable zoom levels
• Enhanced contrast settings
• Cursor enhancements

Text-to-speech tools

While often grouped with screen readers, standalone TTS tools like NaturalReader or Read Aloud browser extensions help users with partial vision or fatigue listen to content at their own pace.

High-contrast and inversion modes

Operating systems and browsers frequently offer display enhancements, such as dark mode or high-contrast color schemes, making text easier to read for users with light sensitivity or reduced contrast perception.

For your digital content to be truly accessible, it must be compatible with these technologies – from ensuring correct label markup to avoiding text baked into images.

Examples of assistive technology for hearing impairments

For individuals who are deaf or hard of hearing, assistive technology means better access to auditory content – from conversations to multimedia – through visual and tactile alternatives.

Real-time captioning tools

Live captioning converts speech to text on the fly. It’s especially valuable for:

• Video conferencing (e.g., Google Meet, Zoom, Microsoft Teams all offer built-in captions)
• Live events (via CART services: Communication Access Real-Time Translation)
• Streaming platforms (like YouTube’s auto-captions or third-party services)

Subtitling and transcription software

Transcripts and subtitles make audio and video content accessible. Tools like Otter.ai, Rev, and Descript help create readable versions of spoken content, useful in both educational and professional settings.

Visual alert systems

Devices like flashing doorbells, visual fire alarms, and vibrating pagers offer non-auditory notifications. On websites, visual cues for sounds (like “ding” when a message is sent) improve the user experience for everyone.

Sign language interpretation technology

Video relay services (VRS) and interpretation apps like InterpreterNow and SignLive connect users with interpreters via video, helping bridge communication gaps in real-time settings.

Hearing aid-compatible technology

Modern hearing aids now integrate with:

• Bluetooth for direct audio streaming
• Telecoils for improved sound in public venues
• Smartphone apps for sound filtering and environmental control

TIP: Audio content on websites should always be accompanied by transcripts or alternative formats. Not all users benefit from amplification – many need a visual version.

Examples of assistive technology for mobility challenges

People with mobility impairments may experience difficulty using standard input devices like keyboards, mice, or touchscreens. Assistive technology helps them interact with digital content in ways that suit their physical abilities.

Alternative input devices

These tools replace or supplement traditional hardware:

• Mouth sticks and head wands allow users to press keys or touchscreen elements with head or mouth movements.
• Foot switches and sip-and-puff systems enable interaction using air pressure or foot motion.
• Joystick mice offer greater control for users with limited dexterity.

These tools are often customized to individual needs, improving both autonomy and speed.

Voice control and speech recognition

Software like Dragon NaturallySpeaking, Apple Voice Control, and Google Assistant lets users navigate, dictate, and interact with devices entirely hands-free. This technology is especially helpful for users with limited or no use of their arms and hands.

TIP: Make sure your website or app is compatible with voice commands and doesn’t require complex gestures to operate.

On-screen keyboards

These allow typing using:

• A mouse
• Eye tracking
• Switch controls

Available on most operating systems, on-screen keyboards are especially useful when paired with pointer tools or gaze tracking.

Switch-access systems

Switches offer simplified interaction by mapping multiple commands to a single button or sequence. 

They can be activated with:

• Head movements
• Shoulder taps
• Blinking (via sensors)

These systems are often used alongside screen readers or scanning software that cycles through options.

Ergonomic and adaptive hardware

Custom setups include:

• Split keyboards, trackballs, and vertical mice
• Adjustable desks and mounts for optimal device positioning
• Touch-free access options using eye gaze technology (like Tobii Dynavox)

Developer tip: Make sure all interactive components (e.g., form fields, buttons) are keyboard-accessible and support focus indicators.

Examples of Text-to-Speech (TTS) tools

Tools like NaturalReader, Kurzweil 3000, and Read&Write by Texthelp convert written content into audio, helping users with dyslexia or reading difficulties absorb information more easily. These tools often include synchronized highlighting, improving word recognition, and focus.

Screen masking and focus tools

These help reduce on-screen distractions by dimming irrelevant areas or guiding the eye line. 

Examples include:

• Visor (browser extension)
• BeeLine Reader (uses color gradients to help tracking)
• Focus@Will (supports attention through soundscapes)

Useful for: users with ADHD, visual processing disorders, and executive function challenges.

Mind mapping and visual organizers

For users who struggle with linear note-taking or abstract planning, visual mapping tools can help structure information:

• MindMeister
• Inspiration Maps
• Coggle

These tools are great at offering support for joining the dots for complex auditory information

Assistive technology in education

Inclusive education means empowering every student, regardless of ability, to participate fully in the learning process. Assistive technology is a critical enabler, especially for students with disabilities. When integrated thoughtfully, it enhances learning outcomes, independence, and engagement.

Key use cases across disability types

For students with visual impairments:

• Screen readers (JAWS, NVDA) provide spoken descriptions of digital content.
• Braille displays allow reading and writing through tactile input.
• Accessible e-textbooks offer reflowable, alt-text-equipped formats.

For students with hearing impairments:

• Captioning services (e.g., Otter.ai, Google Meet captions) ensure access to spoken content.
• Visual learning tools support comprehension through imagery and text-based resources.

For students with motor disabilities:

• Alternative input devices like adaptive keyboards or switch controls support writing and navigation.
• Voice dictation tools (Dragon Naturally Speaking and Google Voice Typing) enable speech-based interaction.

For students with cognitive disabilities:

• Text simplification tools (Rewordify, SMMRY) and TTS tools support literacy and comprehension.
• Scheduling apps and visual organizers help with time management and executive function.

Accessibility features in learning platforms

Most major learning management systems (LMS) like Moodle, Blackboard, and Canvas now include built-in accessibility tools such as:

• Adjustable font sizes and contrast
• Keyboard navigation support
• Captioning and transcript tools

Educators can enhance accessibility by providing:

• Multiple content formats (e.g., video + transcript)
• Structured documents with headings
• Alt text for all visual materials

TIP: When designing digital learning materials, apply Universal Design for Learning (UDL) principles – offering multiple means of representation, engagement, and expression.

Assistive technology in the workplace

Workplaces that embrace assistive technology not only support employees with disabilities – they also unlock productivity, inclusivity and innovation. With the right tools and culture, everyone can contribute meaningfully.

Key use cases by disability type

Visual impairments:

• Screen readers (JAWS, VoiceOver, NVDA) allow employees to interact with software, emails, and documents.
• Screen magnifiers (ZoomText, Windows Magnifier) assist with reading and on-screen navigation.
• Accessible email clients and intranet tools with keyboard navigation and alt-text support ensure inclusive communication.

Hearing impairments:

• Real-time transcription tools (Otter.ai, Microsoft Teams captions) improve meeting accessibility.
• Video conferencing with live captions or interpreters ensures equal participation.
• Visual notifications replace audio alerts in workplace systems.

Motor disabilities:

• Speech recognition software (e.g., Dragon, Windows Speech Recognition) for hands-free computing.
• Adaptive input devices like ergonomic keyboards, head pointers, and eye-tracking systems.
• Customizable workstations for physical comfort and accessibility.

Cognitive disabilities:

• Task automation and reminder tools (e.g., Trello, Asana) for executive function support.
• Distraction-reducing apps (like Focus@Will or Freedom) to enhance concentration.
• Simplified interfaces and consistent layouts reduce cognitive load.

Employer responsibilities and best practices

• Conduct accessibility audits for internal systems and tools.
• Offer accommodations proactively – through HR processes or inclusive design from the outset.
• Train teams on digital accessibility, including how to create accessible documents, presentations, and emails.
• Integrate assistive technologies as standard options – not exceptions.

How to choose the right assistive technology

With so many tools available, selecting the right assistive technology can feel overwhelming. The key is to align the solution with the individual’s unique needs, context, and preferences – not just the disability category.

1. Start with the user’s goals

• What tasks or environments are most challenging?
• Is the goal communication, navigation, education, employment, or daily independence?
• Consider both short-term needs (e.g., exams, work apps) and long-term adaptability.

2. Assess needs and try solutions

• Needs assessments (conducted by AT specialists or therapists) help match tools to abilities and context.
• Trial periods or demos let users test tools before committing.
• Involving the user in the decision-making process is critical for long-term success.

3. Think about these key elements

• Compatibility: Will it work with the user’s current devices, browsers, or platforms?
• Ease of use: Is the interface intuitive and customizable?
• Support and training: Are tutorials, help guides, or community support available?
• Cost and funding: Are grants or employer/educational reimbursements available?

Pro tip: Remember that needs evolve. The right solution today may need adjusting tomorrow. Flexibility is key.

The post Assistive technology examples: Tools that empower access appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

From helping visually impaired individuals navigate websites to supporting neurodivergent learners in educational settings, TTS plays a vital role in building an inclusive digital world.

As digital content continues to multiply across platforms and devices, making sure that information is accessible to all users is no longer optional. Assistive technologies like TTS are essential components of accessibility compliance under global standards such as the Web Content Accessibility Guidelines (WCAG) and the European Accessibility Act (EAA). But despite this importance, many organizations still don’t fully understand how TTS works, or how to optimize their content so that it’s truly accessible when read aloud by machines.

This article breaks down what TTS technology is, how it supports users with different abilities, and what you can do to keep your digital content working effectively. You’ll find implementation tips, real-world examples, and practical guidance that helps you build better, more inclusive experiences for every user.

What is Text-to-Speech (TTS) assistive technology?

TTS assistive technology is software that converts digital text into spoken words. It reads content aloud from screens, whether it’s a paragraph on a website, an email, or a menu in an app, allowing users to consume information audibly instead of visually.

Unlike screen readers, which provide complex navigation and interaction capabilities for blind users, TTS tools focus on voice output alone. 

They’re used by a broad range of people: not just those with disabilities, but also anyone who benefits from auditory learning, multitasking, or reduced screen time.

TTS systems can be built into devices (like iOS VoiceOver or Android’s Select to Speak), embedded in websites and apps, or installed as standalone software or browser extensions. 

High-quality TTS software often includes:

• Natural-sounding synthetic voices
• Multi-language and dialect support
• Speed and pitch controls
• Word and sentence highlighting while reading
• Compatibility with different content types (e.g., PDFs, HTML, eBooks)

TTS has become more sophisticated thanks to advances in AI and natural language processing, allowing voices to sound more human and less robotic, enhancing both comprehension and user experience.

How Text-to-Speech technology works

TTS technology follows a relatively straightforward process, but under the hood, it relies on sophisticated linguistic, computational, and audio processing techniques to deliver a natural listening experience.

1. Text analysis

The software begins by analyzing the raw text input. It breaks sentences into smaller units, identifies punctuation and grammatical structure, and prepares the content for speech conversion. This stage also includes normalization – for instance, turning “€10” into “ten euros” or “Dr.” into “doctor.”

2. Linguistic processing

Next, the TTS engine applies phonetic rules and natural language processing (NLP) to determine how each word should be pronounced. 

This step is essential for:

• Handling homographs (e.g., “lead” as in “to guide” vs. “a metal”)
• Adjusting intonation based on sentence type (statement vs. question)
• Focusing on correct stress and rhythm in multi-syllable words

3. Speech synthesis

Once the text is linguistically parsed, the engine generates speech using one of two main approaches:

• Concatenative synthesis: Strings together pre-recorded fragments of human speech.
• Neural or parametric synthesis: Uses deep learning to generate speech from scratch (e.g., Google’s WaveNet, Amazon Polly). This approach produces more natural and expressive voices.

4. Audio output

The final output is a spoken voice rendered through speakers or headphones. Advanced tools also include highlighting, allowing users to follow along visually as the text is read aloud – an important feature for improving literacy, attention, and comprehension.

Modern TTS engines are increasingly integrated into platforms, browsers, and operating systems, making the technology more accessible than ever. As capabilities expand, understanding these mechanics helps content creators and developers design experiences that support – rather than hinder – spoken interaction.

Who benefits from TTS assistive technology?

TTS isn’t just a tool for people with permanent disabilities. Its versatility makes it valuable across a wide range of user needs, contexts, and industries. 

Here’s a breakdown of who benefits most:

1. Individuals with visual impairments

For blind and low-vision users, TTS provides vital access to digital content. It allows them to consume information on websites, documents, and applications without needing to rely on visual cues.

• Example: A screen reader using TTS can read out webpage content, including headings, buttons, and links, enabling independent web navigation.

2. People with dyslexia or other reading disabilities

TTS helps decode complex or unfamiliar words, easing cognitive load and improving reading comprehension.

• Example: A student with dyslexia may use TTS to follow along with assigned readings, improving retention through dual auditory and visual input.

3. Individuals with ADHD or memory challenges

TTS can help users maintain focus and reinforce understanding by presenting content in a different sensory format.

• Example: Hearing a passage read aloud can support working memory and reduce distractions for people with attention difficulties.

4. Non-native language speakers

TTS offers clear pronunciation and pacing, aiding language learners and multilingual users.

• Example: A website visitor unfamiliar with written English may prefer listening to content rather than reading it.

5. People with motor disabilities

For users with limited mobility or dexterity, TTS allows for hands-free content consumption – especially useful when used with voice control or keyboard navigation.

• Example: A user with a tremor may find it easier to navigate using a screen reader and listen to content rather than scroll and click.

6. Mobile and situational users

Even users without any disability can benefit from TTS in specific contexts, such as multitasking, driving, or exercising.

• Example: A commuter may use TTS to listen to an article during a train ride instead of reading on a small screen.

The bottom line is that TTS technology makes digital content more inclusive, usable, and versatile for everyone, not just those with diagnosed disabilities.

Key features of effective TTS software

Not all TTS tools are created equal. While basic versions can read text aloud, the most effective TTS software includes a range of features designed to improve clarity, control, and user experience – especially for individuals who rely on it daily.

1. Natural-sounding voices

Modern TTS engines use neural networks and deep learning to simulate human speech patterns. 

You need to look for tools that offer:

• Expressive intonation
• Appropriate pacing and rhythm
• Regional accents or multilingual support

2. Customizable playback settings

Different users need different speeds, tones, and reading styles. 

Quality TTS tools allow users to:

• Adjust reading speed (slower for comprehension, faster for skimming)
• Modify pitch or emphasis
• Choose between male/female or child/adult voices

3. Highlighting and word tracking

Highlighting text as it’s read helps users follow along visually. 

This is especially helpful for:

• Users with dyslexia or reading difficulties
• Language learners building reading fluency

4. Pronunciation control

Advanced TTS software allows for customization of tricky words, acronyms, or brand names – especially important for:

• Medical or technical content
• Multilingual websites
• Company or industry-specific terms

5. Compatibility with assistive technologies

Effective TTS tools integrate well with:

• Screen readers (like NVDA, JAWS, VoiceOver)
• Browsers and mobile apps
• Learning management systems (LMS)

6. Offline or cross-platform use

Some users need TTS access on the go, in low-bandwidth settings, or across different devices. 

You need to look for tools that support:

• Offline playback
• Cloud syncing of preferences and settings
• Browser extensions and mobile apps

Best TTS tools and software

Whether you’re designing a website, building educational tools, or crafting inclusive workplace policies, selecting the right TTS technology is essential. 

We’ve curated a list of the top-performing TTS tools, ranging from enterprise-level platforms to consumer-friendly apps.

1. Screen reader TTS engines

These tools are integrated with screen readers used by millions of people with visual and cognitive disabilities.

• JAWS (Job Access With Speech)
  – Industry standard for Windows users with vision loss
  – Highly customizable voice profiles and shortcut commands
  – Common in government and enterprise settings
• NVDA (NonVisual Desktop Access)
  – Open-source, free for Windows
  – Uses eSpeak or can integrate with premium voices like Vocalizer
• VoiceOver (macOS/iOS)
  – Built into all Apple devices
  – Includes high-quality voices with natural cadence
  – Syncs user settings across devices via iCloud
• TalkBack (Android)
  – Android’s native screen reader
  – Supported by Google’s speech services
  – Works well with Braille displays and other ATs

2. Standalone TTS applications

These tools are used for reading websites, documents, or books aloud, even by users without disabilities.

• NaturalReader
  – Supports PDFs, Docs, emails, and web pages
  – Offers offline mode and AI voices
  – Suitable for education and general productivity
• Read Aloud (Chrome/Edge Extension)
  – Free browser extension for reading web content
  – Supports multiple languages and speech engines
  – Popular with casual users and students
• Speech Central
  – Cross-platform TTS for Windows, macOS, iOS
  – Can read RSS feeds, websites, and books
  – Useful for professionals and language learners

3. Cloud-based and developer APIs

These are ideal for integrating TTS into apps, platforms, and digital products.

• Google Cloud Text-to-Speech
  – Over 220 voices in 40+ languages
  –  Offers WaveNet natural voice synthesis
  – Widely used in education, telehealth, and IoT devices
• Amazon Polly
  – Real-time and batch TTS support
  – Neural TTS (NTTS) options for lifelike speech
  – Integrates with Alexa, learning apps, and accessibility tools
• IBM Watson Text to Speech
  – Enterprise-grade security and scalability
  – Supports SSML (Speech Synthesis Markup Language) for custom pronunciation
  – Suitable for healthcare and enterprise solutions

TTS for web accessibility and inclusion

When integrated thoughtfully, TTS can dramatically enhance how users interact with websites, apps, and digital platforms.

Why TTS matters for accessibility

TTS plays a vital role in ensuring compliance with accessibility laws such as the Web Content Accessibility Guidelines (WCAG) and the European Accessibility Act (EAA). Specifically, it supports:

• Perceivability: Helps users perceive content regardless of visual or cognitive ability.
• Operability: Offers alternative methods of accessing content for those who struggle with manual input or screen reading.
• Inclusivity: Makes digital services more usable for individuals with literacy challenges, second-language users, and aging populations.

Globally, over 2.2 billion people have some form of visual impairment (WHO, 2023). TTS makes information accessible to many of them.

Common applications of TTS in web accessibility

• Screen readers: These tools convert everything on a web page – text, buttons, menus – into spoken content.
• Accessible document readers: PDFs or Word docs with accessible formatting are read aloud using TTS tools.
• Audio guidance for forms: Well-structured labels and instructions read via TTS can improve form usability.
• Dynamic content alerts: ARIA live regions allow updates (like error messages) to be announced in real-time.

Best practices for TTS-friendly websites

• Use semantic HTML: Structure your site with clear headings (<h1>–<h6>), paragraphs (<p>), and landmarks (<nav>, <main>, <footer>) to help TTS parse the content.
• Label everything: Buttons, form fields, and links should all have proper aria-label, alt, or visible text.
• Avoid auto-playing audio: It can interfere with screen readers and confuse users relying on TTS.
• Ensure keyboard navigation: TTS users often rely on keyboard shortcuts – your site should support smooth tabbing and focus.

Tip: Use tools like Lighthouse or axe DevTools to test how TTS interacts with your site.

Applications of TTS in education and the workplace

TTS technology has moved far beyond its original use cases and now plays a pivotal role in enabling access to information in both educational and professional settings. Its flexible, multimodal delivery of content can boost inclusion, productivity, and learning outcomes for a broad range of users.

Education: Leveling the learning field

In classrooms and remote learning environments, TTS can:

• Support learners with reading or visual impairments by reading assignments, textbooks, and test instructions aloud.
• Help with comprehension for students who struggle with decoding written text – especially useful for learners with dyslexia, ADHD, or ESL (English as a second language) backgrounds.
• Encourage independent study by allowing students to listen to notes, handouts, and digital materials at their own pace.
• Reinforce auditory learning styles, helping students who absorb information better when it’s spoken rather than read.

Example: A student with dyslexia may use TTS to review homework instructions while following along with the text visually, increasing understanding and retention.

The workplace: supporting focus and productivity

TTS tools have also found their place in the modern workplace, especially as organizations move toward more inclusive digital environments. 

In this context, TTS can:

• Enable accessibility compliance in internal communications, training modules, and HR systems.
• Assist neurodivergent employees who may find spoken instructions easier to follow than dense documentation.
• Reduce cognitive load by allowing employees to “read” long reports or policy documents while multitasking.
• Facilitate productivity on the go, making it easier to absorb content during commutes or while completing manual tasks.

TTS is particularly valuable in hybrid or remote work settings, where digital content needs to be as inclusive and flexible as possible.

By integrating TTS features into their learning platforms and workplace tools, organizations create more equitable experiences and help people thrive – regardless of ability or preferred learning mode.

The challenges and limitations of TTS technology

While TTS technology offers immense benefits for accessibility and inclusion, it’s not without limitations. Understanding these challenges is essential for optimizing content and setting realistic expectations for users and implementers.

1. Lack of human-like nuance

Even the most advanced TTS engines can struggle to replicate the intonation, emotion, and rhythm of human speech. This can make the output sound robotic or monotonous, especially in long-form content or emotionally charged material.

• Impact: May reduce engagement or make it harder for users to interpret tone or emphasis.
• Mitigation: Choose TTS tools with natural-sounding voices and support for SSML (Speech Synthesis Markup Language) to control pitch, pauses, and pronunciation.

2. Contextual misinterpretation

TTS systems may mispronounce homographs (e.g., “lead” the verb vs. “lead” the metal), acronyms, or unusual proper nouns, especially without context clues or phonetic guidance.

• Impact: Could lead to confusion or misinformation.
• Mitigation: Use SSML or pronunciation guides in structured content when needed, and test outputs before publishing.

3. Language and dialect limitations

Although TTS supports an increasing number of languages and accents, coverage can still be limited for:

• Minority or regional languages
• Non-standard dialects
• Multilingual documents or websites
• Impact: May exclude users who speak less-common languages or rely on mixed-language content.
• Mitigation: Choose multilingual TTS providers and make sure fallback content or translations are available.

4. Compatibility and integration gaps

Not all websites, apps, or documents are designed with TTS users in mind. Poor semantic structure, missing alt text, or inaccessible navigation can reduce the effectiveness of TTS tools, even if the tools themselves are robust.

• Impact: Frustrating user experience, particularly for screen reader users.
• Mitigation: Apply accessible development practices, use semantic HTML, and test TTS compatibility across platforms.

5. Privacy and data security concerns

Some cloud-based TTS tools may require sending user input or personal data to third-party servers for processing.

• Impact: May raise compliance concerns under privacy regulations like GDPR.
• Mitigation: Select TTS solutions with transparent privacy policies and on-device processing options where necessary.

Final thoughts

Text-to-speech assistive technology is a powerful tool for promoting accessibility, inclusion, and digital equality. But it only works when paired with thoughtful content and accessible design practices. Whether you’re a developer, content creator, educator, or product leader, taking steps to make your content TTS-friendly can open digital doors for countless users.

By adopting inclusive content strategies, testing with real users, and selecting TTS-compatible platforms, you help make sure that everyone – regardless of ability – can engage with your content fully and independently.

The post Creating content for everyone: A guide to Text-to-Speech assistive technology appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

That’s the problem of poor color contrast in action. 

Color is a beautiful thing, with a whole spectrum to pick from – but for millions of people with visual impairments, that same rainbow can be a daily barrier. 

Think of color contrast like the volume dial on your content’s clarity. Turn it down too low, and your message gets lost, especially for those with visual impairments. 

And yet, many websites still fall short, using color combos that make content hard to read or interact with.

In this guide, we’ll break down exactly what color contrast accessibility means, why it matters, and what changes you can make to your site to get it right. 

What is color contrast accessibility? 

Color contrast accessibility refers to using color combinations that provide sufficient contrast between text (or other foreground elements) and the background. 

It plays a big role in making digital content readable and accessible for everyone, especially those with visual impairments such as color blindness and low vision. Without having the right contrast, important content can become difficult, or even impossible in some cases, to read. 

Why does color contrast matter for accessibility?

Poor color contrast is one of the most common and overlooked accessibility issues in digital design.

When contrast isn’t balanced properly:

• Users with color vision impairments may not be able to distinguish text or interface elements
• People with low vision may struggle to read small or light text
• Mobile users in bright environments may have trouble seeing content 

Who benefits from proper color contrast?

Improving color contrast isn’t just a simple matter of meeting legal requirements, although that is important. It’s also about being able to improve the user experience for a wide range of people, including:

• Users with visual impairments (color blindness, cataracts, glaucoma, etc.) 
• Older users with age-related vision changes
• Mobile users viewing content in sunlight
• Anyone experiencing fatigue or distraction 

Accessible color contrasts benefit everyone. They make content clear, easier to engage with, help widen your audience, but also, things just look better, and what’s not to like about that?

WCAG guidelines for color contrast

 The Web Content Accessibility Guidelines (WCAG) provide clear guidelines for color contrast accessibility. 

They state:

• Minimum contrast ratio: Text and background color combinations must have a contrast ratio of at least 4.5:1
• Large text: For 18pt or 14pt bold, the minimum contrast ratio is 3:1
• UI elements and graphical objects: These should have a contrast ratio of 3:1 against adjacent colors 

By following this criteria, you can make sure all of your site users can see content clearly, no matter their visual ability. 

Common color contrast issues and their impact

Even when teams are fully clued into contrast issues and have good intentions, issues can still slip through the cracks – especially during the rush of product development or visual branding. 

Understanding the most common pitfalls can help you catch them early and build more inclusive designs from the ground up. 

Typical issues can include:

• Light gray text on white backgrounds
• Low contrast buttons and links
• Using color alone to convey information (e.g., red for errors)

These common, yet avoidable mistakes can lead to things such as:

• Increased user frustration
• Higher bounce rates
• Legal compliance risks 

Best practices for designing with accessible color contrast

Good design is about aesthetics, of course. But it’s also about function and inclusion.

When it comes to color contrast, a few intentional choices can go a long way toward making your content readable for everyone. 

Here’s how to build accessibility into your design right from the start: 

• Use high-contrast color combinations: Dark text on a light background or vice versa
• Avoid relying solely on color to communicate: Use icons, labels, or underlines for clarity
• Test your palette early: Check contrast ratios before finalizing your design elements
• Be mindful of branding colors: Adjust shades if necessary to meet contrast requirements 

Top color contrast checkers and testing tools

Designing with accessibility in mind should never be about guesswork.

There are a number of different tools that take any mystery out of contrast compliance, giving you clear feedback and actionable suggestions.

Here are a few helpful tools you can use to test and improve your color contrast: 

• WebAIM Contrast Checker: A simple tool that lets you input text and background colors to instantly check contrast ratios
• Accessible Colors (by Material Design): Helps designers choose accessible color palettes that work well within Material Design standards
• Tanaguru Contrast-Finder: Suggests compliant color alternatives when your original choices don’t meet accessibility thresholds
• Color Contrast Analyzer (by TPGi): A downloadable tool that tests contrast on web pages and software interfaces, including visual simulations

How to fix poor color contrast in websites and apps

Spotted a contrast issue? Not to worry, they’re usually a quick fix. 

Whether you’re updating a single button or reworking your entire color scheme, these steps will help you bring your contrast up to standard. 

If your audit reveals issues:

• Adjust foreground or background colors to meet the required ratio
• Use semi-transparent overlays or shading to improve contrast
• Reconsider font size and weight for better legibility
• Use automated tools to retest and validate changes

Legal requirements for color contrast compliance

Beyond usability, color contrast has legal weight. As accessibility regulations tighten worldwide, making sure you have compliant contrast ratios is essential, not optional.

Several global laws and standards emphasize color contrast as a key part of accessibility:

• ADA (US): Enforced under Title III for public digital spaces
• WCAG: Internationally recognized technical standard
• EAA (EU): Requires accessibility for many digital services by 2025

Color contrast makes or breaks accessibility

Color contrast accessibility plays a huge role in shaping an inclusive and legally sound experience of an inclusive and legally compliant digital experience. 

By understanding the rules, testing your content, and applying thoughtful design practices, you can make your site more readable, more user-friendly, and more future-proof.

Frequently asked questions

The post Color contrast accessibility: What it is and how to get it right appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

The post Test post appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Conosci le 5 trappole della conformità?

Non sempre è facile capire se il tuo sito è conforme alle normative sulla privacy. Guarda il video di Andrea Giorgi, esperto web e di AI, ti spiegherà le 5 trappole più comuni e come evitarle con iubenda.

Non sei ancora sicuro che il tuo sito web sia a norma? Usa il nostro scanner e ricevi un report completo sul tuo tasso di compliance.

Scansiona ora

“Se anche tu lavori in un team smart e non sopporti di aggiornare la privacy policy ogni volta che aggiungi del codice al tuo sito, allora iubenda fa per te. È incredibilmente conveniente e super facile da utilizzare.”

Oltre 400.000

siti web conformi
con iubenda

Le 5 trappole più comuni

1

Cookie banner non conforme

Se il tuo cookie banner non ha il tasto “Rifiuta” ben visibile o se non blocca i cookie prima del consenso, rischi sanzioni.

2

Privacy policy incompleta o assente

La privacy policy deve riflettere davvero le tecnologie e i servizi che usi sul sito; copiare un modello da internet non è sufficiente.

3

Nessun registro dei consensi

Se un utente ti dà il consenso all’uso dei cookie o alla ricezione di newsletter, devi poterlo dimostrare in caso di controlli.

4

Mancata conformità alle normative internazionali

Hai visitatori dagli Stati Uniti, Regno Unito o Brasile? Oltre al GDPR, ci sono leggi locali da rispettare come il CCPA o la LGPD.

5

Nessun aggiornamento alle nuove leggi

Le normative cambiano di continuo. Se non aggiorni il cookie banner e le policy alle ultime regole, rischi multe anche se in precedenza eri conforme.

Scopri subito se sei caduto in una trappola

La soluzione: iubenda

Scanner automatico

In pochi clic, iubenda analizza il tuo sito e ti dice esattamente cosa devi sistemare.

Generazione automatica di cookie banner e privacy policy

Senza scrivere alcun codice, tutto personalizzabile e aggiornato automaticamente.

Registro dei consensi integrato

Tutti i consensi vengono raccolti e archiviati nel rispetto delle normative.

Supporto multi-legislazione

Se il tuo sito è visitato da utenti di altri paesi, iubenda si adatta automaticamente alle principali legislazioni.

Auto-aggiornamenti legali

Le leggi cambiano? Tutte le soluzioni iubenda si aggiornano in autonomia.

---

iubenda è valutato 4.5 su 5 su Trustpilot

Tommaso D.

Sviluppatore iOS senior

“È una buona piattaforma per gestire consenso e cookie policy. Il loro supporto è davvero ottimo.”

Federico F.

Sviluppatore iOS senior

“Per la conformità al GDPR, ho provato altri software simili. Dopo 2 anni, sono passato a iubenda perché copre tutto e non devo più usare tanti strumenti per soddisfare i diversi requisiti.”

Per non cadere in tutte queste trappole, affidati a iubenda

Effettua una scansione gratuita e scopri subito il livello di conformità del tuo sito.

Proteggi il tuo sito e il tuo business con iubenda

The post Conosci le 5 trappole della conformità? appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> https://www.iubenda.com/en/help/182511-guide-complet-de-la-conformite-a-la-lea-pour-les-services-numeriques/ Thu, 05 Jun 2025 17:01:36 +0000 https://help.iubenda.com/?p=182511 Ce que la Loi Européenne sur l’Accessibilité signifie pour vos opérations numériques L’accessibilité numérique n’est plus un ajout, c’est une obligation légale pour de nombreuses entreprises opérant en Europe. La Loi Européenne sur l’Accessibilité (EAA), qui entrera en vigueur le 28 juin 2025, introduit un ensemble uniforme de exigences d’accessibilité pour les sites web, les […]

The post Guide complet de la conformité à la LEA pour les services numériques appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> Ce que la Loi Européenne sur l’Accessibilité signifie pour vos opérations numériques

L’accessibilité numérique n’est plus un ajout, c’est une obligation légale pour de nombreuses entreprises opérant en Europe.

La Loi Européenne sur l’Accessibilité (EAA), qui entrera en vigueur le 28 juin 2025, introduit un ensemble uniforme de exigences d’accessibilité pour les sites web, les applications mobiles et d’autres produits et services numériques.

Quel est l’objectif ? S’assurer que les personnes en situation de handicap peuvent accéder et utiliser les services numériques aussi facilement que tout le monde. Mais pour de nombreuses entreprises – en particulier celles qui ne disposent pas d’experts internes en accessibilité – le chemin vers la conformité peut sembler flou et accablant :

• Qui doit se conformer ?
• Quelles sont les exigences spécifiques en matière d’accessibilité ?
• Comment évaluer votre niveau de conformité actuel ?
• Et quelles étapes pratiques pouvez-vous suivre pour respecter les normes ?

Ce guide apporte les réponses. Que vous soyez dans le domaine juridique, produit, design ou développement, nous détaillerons les exigences clés de l’EAA, montrerons comment elles affectent vos propriétés numériques et proposerons un cadre clair pour atteindre la conformité.

En résumé

• Qui doit se conformer à la Loi Européenne sur l’Accessibilité ?
• Exigences clés pour se conformer à l’EAA
• Comment l’EAA affecte les services numériques et les sites web
• Étapes pour atteindre la conformité à l’EAA
• Défis courants pour respecter les normes de l’EAA
• Outils et ressources pour la conformité
• Faites de l’accessibilité une priorité – avant la date limite de 2025

Qui doit se conformer à la Loi Européenne sur l’Accessibilité ?

L’EAA s’applique à un large éventail d’entreprises opérant dans l’Union Européenne ou fournissant des services à des consommateurs au sein de l’UE.

Mais quelles entreprises sont réellement concernées ?

La réponse courte : la plupart des fournisseurs de services numériques B2C.

Vous devrez peut-être vous conformer si vous :

• Exploitez une plateforme de commerce électronique ou vendez des produits en ligne
• Offrez des services bancaires ou financiers
• Proposez des systèmes de réservation de transport (bus, train, avion, etc.)
• Gérez une plateforme de médias, y compris des vidéos, de l’audio ou du streaming
• Publiez des eBooks ou des outils de lecture numérique
• Fournissez des services de télécommunications
• Proposez des sites web ou des applications mobiles accessibles au public
• Servez des consommateurs de l’UE, même si vous êtes basé en dehors de l’UE

Quelques mythes courants sur la conformité

Vous avez probablement eu ces pensées dans le passé, mais elles ne sont (probablement) pas exactes :

• “Nous sommes trop petits.” → La taille n’est généralement pas un facteur déterminant pour la conformité (avec quelques exceptions mineures).
• “Nous ne sommes pas dans l’UE.” → Si votre service cible ou atteint des consommateurs de l’UE, vous êtes probablement concerné.
• “Nous ne vendons que des biens physiques.” → Vos interfaces numériques (site web, paiement, application) doivent toujours être conformes – tout comme certains biens physiques !

Alors, voici un petit contrôle : êtes-vous concerné ?

• Vendez-vous ou commercialisez-vous des produits/serviços pour des consommateurs de l’UE ?
• Fournissez-vous des services numériques (site web, application, contenu) ?
• Des fonctionnalités non accessibles empêcheraient-elles un utilisateur de compléter une tâche clé ?

Si la réponse est oui, la conformité est probablement requise, vous devez donc agir.

Exigences clés pour la conformité à l’EAA

L’EAA ne recommande pas simplement de meilleures expériences numériques, elle les impose. Les entreprises concernées doivent s’assurer que leurs produits et services numériques sont accessibles aux personnes handicapées, sur la base d’un ensemble cohérent d’exigences dans tous les États membres de l’UE.

Qu’est-ce qui doit être accessible ?

L’EAA s’applique à une gamme de ressources numériques, y compris :

• Sites web et applications web
• Applications mobiles
• Plateformes de commerce électronique et magasins en ligne
• Bornes en libre-service (par exemple, bornes de billetterie, guichets automatiques)
• eBooks et logiciels de lecture
• Lecteurs multimédia audiovisuels
• Interfaces de service client numériques

En gros, toute interface avec laquelle un utilisateur interagit pour accéder ou gérer un service est probablement concernée.

Que signifie « accessible » selon l’EAA ?

Pour se conformer à l’EAA, les services numériques doivent respecter les normes techniques d’accessibilité, à savoir :

• Conformité avec ce qui suit :
  • Texte alternatif pour le contenu non textuel
  • Navigabilité au clavier
  • Compatibilité avec les lecteurs d’écran
  • Options de redimensionnement du texte sans perte de fonctionnalité
  • Contraste de couleurs suffisant
  • Patrons de navigation cohérents
  • Étiquettes descriptives des formulaires et messages d’erreur
  • Sous-titres et transcriptions pour les contenus vidéo/audio

Date limite clé : 28 juin 2025

---

C’est à partir de cette date que les mesures d’application commencent. Après cette date, les produits et services non conformes pourraient être soumis à des amendes, être retirés du marché ou faire l’objet d’autres actions légales de la part des autorités nationales.

Comment l’EAA affecte les services numériques et les sites web

L’EAA ne se limite pas à la présentation de l’information ; elle affecte également la conception, la construction et la maintenance des services numériques. Cela inclut les flux utilisateurs, les composants de l’interface, le contenu multimédia et même les technologies utilisées pour construire votre site ou votre application.

Si votre entreprise dépend des canaux numériques pour fournir des services, que ce soit un magasin en ligne, un portail client, une application mobile ou une plateforme médiatique, la conformité à l’EAA doit faire partie de votre stratégie.

Plateformes de commerce électronique

Les magasins en ligne doivent permettre à tous les utilisateurs de :

• Explorer, sélectionner et acheter des produits
• Lire les descriptions des produits via des lecteurs d’écran
• Naviguer dans le processus de paiement en utilisant uniquement le clavier
• Voir des messages d’erreur accessibles en cas d’échec du formulaire

Services bancaires et financiers

Les portails et les applications sécurisées doivent :

• Être navigables sans souris
• Fournir des interfaces et des formulaires 2FA accessibles
• Offrir des documents téléchargeables (par exemple, PDF) au format accessible

Plateformes de streaming et médias numériques

Les contenus audiovisuels doivent inclure :

• Sous-titres pour le contenu parlé
• Transcriptions pour les fichiers audio uniquement
• Interfaces compatibles avec la technologie d’assistance

Systèmes de conception et motifs de navigation

Tous les services doivent veiller à ce qu’il y ait :

• Des mises en page cohérentes sur les pages
• Des indicateurs de focus clairs pour les éléments interactifs
• HTML sémantique et une structure correcte des en-têtes pour les lecteurs d’écran

En résumé, l’accessibilité numérique affecte presque tous les aspects de l’expérience utilisateur. Par conséquent, commencer à respecter la conformité signifie concevoir pour l’inclusion dès le début.

Étapes pour atteindre la conformité avec l’EAA

Répondre aux exigences de l’EAA ne signifie pas nécessairement une refonte complète dès le premier jour. Avec une approche structurée et progressive, les organisations peuvent commencer à apporter des améliorations significatives immédiatement, puis évoluer vers une conformité accrue.

Voici un cadre pratique pour guider votre équipe.

1. Auditez vos actifs numériques

Commencez par évaluer votre site web, vos applications et vos produits numériques pour comprendre où vous en êtes. Combinez :

• Des outils automatisés comme WAVE, axe DevTools ou Google Lighthouse
• Des tests manuels avec des lecteurs d’écran (NVDA, VoiceOver)
• Tests de navigation au clavier uniquement
• Tests utilisateurs réels, avec des utilisateurs utilisant des technologies d’assistance, si possible

2. Priorisez les problèmes par impact et visibilité

Identifiez les domaines de focalisation clés :

• Pages à fort trafic (accueil, produit, paiement, connexion)
• Formulaires et parcours utilisateurs critiques
• Contenus non conformes (vidéos, PDF, contenu interactif)

NOTE: Assurez-vous d’utiliser le niveau AA de WCAG 2.1 et les annexes de l’EAA comme référence technique ; c’est important.

3. Corrigez les barrières d’accessibilité les plus courantes

Commencez par des corrections réalisables qui feront une grande différence :

• Ajouter un texte alternatif à toutes les images significatives
• Assurez-vous que les champs de formulaire ont des étiquettes et des messages d’erreur accessibles
• Ajustez le contraste des couleurs et permettez le redimensionnement du texte
• Corrigez la structure des en-têtes pour un HTML sémantique
• Ajoutez des sous-titres et des transcriptions au contenu multimédia

4. Utilisez la solution Accessibility Solution pour un impact rapide

La Accessibility Solution permet aux équipes de progresser rapidement :

• Ajoute des améliorations essentielles pour l’accessibilité
• Aide à satisfaire les critères WCAG 2.1 Niveau AA
• Offre un chemin simple pour démontrer un engagement proactif en matière d’accessibilité

5. Éduquez et habilitez vos équipes

Assurez-vous que les équipes produit, design, marketing et développement :

• Comprennent les principes du design accessible
• Intègrent des contrôles d’accessibilité dans le processus de QA
• Sachent où trouver les normes et les documents de référence

6. Surveillez, itérez et maintenez

L’accessibilité n’est pas un projet ponctuel. Assurez-vous d’intégrer :

• Des ré-audits périodiques
• Des canaux de feedback pour les utilisateurs
• Des processus de gouvernance pour garantir la conformité continue

Les défis courants pour respecter les normes EAA

De nombreuses organisations reconnaissent le besoin d’accessibilité, mais rencontrent des obstacles lorsqu’elles commencent à mettre en œuvre les changements. Comprendre les défis les plus courants peut vous aider à éviter les retards et à garder votre plan de conformité sur la bonne voie.

1. Manque d’expertise interne

De nombreuses équipes – en particulier dans les PME – manquent de spécialistes internes en accessibilité. En conséquence, la conformité peut sembler trop technique ou accablante.

La solution : commencez petit. Utilisez des outils de test automatisés, des ressources d’apprentissage gratuites et des bibliothèques de design accessibles. Et lorsque nécessaire, consultez des partenaires externes spécialisés en accessibilité.

2. Systèmes obsolètes et technologie dépassée

Les anciens sites web ou les systèmes de gestion de contenu peuvent ne pas supporter le HTML sémantique, les rôles ARIA ou la compatibilité avec les lecteurs d’écran.

La solution : donnez la priorité aux pages critiques et travaillez l’accessibilité lors des refontes ou des mises à jour planifiées. Des outils comme le widget d’accessibilité d’iubenda peuvent vous aider à commencer à travailler vers un chemin accessible.

3. Responsabilité fragmentée

L’accessibilité est souvent partagée entre plusieurs équipes – design, développement, marketing et juridique – sans propriétaire clairement défini.

La solution : assignez une responsabilité claire. Désignez un responsable interne ou créez un groupe de travail et incluez l’accessibilité dans vos processus de QA et de gestion du contenu.

4. Malentendus sur les obligations légales

Certaines équipes supposent que l’EAA ne s’applique pas à elles ou sous-estiment ce qui est nécessaire pour répondre aux normes WCAG.

La solution : utilisez des listes de vérification d’autoévaluation, examinez l’étendue de l’EAA et consultez le service juridique si nécessaire. Rappelez-vous : si vous servez des consommateurs de l’UE, la conformité est probablement requise.

En abordant ces défis dès le début, votre organisation peut réaliser des progrès mesurables sans se perdre dans les détails.

Outils et ressources pour la conformité

Que vous commenciez votre parcours d’accessibilité ou cherchiez à rationaliser les améliorations continues, les bons outils peuvent faire toute la différence.

Voici une sélection de ressources fiables pour aider votre équipe à atteindre et maintenir la conformité à l’EAA.

Outils de test pour l’accessibilité

Commencez par des analyses automatisées pour repérer les problèmes d’accessibilité les plus courants :

• WAVE – Met en évidence les erreurs de contraste, les textes alternatifs manquants et les défauts de structure sémantique
• axe DevTools – Extension Chrome pour les développeurs avec des conseils pratiques pour les WCAG
• Google Lighthouse – Intégré dans Chrome DevTools, avec des scores d’accessibilité

Support pour les tests manuels

Les outils automatisés ne détectent que 30 à 40 % des problèmes. Associez-les à :

• Lecteurs d’écran : NVDA (Windows), VoiceOver (Mac)
• Tests de navigation au clavier : Utilisez Tab, Shift+Tab et Enter pour naviguer sur votre site
• Tests de zoom/redimensionnement : Assurez-vous que la mise en page et le contenu restent utilisables à 200 % de zoom

Ressources pour la conception et le contenu

• Vérificateurs de contraste (ex. WebAIM, Stark)
• Principes de conception inclusive du W3C et systèmes de conception ouverts
• Guides pour les textes alternatifs et l’accessibilité des médias

Solution Accessibility Solution

Pour les entreprises cherchant une étape immédiate vers l’accessibilité, Accessibility Solution :

• Ajoute des améliorations clés pour WCAG 2.1 Niveau AA
• Ne nécessite aucun redéveloppement ni replatforming
• Supporte votre stratégie d’accessibilité continue

Faites de l’accessibilité une priorité – avant la date limite de 2025

L’accessibilité numérique n’est plus optionnelle. Avec la date limite d’application de la Loi Européenne sur l’Accessibilité fixée au 28 juin 2025, les entreprises à travers l’Europe – et au-delà – doivent s’assurer que leurs sites web, applications et services numériques sont accessibles à tous les utilisateurs.

La bonne nouvelle ? Vous n’avez pas à tout faire d’un coup.

En comprenant vos obligations légales, en identifiant les lacunes en matière d’accessibilité et en faisant des améliorations continues en utilisant le niveau AA de WCAG 2.1 comme guide, votre organisation peut réduire les risques, élargir son audience et offrir une meilleure expérience numérique à tous.

Commencez dès maintenant avec une solution simple et évolutive

Accessibility Solution facilite le début de la conformité aux exigences dès maintenant, sans avoir besoin d’une reconstruction complète.

Que vous soyez dans le produit, la conformité, l’UX ou la direction, faire le premier pas aujourd’hui peut vous faire économiser du temps, des coûts et de la complexité demain.

Essayez notre Accessibility Solution

The post Guide complet de la conformité à la LEA pour les services numériques appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> https://www.iubenda.com/en/help/182508-guide-complet-de-la-conformite-a-la-lea-pour-les-services-numeriques-2/ Thu, 05 Jun 2025 16:59:09 +0000 https://help.iubenda.com/?p=182508 Ce que la Loi Européenne sur l’Accessibilité signifie pour vos opérations numériques L’accessibilité numérique n’est plus un ajout, c’est une obligation légale pour de nombreuses entreprises opérant en Europe. La Loi Européenne sur l’Accessibilité (EAA), qui entrera en vigueur le 28 juin 2025, introduit un ensemble uniforme de exigences d’accessibilité pour les sites web, les […]

The post Guide complet de la conformité à la LEA pour les services numériques appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> Ce que la Loi Européenne sur l’Accessibilité signifie pour vos opérations numériques

L’accessibilité numérique n’est plus un ajout, c’est une obligation légale pour de nombreuses entreprises opérant en Europe.

La Loi Européenne sur l’Accessibilité (EAA), qui entrera en vigueur le 28 juin 2025, introduit un ensemble uniforme de exigences d’accessibilité pour les sites web, les applications mobiles et d’autres produits et services numériques.

Quel est l’objectif ? S’assurer que les personnes en situation de handicap peuvent accéder et utiliser les services numériques aussi facilement que tout le monde. Mais pour de nombreuses entreprises – en particulier celles qui ne disposent pas d’experts internes en accessibilité – le chemin vers la conformité peut sembler flou et accablant :

• Qui doit se conformer ?
• Quelles sont les exigences spécifiques en matière d’accessibilité ?
• Comment évaluer votre niveau de conformité actuel ?
• Et quelles étapes pratiques pouvez-vous suivre pour respecter les normes ?

Ce guide apporte les réponses. Que vous soyez dans le domaine juridique, produit, design ou développement, nous détaillerons les exigences clés de l’EAA, montrerons comment elles affectent vos propriétés numériques et proposerons un cadre clair pour atteindre la conformité.

En résumé

• Qui doit se conformer à la Loi Européenne sur l’Accessibilité ?
• Exigences clés pour se conformer à l’EAA
• Comment l’EAA affecte les services numériques et les sites web
• Étapes pour atteindre la conformité à l’EAA
• Défis courants pour respecter les normes de l’EAA
• Outils et ressources pour la conformité
• Faites de l’accessibilité une priorité – avant la date limite de 2025

Qui doit se conformer à la Loi Européenne sur l’Accessibilité ?

L’EAA s’applique à un large éventail d’entreprises opérant dans l’Union Européenne ou fournissant des services à des consommateurs au sein de l’UE.

Mais quelles entreprises sont réellement concernées ?

La réponse courte : la plupart des fournisseurs de services numériques B2C.

Vous devrez peut-être vous conformer si vous :

• Exploitez une plateforme de commerce électronique ou vendez des produits en ligne
• Offrez des services bancaires ou financiers
• Proposez des systèmes de réservation de transport (bus, train, avion, etc.)
• Gérez une plateforme de médias, y compris des vidéos, de l’audio ou du streaming
• Publiez des eBooks ou des outils de lecture numérique
• Fournissez des services de télécommunications
• Proposez des sites web ou des applications mobiles accessibles au public
• Servez des consommateurs de l’UE, même si vous êtes basé en dehors de l’UE

Quelques mythes courants sur la conformité

Vous avez probablement eu ces pensées dans le passé, mais elles ne sont (probablement) pas exactes :

• “Nous sommes trop petits.” → La taille n’est généralement pas un facteur déterminant pour la conformité (avec quelques exceptions mineures).
• “Nous ne sommes pas dans l’UE.” → Si votre service cible ou atteint des consommateurs de l’UE, vous êtes probablement concerné.
• “Nous ne vendons que des biens physiques.” → Vos interfaces numériques (site web, paiement, application) doivent toujours être conformes – tout comme certains biens physiques !

Alors, voici un petit contrôle : êtes-vous concerné ?

• Vendez-vous ou commercialisez-vous des produits/serviços pour des consommateurs de l’UE ?
• Fournissez-vous des services numériques (site web, application, contenu) ?
• Des fonctionnalités non accessibles empêcheraient-elles un utilisateur de compléter une tâche clé ?

Si la réponse est oui, la conformité est probablement requise, vous devez donc agir.

Exigences clés pour la conformité à l’EAA

L’EAA ne recommande pas simplement de meilleures expériences numériques, elle les impose. Les entreprises concernées doivent s’assurer que leurs produits et services numériques sont accessibles aux personnes handicapées, sur la base d’un ensemble cohérent d’exigences dans tous les États membres de l’UE.

Qu’est-ce qui doit être accessible ?

L’EAA s’applique à une gamme de ressources numériques, y compris :

• Sites web et applications web
• Applications mobiles
• Plateformes de commerce électronique et magasins en ligne
• Bornes en libre-service (par exemple, bornes de billetterie, guichets automatiques)
• eBooks et logiciels de lecture
• Lecteurs multimédia audiovisuels
• Interfaces de service client numériques

En gros, toute interface avec laquelle un utilisateur interagit pour accéder ou gérer un service est probablement concernée.

Que signifie « accessible » selon l’EAA ?

Pour se conformer à l’EAA, les services numériques doivent respecter les normes techniques d’accessibilité, à savoir :

• Conformité avec ce qui suit :
  • Texte alternatif pour le contenu non textuel
  • Navigabilité au clavier
  • Compatibilité avec les lecteurs d’écran
  • Options de redimensionnement du texte sans perte de fonctionnalité
  • Contraste de couleurs suffisant
  • Patrons de navigation cohérents
  • Étiquettes descriptives des formulaires et messages d’erreur
  • Sous-titres et transcriptions pour les contenus vidéo/audio

Date limite clé : 28 juin 2025

---

C’est à partir de cette date que les mesures d’application commencent. Après cette date, les produits et services non conformes pourraient être soumis à des amendes, être retirés du marché ou faire l’objet d’autres actions légales de la part des autorités nationales.

Comment l’EAA affecte les services numériques et les sites web

L’EAA ne se limite pas à la présentation de l’information ; elle affecte également la conception, la construction et la maintenance des services numériques. Cela inclut les flux utilisateurs, les composants de l’interface, le contenu multimédia et même les technologies utilisées pour construire votre site ou votre application.

Si votre entreprise dépend des canaux numériques pour fournir des services, que ce soit un magasin en ligne, un portail client, une application mobile ou une plateforme médiatique, la conformité à l’EAA doit faire partie de votre stratégie.

Plateformes de commerce électronique

Les magasins en ligne doivent permettre à tous les utilisateurs de :

• Explorer, sélectionner et acheter des produits
• Lire les descriptions des produits via des lecteurs d’écran
• Naviguer dans le processus de paiement en utilisant uniquement le clavier
• Voir des messages d’erreur accessibles en cas d’échec du formulaire

Services bancaires et financiers

Les portails et les applications sécurisées doivent :

• Être navigables sans souris
• Fournir des interfaces et des formulaires 2FA accessibles
• Offrir des documents téléchargeables (par exemple, PDF) au format accessible

Plateformes de streaming et médias numériques

Les contenus audiovisuels doivent inclure :

• Sous-titres pour le contenu parlé
• Transcriptions pour les fichiers audio uniquement
• Interfaces compatibles avec la technologie d’assistance

Systèmes de conception et motifs de navigation

Tous les services doivent veiller à ce qu’il y ait :

• Des mises en page cohérentes sur les pages
• Des indicateurs de focus clairs pour les éléments interactifs
• HTML sémantique et une structure correcte des en-têtes pour les lecteurs d’écran

En résumé, l’accessibilité numérique affecte presque tous les aspects de l’expérience utilisateur. Par conséquent, commencer à respecter la conformité signifie concevoir pour l’inclusion dès le début.

Étapes pour atteindre la conformité avec l’EAA

Répondre aux exigences de l’EAA ne signifie pas nécessairement une refonte complète dès le premier jour. Avec une approche structurée et progressive, les organisations peuvent commencer à apporter des améliorations significatives immédiatement, puis évoluer vers une conformité accrue.

Voici un cadre pratique pour guider votre équipe.

1. Auditez vos actifs numériques

Commencez par évaluer votre site web, vos applications et vos produits numériques pour comprendre où vous en êtes. Combinez :

• Des outils automatisés comme WAVE, axe DevTools ou Google Lighthouse
• Des tests manuels avec des lecteurs d’écran (NVDA, VoiceOver)
• Tests de navigation au clavier uniquement
• Tests utilisateurs réels, avec des utilisateurs utilisant des technologies d’assistance, si possible

2. Priorisez les problèmes par impact et visibilité

Identifiez les domaines de focalisation clés :

• Pages à fort trafic (accueil, produit, paiement, connexion)
• Formulaires et parcours utilisateurs critiques
• Contenus non conformes (vidéos, PDF, contenu interactif)

NOTE: Assurez-vous d’utiliser le niveau AA de WCAG 2.1 et les annexes de l’EAA comme référence technique ; c’est important.

3. Corrigez les barrières d’accessibilité les plus courantes

Commencez par des corrections réalisables qui feront une grande différence :

• Ajouter un texte alternatif à toutes les images significatives
• Assurez-vous que les champs de formulaire ont des étiquettes et des messages d’erreur accessibles
• Ajustez le contraste des couleurs et permettez le redimensionnement du texte
• Corrigez la structure des en-têtes pour un HTML sémantique
• Ajoutez des sous-titres et des transcriptions au contenu multimédia

4. Utilisez la solution Accessibility Solution pour un impact rapide

La Accessibility Solution permet aux équipes de progresser rapidement :

• Ajoute des améliorations essentielles pour l’accessibilité
• Aide à satisfaire les critères WCAG 2.1 Niveau AA
• Offre un chemin simple pour démontrer un engagement proactif en matière d’accessibilité

5. Éduquez et habilitez vos équipes

Assurez-vous que les équipes produit, design, marketing et développement :

• Comprennent les principes du design accessible
• Intègrent des contrôles d’accessibilité dans le processus de QA
• Sachent où trouver les normes et les documents de référence

6. Surveillez, itérez et maintenez

L’accessibilité n’est pas un projet ponctuel. Assurez-vous d’intégrer :

• Des ré-audits périodiques
• Des canaux de feedback pour les utilisateurs
• Des processus de gouvernance pour garantir la conformité continue

Les défis courants pour respecter les normes EAA

De nombreuses organisations reconnaissent le besoin d’accessibilité, mais rencontrent des obstacles lorsqu’elles commencent à mettre en œuvre les changements. Comprendre les défis les plus courants peut vous aider à éviter les retards et à garder votre plan de conformité sur la bonne voie.

1. Manque d’expertise interne

De nombreuses équipes – en particulier dans les PME – manquent de spécialistes internes en accessibilité. En conséquence, la conformité peut sembler trop technique ou accablante.

La solution : commencez petit. Utilisez des outils de test automatisés, des ressources d’apprentissage gratuites et des bibliothèques de design accessibles. Et lorsque nécessaire, consultez des partenaires externes spécialisés en accessibilité.

2. Systèmes obsolètes et technologie dépassée

Les anciens sites web ou les systèmes de gestion de contenu peuvent ne pas supporter le HTML sémantique, les rôles ARIA ou la compatibilité avec les lecteurs d’écran.

La solution : donnez la priorité aux pages critiques et travaillez l’accessibilité lors des refontes ou des mises à jour planifiées. Des outils comme le widget d’accessibilité d’iubenda peuvent vous aider à commencer à travailler vers un chemin accessible.

3. Responsabilité fragmentée

L’accessibilité est souvent partagée entre plusieurs équipes – design, développement, marketing et juridique – sans propriétaire clairement défini.

La solution : assignez une responsabilité claire. Désignez un responsable interne ou créez un groupe de travail et incluez l’accessibilité dans vos processus de QA et de gestion du contenu.

4. Malentendus sur les obligations légales

Certaines équipes supposent que l’EAA ne s’applique pas à elles ou sous-estiment ce qui est nécessaire pour répondre aux normes WCAG.

La solution : utilisez des listes de vérification d’autoévaluation, examinez l’étendue de l’EAA et consultez le service juridique si nécessaire. Rappelez-vous : si vous servez des consommateurs de l’UE, la conformité est probablement requise.

En abordant ces défis dès le début, votre organisation peut réaliser des progrès mesurables sans se perdre dans les détails.

Outils et ressources pour la conformité

Que vous commenciez votre parcours d’accessibilité ou cherchiez à rationaliser les améliorations continues, les bons outils peuvent faire toute la différence.

Voici une sélection de ressources fiables pour aider votre équipe à atteindre et maintenir la conformité à l’EAA.

Outils de test pour l’accessibilité

Commencez par des analyses automatisées pour repérer les problèmes d’accessibilité les plus courants :

• WAVE – Met en évidence les erreurs de contraste, les textes alternatifs manquants et les défauts de structure sémantique
• axe DevTools – Extension Chrome pour les développeurs avec des conseils pratiques pour les WCAG
• Google Lighthouse – Intégré dans Chrome DevTools, avec des scores d’accessibilité

Support pour les tests manuels

Les outils automatisés ne détectent que 30 à 40 % des problèmes. Associez-les à :

• Lecteurs d’écran : NVDA (Windows), VoiceOver (Mac)
• Tests de navigation au clavier : Utilisez Tab, Shift+Tab et Enter pour naviguer sur votre site
• Tests de zoom/redimensionnement : Assurez-vous que la mise en page et le contenu restent utilisables à 200 % de zoom

Ressources pour la conception et le contenu

• Vérificateurs de contraste (ex. WebAIM, Stark)
• Principes de conception inclusive du W3C et systèmes de conception ouverts
• Guides pour les textes alternatifs et l’accessibilité des médias

Solution Accessibility Solution

Pour les entreprises cherchant une étape immédiate vers l’accessibilité, Accessibility Solution :

• Ajoute des améliorations clés pour WCAG 2.1 Niveau AA
• Ne nécessite aucun redéveloppement ni replatforming
• Supporte votre stratégie d’accessibilité continue

Faites de l’accessibilité une priorité – avant la date limite de 2025

L’accessibilité numérique n’est plus optionnelle. Avec la date limite d’application de la Loi Européenne sur l’Accessibilité fixée au 28 juin 2025, les entreprises à travers l’Europe – et au-delà – doivent s’assurer que leurs sites web, applications et services numériques sont accessibles à tous les utilisateurs.

La bonne nouvelle ? Vous n’avez pas à tout faire d’un coup.

En comprenant vos obligations légales, en identifiant les lacunes en matière d’accessibilité et en faisant des améliorations continues en utilisant le niveau AA de WCAG 2.1 comme guide, votre organisation peut réduire les risques, élargir son audience et offrir une meilleure expérience numérique à tous.

Commencez dès maintenant avec une solution simple et évolutive

Accessibility Solution facilite le début de la conformité aux exigences dès maintenant, sans avoir besoin d’une reconstruction complète.

Que vous soyez dans le produit, la conformité, l’UX ou la direction, faire le premier pas aujourd’hui peut vous faire économiser du temps, des coûts et de la complexité demain.

Essayez notre Accessibility Solution

The post Guide complet de la conformité à la LEA pour les services numériques appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> https://www.iubenda.com/en/help/182497-most-accessible-fonts/ Thu, 05 Jun 2025 16:01:00 +0000 https://help.iubenda.com/?p=182497 Fonts are just fonts. Sure, they look nice, but there’s nothing all that special or important about them, right? Think again.  There is far more behind fonts than a simple matter of typography.  They have the power to make content fun or serious, playful or straight-laced; they give hints as to what the reader can […]

The post Most accessible fonts: How to choose typography that supports inclusion appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> Fonts are just fonts.

Sure, they look nice, but there’s nothing all that special or important about them, right?

Think again. 

There is far more behind fonts than a simple matter of typography. 

They have the power to make content fun or serious, playful or straight-laced; they give hints as to what the reader can expect next, like a helpful guidebook, a friendly voice, or a clearly marked path. 

But they can also do the opposite. 

For users with visual impairments, dyslexia, or cognitive challenges, the wrong typeface can turn simple letters and numbers into impenetrable barriers. 

In this guide, we’ll take a look at why fonts matter, how to choose the most accessible fonts, and how to implement them effectively in your digital content. 

In short

• Why font choice matters for accessibility
• Key characteristics of an accessible font
• Sans-serif vs. serif fonts: which is more accessible?
• Most accessible fonts for readability
• Best fonts for dyslexia and cognitive accessibility
• Font size, spacing, and line height: How they affect accessibility
• Fonts to avoid for accessibility
• WCAG guidelines for typography and readability
• Make accessible font choices part of your design DNA
• Frequently asked questions about accessible fonts

Why font choice matters for accessibility

Choosing the right font isn’t just a matter of aesthetics; it’s also about being inclusive. 

Fonts can influence how easily content is perceived, understood, and navigated – and when chosen thoughtfully, typography supports accessibility for people with diverse needs. 

Typography affects legibility, comprehension, and fatigue. So when you choose an inaccessible font, you can create significant barriers to understanding – even when the content itself is well written and accessible. 

Here’s why it matters: 

• Legibility and comprehension: The right font reduces eye strain and supports faster reading.
• Neurodiverse needs: Font style can help or hinder users with low vision, dyslexia, ADHD, and other neurodivergent conditions.
• Legal alignment: Typography plays a role in meeting WCAG’s readability and perceivability standards. 

But remember, accessibility isn’t just about contrast ratios. Learn how to design for everyone with iubenda’s Accessibility Widget. 

Key characteristics of an accessible font

So what actually makes a font accessible?

While aesthetic preferences vary, certain characteristics consistently enhance the readability for all users. These traits reduce cognitive strain and help prevent misreading:

• Simple, open letterforms: Avoid overly ornate styles that make characters hard to distinguish. 
• Large x-height: Taller lowercase letters improve legibility, especially at smaller sizes. 
• Generous character spacing: This helps prevent letters from blending into one another, especially in longer passages. 
• Clear distinction between similar shapes: Characters like “l, I, and 1” or “o, O, and 0” should look noticeably different. 
• Minimal decoration or compression: Fonts that are too stylized or condensed reduce readability, especially when being viewed on a mobile device like a phone or iPad. 

Sans-serif vs. serif fonts: which is more accessible?

There’s an ongoing debate in the design world about serif vs. sans-serif fonts. But when it comes to accessibility, one type generally comes out on top.

Sans-serif fonts like Arial or Helvetica are generally easier to read on screens.

Serif fonts can work in print or headings, but may reduce legibility for users with dyslexia or low vision.

So the verdict? 

Sans-serif is the best choice for body text. You can still use serif, but sparingly – and make sure you test thoroughly.

Most accessible fonts for readability

Certain fonts are widely recognized for their clarity and readability. They’re frequently used in inclusive design because they work well across devices and are familiar to users.

• Arial: Clean and common
• Verdana: Wider spacing, large x-height
• Tahoma: Legible on screens
• Trebuchet MS: Open, rounded characters
• Helvetica: Widely used, but tighter spacing may require adjustments
• Roboto: Modern sans-serif with good readability

A good tip is to test font rendering across devices, as some system fonts vary in performance. 

Best fonts for dyslexia and cognitive accessibility

For users with dyslexia and other cognitive conditions, specially designed fonts can make a big difference. They can improve comprehension and reduce frustration, vastly improving their experience with your site. 

These typefaces use unique visual cues to make each letter more distinct.

• OpenDyslexic: Specially designed to reduce letter confusion
• Lexend: Reduces visual stress and improves reading speed
• Atkinson Hyperlegible: Designed by Braille Institute with clear differentiation
• Read Regular: Tailored to dyslexic readers

These fonts use visual strategies like heavier bottoms, wider spacing, and unique shapes to reduce people’s cognitive load and make everything much easier to understand. 

Font size, spacing, and line height: How they affect accessibility

Typography is also about how you present your typefaces – with key aspects like size, spacing, and formatting all influencing readability. 

Here’s how to get it right:

• Minimum font size for accessibility: WCAG recommends at least 16px for body text.
• Line height: Use 1.5x line spacing for body text (as per WCAG 1.4.8).
• Letter spacing: Aim for at least 0.12x the font size.
• Word spacing: Target 0.16x the font size.

It’s also a good idea to use relative units (em/rem) for flexibility and avoid fixed pixel sizes on responsive layouts.

Fonts to avoid for accessibility

Let’s be honest, some fonts just look great. Whether that’s in a brand deck, on a presentation, or across your site. 

But the issue is that these can also seriously hinder readability online. 

When accessibility is the goal, steer clear of these common culprits:

• Cursive or script fonts: Hard to parse quickly
• Condensed fonts: Reduce spacing and character distinction
• Decorative/stylized fonts: Especially problematic for neurodivergent users
• Comic Sans: Although sometimes recommended for dyslexia, it’s divisive, and it can be argued that it lacks professionalism

How to test font accessibility on websites

---

Not sure if your font choices are up to scratch? 

Here’s how to assess them in a practical, user-focused way:

Automated tools: Use browser extensions like Accessibility Insights, WAVE, or axe DevTools to flag common issues quickly.

Responsive testing: Check how fonts render at different screen sizes and zoom levels to ensure consistency.

Visual evaluation: Combine font tests with contrast and scalability evaluations to check for readability and clarity.

User testing: Whenever possible, test with real users to uncover problems that tools might miss.

WCAG guidelines for typography and readability

The Web Content Accessibility Guidelines (WCAG) include several checkpoints that relate directly to typography. 

These help you make sure your content remains clear and readable in diverse contexts.

• WCAG 2.2 Success Criterion 1.4.12 (Text Spacing)
• 1.4.3 (Contrast), 1.4.4 (Resize Text), and 1.4.8 (Visual Presentation)
• Emphasize: “No loss of content or functionality” when resized or reformatted

You can take a look at the WCAG guidelines and the specific clauses above by visiting their website here. 

Need help applying WCAG to your site?

Discover how iubenda simplifies accessibility right here.

Make accessible font choices part of your design DNA

Even though it may not be the first thing to spring to mind, typography really does shape the reading experience. 

By making smart, accessible choices – from font selection to spacing and formatting – you can create content that works for more people, more of the time.

And when your content and site are more accessible, this doesn’t just benefit those with additional needs – it creates a more rounded, streamlined experience for everyone who visits your site. 

Frequently asked questions about accessible fonts

1. What makes a font accessible?

An accessible font is designed to improve readability through clear letterforms, ample spacing, and high legibility across digital and print formats.

2. Are sans-serif fonts better for accessibility?

Generally speaking, yes. Sans-serif fonts are easier to read on screens due to their clean, simple shapes.

3. What’s the best font for dyslexia?

Fonts like OpenDyslexic, Lexend, and Atkinson Hyperlegible are specifically designed to support dyslexic readers.

4. What is the WCAG minimum font size for accessibility?

At least 16px for body text is recommended to meet accessibility guidelines.

5. How can I test if a font is accessible?

Use tools like WAVE or axe DevTools and perform user testing with people who have diverse needs.

6. Is Comic Sans really good for dyslexia?

Some say yes due to its uneven shapes, but it’s also polarizing and often considered unprofessional.

7. What fonts should I avoid if I want to be accessible?

Avoid cursive, decorative, and condensed fonts that reduce legibility.

8. Can font choice affect cognitive load?

Absolutely. Clear, consistent fonts reduce cognitive strain and make reading easier.

9. Do accessible fonts work across all browsers and devices?

Most web-safe fonts do. Be sure to test font rendering across different platforms.

10. How can iubenda help with font accessibility?

iubenda’s Accessibility Widget can help you fix the most common accessibility issues in just minutes.

The post Most accessible fonts: How to choose typography that supports inclusion appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> https://www.iubenda.com/en/help/182488-digital-inclusion/ Thu, 05 Jun 2025 14:43:35 +0000 https://help.iubenda.com/?p=182488 Being digitally connected isn’t a luxury; it’s a lifeline. Everything from education to healthcare, banking, shopping, and government services is online, but millions of people are still being left behind. Digital inclusion means making sure that everyone, regardless of income, location, age, ability, or literacy, can access and use digital technologies effectively.  It’s about equity. […]

The post A guide to digital inclusion: Breaking barriers in the digital age appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> Being digitally connected isn’t a luxury; it’s a lifeline.

Everything from education to healthcare, banking, shopping, and government services is online, but millions of people are still being left behind.

Digital inclusion means making sure that everyone, regardless of income, location, age, ability, or literacy, can access and use digital technologies effectively. 

It’s about equity. It’s about empowerment. And in 2025, it’s more urgent than ever.

According to the World Bank, nearly 3 billion people still don’t use the internet. Even among those who do, many face barriers due to inaccessible interfaces, lack of digital skills, or unreliable infrastructure. 

The result? A growing digital divide that mirrors – and often magnifies – existing social and economic inequalities.

Digital exclusion doesn’t just affect individuals. It limits participation in democracy, reduces workforce potential, and creates reputational and legal risks for organizations. As businesses and institutions digitize rapidly, they must make sure that progress doesn’t leave people behind.

Fortunately, digital inclusion isn’t an abstract ideal – it’s something we can build through thoughtful design, policy, and technology. And web accessibility plays a foundational role in making it possible.

This article will explore the key pillars of digital inclusion, the barriers people face, and what governments, businesses, and digital teams can do to promote a truly inclusive digital future.

In short

• The key barriers to digital inclusion
• The role of accessibility in digital inclusion
• How governments and organizations promote digital inclusion
• Best practices for improving digital inclusion
• The impact of assistive technology on digital inclusion
• Digital inclusion in education and the workplace
• How businesses can support digital inclusion
• Conclusion: Building a digitally inclusive future, together

The key barriers to digital inclusion

Despite growing awareness, digital inclusion remains out of reach for many. That’s because the barriers to full participation are not just technical – they’re social, economic, physical, and cultural. 

Let’s take a look at some of the most common and persistent obstacles:

1. Infrastructure and affordability

• In many regions, broadband access is limited or prohibitively expensive.
• Even in urban centers, some households can’t afford data plans, devices, or consistent electricity.
• Rural and low-income communities are disproportionately affected by infrastructure gaps.

2. Lack of digital skills

• Access doesn’t guarantee capability. Millions struggle with basic tasks like creating passwords, navigating websites, or sending emails.
• The digital skills gap is especially pronounced among older adults, people with lower literacy, and those with limited education.

3. Accessibility barriers

• Many websites, apps, and services are not designed with disabled users in mind.
• Barriers include poor color contrast, missing alt text, inaccessible forms, and incompatible designs for assistive technologies.

4. Language and literacy challenges

• Digital content that is overly complex or not available in users’ native language can exclude large groups.
• This particularly affects migrants, multilingual communities, and people with learning differences such as dyslexia.

5. Cultural and motivational factors

• Distrust in digital platforms, fear of online scams, or cultural stigma around technology can discourage participation.
• Some people simply don’t see digital tools as relevant or safe.

Solving digital inclusion requires addressing these barriers holistically, not just with tech, but through policy, education, design, and empathy.

The role of accessibility in digital inclusion

Digital inclusion and accessibility are deeply interconnected, but they’re not interchangeable.

While digital inclusion is the broader concept of ensuring equitable participation in the digital world, accessibility focuses specifically on removing barriers for people with disabilities. It’s a crucial pillar of digital inclusion – and often the first step toward achieving it.

Why accessibility matters

---

According to the World Health Organization, over 1.3 billion people worldwide live with a disability. That’s nearly 1 in 6 of us.

If digital platforms aren’t accessible, vast segments of the population are immediately excluded from essential services and opportunities.

Inaccessible websites, mobile apps, and documents can prevent users from:

Navigating interfaces using a keyboard

Understanding content due to poor color contrast or small fonts

Hearing audio content without captions or transcripts

Filling out forms that aren’t compatible with screen readers

WCAG: The accessibility foundation

The Web Content Accessibility Guidelines (WCAG) provide a framework for designing inclusive digital experiences. 

Their principles – Perceivable, Operable, Understandable, and Robust (POUR) – are used globally as a benchmark for accessibility compliance.

Accessibility is the gateway

By addressing accessibility, organizations automatically improve usability for all. Clear navigation, descriptive links, flexible layouts, and readable fonts benefit everyone – not just disabled users.

In other words, you can’t have digital inclusion without accessibility. It’s the baseline for building digital experiences that respect and reflect human diversity.

How governments and organizations promote digital inclusion

Tackling digital exclusion is not the responsibility of one group alone. It takes collaboration between governments, non-profits, businesses, educators, and technologists to create an inclusive digital society.

Here’s how different sectors are making progress:

Government-led initiatives

Many countries have launched national digital inclusion strategies focused on expanding access, improving digital skills, and ensuring accessibility. For example:

• The European Union mandates accessibility through the European Accessibility Act (EAA), which requires many digital services to be accessible by 2025.
• Local councils and municipalities often fund digital literacy training, especially for older adults and job seekers.

Private sector contributions

Forward-thinking companies are embedding digital inclusion into their products and services by:

• Investing in accessible design from the ground up
• Offering free or subsidized access to digital tools and connectivity (e.g., Google’s Chromebooks for Education or Microsoft’s Airband Initiative)
• Partnering with non-profits to fund training programs for marginalized communities
• Building internal diversity and inclusion teams to shape digital equity strategies

Non-profits and community groups

Organizations like the Digital Equity Foundation, AbilityNet, and Good Things Foundation play a key role in:

• Delivering community-based tech support
• Running inclusion-focused awareness campaigns
• Advocating for inclusive policies and funding

Ultimately, digital inclusion is a shared responsibility. Governments can create the regulatory foundation, but lasting change requires public-private cooperation and user-centered design.

Best practices for improving digital inclusion

Digital inclusion is not a one-time initiative; it’s a mindset embedded in design, delivery, and communication. The following best practices help ensure that your digital products and services are usable and beneficial to everyone.

1. Design with accessibility from the start

Embed accessibility and inclusive design principles into your development lifecycle rather than retrofitting later. Use semantic HTML, provide alt text, ensure keyboard navigability, and maintain strong color contrast.

2. Simplify language and navigation

Use plain language, intuitive layouts, and clear CTAs. Avoid jargon. A well-structured interface helps everyone, especially users with cognitive disabilities, low literacy, or language barriers.

3. Test with diverse users

Involve people from different backgrounds, age groups, and ability levels in user testing. Their feedback reveals friction points that homogenous testing often misses.

4. Provide multiple ways to access content

Offer alternatives: text transcripts for audio, video captions, and downloadable documents in accessible formats. This makes sure users can engage in the way that works best for them.

5. Offer digital skills support

Consider how you can provide or link to training and onboarding materials, especially for tools that may be new to your audience. A friendly FAQ or step-by-step guide can make a big difference.

6. Regularly audit and update

Use accessibility testing tools and perform regular reviews to make sure your content stays inclusive as your product evolves.

By embracing these best practices, you build trust, loyalty, and compliance.

The impact of assistive technology on digital inclusion

Assistive technology (AT) plays a vital role in closing the digital divide for people with disabilities. By enabling access to digital content and services, these tools make inclusion not just possible, but practical.

What is assistive technology?

Assistive technology includes devices, software, and tools that help people with disabilities perform tasks they might otherwise find difficult or impossible. In the digital world, this can range from simple screen magnifiers to advanced speech-to-text systems.

Common examples of digital assistive tech

• Screen readers: Convert on-screen text into speech or braille for users with visual impairments.
• Text-to-speech tools: Help users with dyslexia, ADHD, or low literacy access written content more easily.
• Voice recognition software: Allows users to navigate and input text via speech instead of a keyboard.
• Alternative input devices: Such as eye-tracking tools or adaptive switches for users with limited mobility.
• Customizable interfaces: Options for resizing text, adjusting color contrast, or selecting dyslexia-friendly fonts.

Why assistive tech matters

Assistive technology empowers independence and participation in:

• Education: Helping students access digital learning platforms
• Employment: Enabling remote work and professional development
• Healthcare: Supporting patients in managing telehealth or booking appointments
• Civic life: Allowing individuals to vote, access government services, and connect with their communities

When websites and digital tools are designed to work with assistive technology, everyone benefits.

Digital inclusion in education and the workplace

Access to digital tools and content is essential for learning, professional development, and career participation. However, digital exclusion continues to create inequality in both education and employment.

Education: Learning without limits

Digital education platforms are now standard in all settings, from K-12 classrooms to higher education and remote learning environments. But without inclusive design, these tools can unintentionally exclude students with disabilities or those from disadvantaged backgrounds.

Common barriers include:

• Learning portals that don’t work with screen readers
• Videos without captions
• Text-heavy content that isn’t readable for dyslexic learners

Solutions:

• Use accessible learning management systems (LMS)
• Provide multi-format content (e.g., audio, video, transcripts)
• Offer digital literacy training for students and educators alike

Inclusion in education correlates with long-term academic success and employment outcomes, so it goes beyond ethics.

The workplace: Inclusion as a competitive advantage

Many jobs now rely on digital platforms, from recruitment and onboarding to daily collaboration and upskilling. Yet employees with disabilities often encounter inaccessible systems that hinder productivity and advancement.

Examples:

• Job applications incompatible with keyboard navigation
• Training videos without subtitles
• Intranet tools that lack accessibility controls

Best practices:

• Make sure HR platforms and digital tools meet WCAG standards
• Provide assistive technology support and personalized accommodations
• Make inclusive design a part of company culture and DEI strategy

Digital inclusion in the workplace is about unlocking the full potential of a diverse workforce and attracting talent from all backgrounds.

How businesses can support digital inclusion

Businesses have a powerful role to play in shaping a digital world that works for everyone. Beyond compliance, digital inclusion is a strategic advantage – it opens access to broader markets, improves user experience, and strengthens brand trust.

Here are key ways your organization can contribute:

1. Audit your digital products

Conduct a comprehensive accessibility audit across your websites, apps, and internal platforms. Identify barriers that could exclude users with disabilities, older adults, or individuals with limited digital literacy.

2. Embed inclusive design in your development process

Make inclusive design principles a default. Involve users with diverse needs during product research and usability testing. Use accessible fonts, meaningful link text, flexible layouts, and semantic code from the start.

3. Educate your teams

Invest in ongoing training for developers, content creators, and marketers on accessibility best practices and the importance of inclusive UX. Make this part of your DEI (diversity, equity, and inclusion) strategy.

4. Support assistive technology compatibility

Ensure your services work smoothly with screen readers, voice navigation tools, and keyboard-only browsing. Test with multiple devices and software types.

5. Partner with purpose

Work with organizations that promote digital inclusion – whether through sponsorships, open-source contributions, or employee volunteering. Use your reach to amplify awareness and action.

6. Leverage compliance as a baseline, not a finish line

Laws like the European Accessibility Act and ADA offer clear benchmarks, but true inclusion goes beyond checklists – so aim to meet user needs, not just legal minimums.

Conclusion: Building a digitally inclusive future, together

Digital inclusion is more than a policy or best practice; it’s a reflection of how we value equity, participation, and human potential in an increasingly digital world.

By removing barriers, embracing inclusive design, supporting assistive technologies, and widening access to digital tools, we unlock opportunities for millions of people. It’s good for society, good for business, and essential for long-term growth.

Whether you’re designing a website, building a platform, shaping policy, or leading a team, your role matters. Inclusion isn’t the responsibility of one department or one decision, it’s a commitment embedded across every touchpoint of the digital experience.

Ready to take action?

Explore how iubenda’s Accessibility Widget can support your digital inclusion goals by helping you meet key accessibility standards and deliver more inclusive experiences from the start.

Learn more about iubenda’s Accessibility Widget

Together, we can close the digital divide – and create a more open, connected, and equitable world for all.

The post A guide to digital inclusion: Breaking barriers in the digital age appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> https://www.iubenda.com/en/help/182473-screen-readers/ Wed, 04 Jun 2025 16:21:00 +0000 https://help.iubenda.com/?p=182473 Picture this.  You land on a website only to find that it all makes zero sense.   The content is unreadable, key functions are hidden, and you can’t make head nor tail of how to find what you’re looking for.  For millions of people who rely on screen readers, this isn’t a hypothetical situation – it’s […]

The post How to make your website screen reader-friendly (and why it matters) appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> Picture this. 

You land on a website only to find that it all makes zero sense.  

The content is unreadable, key functions are hidden, and you can’t make head nor tail of how to find what you’re looking for. 

For millions of people who rely on screen readers, this isn’t a hypothetical situation – it’s a daily digital experience.

Screen readers are essential tools for digital accessibility. They convert on-screen content into synthesized speech or Braille, allowing people with visual impairments to navigate websites and applications with ease. 

But in reality, many developers and designers lack a clear understanding of how these tools work and what makes a digital experience accessible. 

It’s a knowledge gap that can unintentionally exclude people who rely on screen readers every day. 

In this article, we break down what screen readers are, how they function, who uses them, and how sites can be designed inclusively – with a few technical tips and practical examples thrown in. 

In short

• What are screen readers?
• How do screen readers work?
• Who uses screen readers?
• Popular screen readers: A comparison
• How screen readers improve digital accessibility
• Common challenges screen reader users face
• Best practices for screen reader-friendly websites
• How to test your website for screen reader compatibility
• Screen reader accessibility matters
• Frequently Asked Questions

What are screen readers?

First things first, what exactly are screen readers?

Essentially, they’re assistive technologies that read digital content aloud or translate it into Braille. 

They help users navigate content using a keyboard or input methods other than a typical mouse. Screen readers rely on the structure and semantics of HTML code to make sense of web content. 

How do screen readers work?

Screen readers work by building an “accessibility tree,” which is a simplified version of the webpage’s underlying structure (called the DOM, or Document Object Model). 

This “tree” picks up on meaningful elements in the code, like headings, labels, and ARIA (Accessible Rich Internet Applications) attributes – all of which help users make sense of the content. 

Here’s an example.

If the code for a button was written as:

<button aria-label=“Submit form”>Submit</button>

A screen reader will announce it as “Submit form button.” 

It’ll also give navigation shortcuts to move through headings, landmarks, links, and form fields. That’s why proper markup and labeling are crucial for easy navigation. 

Who uses screen readers?

Screen readers are mostly used by people with:

• Full visual impairment
• Low vision
• Cognitive or learning disabilities
• Temporary visual impairment (e.g., recovering from eye surgery)

Users often pair screen readers with keyboard navigation, screen magnifiers, or Braille displays. 

Popular screen readers: A comparison

With several screen readers available across different platforms, it helps to understand which ones are the most commonly used and how they differ. 

Here are some of the most widely used screen readers: 

Screen reader	Platform	Cost	Notes
JAWS	Windows	Paid	Feature-rich, enterprise-friendly
NVDA	Windows	Free	Open-source, developer-friendly
VoiceOver	macOS/iOS	Built-in	Default on Apple devices
TalkBack	Android	Built-in	Default on Android devices

Screen readers by platform

Screen readers are built to work across different operating systems, and each platform comes with its own set of tools, features, and user expectations. 

If you’re designing for inclusivity, it’s important to know what screen readers are available on each system and how they differ from each other. 

• Windows: JAWS and NVDA dominate this space. NVDA is often favored by developers thanks to its open-source nature. 
• macOS/iOS: VoiceOver is built in and fully integrated with Apple hardware, so it’s the go-to option. 
• Android: TalkBack offers accessibility support across Android apps and devices, so again, it’s the go-to option for Android users. 

Each system has its own keyboard shortcuts and navigation paradigms, so testing across platforms is always a good idea. 

How screen readers improve digital accessibility

Screen readers are a bridge between visual interfaces and non-visual experiences. 

They support accessibility in several key ways: 

• Access to information: They give millions of users access to web content they wouldn’t otherwise be able to enjoy
• Better code structure: They encourage better semantic markup, which benefits SEO
• Legal compliance: They help websites meet accessibility laws like the ADA and the European Accessibility Act

Compliance and usability go hand-in-hand. See how iubenda’s Accessibility Widget can help.

Common challenges screen reader users face

Despite all the best intentions, many digital experiences still fall short when it comes to accessibility. 

Screen reader users often face a range of barriers that make navigation frustrating, or in some extreme cases, impossible. 

Some common challenges include:

• Poor heading structure: Skipping heading levels or not using them properly
• Missing alt text: Non-descriptive or absent alt attributes on images
• Inaccessible forms: Forms that don’t include visible labels or instructions can confuse screen reader users who rely on auditory cues to complete fields
• Dynamic content: When content updates (like notifications or form results) aren’t announced, users may miss important information
• Misused ARIA roles: Applying ARIA roles incorrectly can interfere with how content is interpreted, leading to disorientation or errors

Best practices for screen reader-friendly websites

Designing for screen reader accessibility doesn’t have to be complicated – but it does require intentional choices. 

Here are some practical ways to make your website more usable for screen reader users:

• Use semantic HTML (e.g., <nav>, <main>, <button>, <label>)
• Write descriptive alt attributes for images
• Label all form inputs with <label> or aria-label
• Use heading tags in a logical order
• Provide keyboard navigation and focus styles
• Avoid using visual cues alone (e.g., “Click the red button”)
• Use meaningful link text (e.g., avoid “Click here”)

Here’s an example of what an accessible form markup might look like:

<label for=”email”>Email address</label>

<input type=”email” id=”email” name=”email” />

How to test your website for screen reader compatibility

Testing is always an important step in any accessibility effort. 

Luckily, there are a number of different tools and techniques you can use to help you evaluate how well your site works with screen readers. 

• Stress-test with screen readers: Use popular readers like VoiceOver, NVDA, or TalkBack as a good barometer to test your interface
• Browser tools: Use tools like Lighthouse to audit your site’s accessibility directly in the browser, giving you quick, actionable feedback
• Extensions: Add-ons like axe DevTools and WAVE can help pinpoint specific code-level issues affecting screen reader compatibility
• Real user testing: The most accurate and meaningful way to test your accessibility is by observing real users interacting with your site using their preferred screen readers

Screen reader accessibility matters

As with any accessibility improvements, creating screen reader-friendly experiences isn’t just a box-ticking exercise. 

Not only does it help with your site’s SEO and keep your site compliant with evolving laws and expectations, it makes the web a more inclusive and welcoming place for everyone. 

By understanding how screen readers work and taking simple, thoughtful steps in your design and development process, you can help remove barriers that stand in the way of equal access. 

So start with small improvements, keep testing, and make accessibility a standard part of your workflow.

Frequently Asked Questions

1. What is a screen reader?

A screen reader is software that reads digital text aloud or converts it to Braille, enabling non-visual access to content

2. Who benefits from screen readers?

People with full visual impairment or low vision, individuals with cognitive impairments, and those with temporary visual issues.

3. Are screen readers only for websites?

No. They are also used in mobile apps, documents, software interfaces, and operating systems.

4. Do all websites work with screen readers

Not by default. Websites must be designed and coded with accessibility in mind.

5. How do I make my site compatible with screen readers?

Use semantic HTML, label elements properly, provide alt text, and follow accessibility guidelines. Tools like iubenda’s Accessibility Widget can help you get started with most of these improvements.

6. What are ARIA roles?

ARIA (Accessible Rich Internet Applications) roles enhance accessibility by providing additional context, especially for dynamic content.

7. How can I test for screen reader compatibility?

Try screen readers like NVDA or VoiceOver, use browser audit tools, and run real user testing.

8. What is the most popular screen reader

According to WebAIM, JAWS, NVDA, and VoiceOver are the most commonly used.

9. Can I use automated tools to fix accessibility issues?

They can help detect issues, but manual testing and proper coding practices are essential.

10. Where can I learn more?

Visit iubenda’s Accessibility Widget for more resources and tools.

The post How to make your website screen reader-friendly (and why it matters) appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> https://www.iubenda.com/en/help/182466-web-content-accessibility-guidelines/ Wed, 04 Jun 2025 14:50:29 +0000 https://help.iubenda.com/?p=182466 Making your digital content accessible to everyone isn’t just good UX, it’s a legal and ethical imperative.  For organizations looking to improve digital inclusion, the Web Content Accessibility Guidelines (WCAG) are the global standard. But despite their importance, many teams find WCAG intimidating and hard to apply in real-world projects. WCAG provides the framework used […]

The post What are the Web Content Accessibility Guidelines – and how do you meet them? appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> Making your digital content accessible to everyone isn’t just good UX, it’s a legal and ethical imperative. 

For organizations looking to improve digital inclusion, the Web Content Accessibility Guidelines (WCAG) are the global standard. But despite their importance, many teams find WCAG intimidating and hard to apply in real-world projects.

WCAG provides the framework used by most digital accessibility laws worldwide, including the Americans with Disabilities Act (ADA) and the European Accessibility Act (EAA). Whether you’re building a new site or auditing existing content, WCAG is likely the compliance benchmark you’ll need to meet.

Don’t worry, we’ve got you covered – this article will walk you through the essentials:

• What WCAG is and why it matters
• How it’s structured (versions, levels, and principles)
• Common challenges and how to overcome them
• Practical steps and tools to help you get started

This guide will help you make sense of WCAG and begin implementing it with confidence.

In short

• What are the Web Content Accessibility Guidelines (WCAG)?
• Why WCAG matters for web accessibility
• WCAG versions: Understanding 2.0, 2.1, and 2.2
• The four principles of WCAG (POUR)
• WCAG conformance levels: A, AA, and AAA explained
• Key WCAG guidelines every website should follow
• Common barriers to WCAG compliance
• How to make your website WCAG compliant
• Best tools for WCAG accessibility testing

What are the Web Content Accessibility Guidelines (WCAG)?

The Web Content Accessibility Guidelines are internationally recognized standards for making digital content accessible to people with disabilities. Developed by the World Wide Web Consortium (W3C) through its Web Accessibility Initiative (WAI), WCAG provides a comprehensive set of guidelines that apply to websites, mobile apps, digital documents, and other online services.

The goal of WCAG is simple: to make content perceivable, operable, understandable, and robust for all users. Especially those with visual, auditory, motor, or cognitive impairments. 

These guidelines are not just best practices, they’re the foundation for most global digital accessibility laws.

If your organization is subject to regulations like the ADA (in the U.S.), Section 508, or the European Accessibility Act (EAA), WCAG is likely the standard you need to follow. Most laws specifically reference WCAG 2.1 Level AA as the minimum threshold for compliance.

Importantly, WCAG is technology-neutral. It doesn’t tell you how to code, it tells you what the outcome should be. So, it can be applied across platforms, devices, and development frameworks.

Why WCAG matters for web accessibility

The WCAG matters because it helps make the internet usable by everyone. For the 1.3+ billion people worldwide who live with a disability (WHO, 2023), WCAG compliance can mean the difference between accessing services, or being excluded from them entirely.

But WCAG doesn’t just benefit users. It also helps businesses:

Get on the road to compliance

Most digital accessibility laws, including the ADA (U.S.), Section 508 (U.S. federal agencies), and the European Accessibility Act, use WCAG as their technical benchmark. Failing to comply can lead to lawsuits, fines, or being excluded from public-sector contracts.

Improve user experience for all

Clear navigation, descriptive links, readable text, and alternative formats aren’t just useful for users with disabilities; they benefit everyone. Inclusive UX often leads to fewer errors, longer sessions, and better conversions.

Boost SEO and discoverability

WCAG-aligned content tends to follow best practices like semantic HTML, alt text for images, and clean heading structures – all of which are also favored by search engines.

Build trust and brand reputation

Meeting WCAG shows that your organization cares about equity, ethics, and user well-being – values that increasingly influence customer decisions.

WCAG versions: Understanding 2.0, 2.1, and 2.2

The WCAG has evolved over time to keep pace with how we use technology. While the core principles have remained the same, each version of WCAG introduces new success criteria to address emerging accessibility needs – especially for mobile, cognitive, and low-vision users.

WCAG 2.0 (Published 2008)

This foundational version introduced the POUR framework and the concept of three conformance levels (A, AA, AAA). It remains the legal standard in some regions, but is now largely superseded.

WCAG 2.1 (Published 2018)

WCAG 2.1 added 17 new success criteria to better address mobile accessibility, touch interactions, zooming/scaling, and additional support for people with cognitive and vision-related disabilities.

Most accessibility laws – including the EAA and ADA – now refer to WCAG 2.1 Level AA as the compliance benchmark.

WCAG 2.2 (Published 2023)

The latest version builds on 2.1 with nine new success criteria focused on navigation, input help, and cognitive support (e.g., clear focus indicators, accessible authentication).

What about WCAG 3.0?

WCAG 3.0 is under development and will represent a major shift – but it’s not a current requirement. Stick with 2.1 Level AA for now unless your jurisdiction mandates 2.2.

The four principles of WCAG (POUR)

At the heart of the WCAG are four foundational principles. These principles – Perceivable, Operable, Understandable, and Robust (POUR) – ensure that content is accessible across a wide spectrum of user needs and technologies.

Perceivable

Users must be able to detect and interpret content using one or more senses.

Examples:

• Provide alt text for images so screen readers can describe them
• Use captions and transcripts for video and audio content
• Ensure sufficient color contrast between text and backgrounds
• Avoid relying solely on color to convey meaning

Operable

Users must be able to navigate and interact with all interface elements.

Examples:

• Enable full keyboard navigation for users who don’t use a mouse
• Use visible focus indicators to show where the cursor is
• Avoid keyboard traps (i.e., where a user gets stuck on an element)
• Give users enough time to complete actions

Understandable

Users must be able to comprehend the information and how to interact with the interface.

Examples:

• Use clear, predictable navigation
• Write in plain language
• Label form fields and buttons clearly
• Provide helpful error messages and suggestions

Robust

Content must be compatible with a range of devices and assistive technologies.

Examples:

• Use semantic HTML and ARIA roles correctly
• Ensure content works across browsers, devices, and screen readers
• Validate code for accessibility and responsiveness

POUR gives teams a structured way to think about accessibility – and a flexible framework to guide implementation.

POUR gives teams a structured way to think about accessibility – and a flexible framework to guide implementation.

WCAG conformance levels: A, AA, and AAA explained

WCAG defines three levels of conformance – A, AA, and AAA – which represent increasing levels of accessibility. These levels help organizations prioritize and plan their accessibility efforts.

Level A – Minimum accessibility

This is the baseline. Meeting Level A means your content avoids major blockers that would completely prevent some users from accessing it.

Examples:

• Alt text on images
• Keyboard navigation
• Avoiding flashing content that could trigger seizures

Level A is essential, but it doesn’t ensure a usable experience for many users.

Level AA – Legal and practical standard

Level AA includes all Level A requirements, plus additional criteria that address color contrast, form errors, navigation consistency, and more.

Examples:

• Minimum 4.5:1 color contrast for text
• Descriptive link text
• Visible focus states for interactive elements
• Error suggestions for form inputs

Most accessibility laws, including the ADA and EAA, require WCAG 2.1 Level AA as the minimum compliance level.

Level AAA – Maximum accessibility

Level AAA includes the most advanced criteria, such as:

• Live sign language interpretation for media
• 7:1 contrast for all text
• Context-sensitive help throughout

It’s not always practical to meet every AAA guideline, but teams can adopt specific AAA techniques where feasible – especially for critical content.

Key WCAG guidelines every website should follow

While WCAG includes dozens of success criteria, some guidelines consistently have the most immediate impact on accessibility and user experience. If you’re working toward WCAG 2.1 Level AA compliance, these are the areas to prioritize:

Provide alt text for images

Every meaningful image should include a descriptive alt attribute so screen readers can convey the content to users who are blind or have low vision. Decorative images should use empty alt text to avoid cluttering the user experience.

Ensure sufficient color contrast

Text must have a contrast ratio of at least 4.5:1 against its background. This ensures readability for users with visual impairments or color blindness.

Support full keyboard navigation

All interactive elements – like menus, buttons, and forms – must be accessible using only a keyboard. Avoid traps and make sure focus indicators are clearly visible.

Make links and buttons descriptive

Avoid vague link text like “click here.” Instead, describe the destination or action – e.g., “Download the report.”

Provide clear form instructions and error messages

Forms must include labels, input instructions, and accessible feedback for errors or required fields.

Common barriers to WCAG compliance

Implementing WCAG can feel overwhelming – especially for teams juggling multiple priorities, legacy systems, and tight timelines. Here are some of the most common obstacles organizations face and how to navigate them:

Legacy code and outdated CMS templates

Older websites often lack semantic HTML or keyboard-friendly components, making retrofitting for accessibility difficult.

Solution: Start by auditing high-impact pages (e.g., homepage, checkout, forms) and incrementally refactor components using WCAG-aligned design patterns.

Lack of in-house expertise

Not every team has an accessibility specialist or frontend developer familiar with WCAG.

Solution: Use trusted tools, training materials, and accessibility libraries. Consider engaging accessibility consultants or using tools like iubenda’s Accessibility Widget for a fast start.

Misinterpreting WCAG language

WCAG documentation can be technical and dense, especially for non-developers.

Solution: Focus on user impact over legal wording. Many success criteria boil down to good UX: clarity, consistency, and flexibility.

Siloed ownership across teams

Design, content, and development often work in isolation – making accessibility harder to coordinate.

Solution: Make accessibility a shared responsibility. Bake it into your design systems, QA processes, and product KPIs.

The path to compliance doesn’t have to be perfect, just proactive and ongoing.

How to make your website WCAG compliant

WCAG compliance doesn’t have to happen all at once. The most effective way to meet the guidelines is to take a phased, practical approach – starting with high-impact improvements and building toward long-term sustainability.

Here’s a step-by-step strategy to help you get started:

1. Run an accessibility audit

Use a combination of automated tools (like WAVE, axe, or Lighthouse) and manual testing (keyboard navigation, screen reader checks, zoom/resizing) to identify barriers on your site.

2. Prioritize what to fix

Focus first on:

• High-traffic or conversion-critical pages (e.g., forms, checkout, login)
• Issues affecting core WCAG 2.1 Level AA criteria
• Quick wins with high usability impact (e.g., contrast, alt text, link clarity)

3. Implement accessibility enhancements

Fix content and design issues directly where feasible. For broader support, consider using iubenda’s Accessibility Widget to implement scalable, standards-aligned improvements.

4. Build accessibility into your workflow

Make sure that new content, pages, and features are reviewed for accessibility as part of your design and dev process. Use inclusive design components, accessible patterns, and checklists in your design system.

5. Review regularly

Accessibility isn’t a one-time fix. Schedule periodic audits and stay updated as WCAG evolves – make it a recurring part of QA and governance.

WCAG compliance is an ongoing journey – but each improvement brings you closer to a more inclusive and resilient product.

Best tools for WCAG accessibility testing

Testing is a crucial step in achieving and maintaining WCAG compliance. While no tool can catch every issue, the right combination of automated and manual methods can significantly reduce accessibility gaps.

Here are some of the most trusted tools to help your team:

Automated testing tools

• WAVE (WebAIM) – Browser-based tool for checking contrast, structure, and ARIA issues
• axe DevTools – Chrome/Firefox extension that flags WCAG violations and suggests fixes
• Google Lighthouse – Built into Chrome DevTools; scores accessibility and performance
• Siteimprove / Deque / Tenon – Enterprise-level automated testing and monitoring solutions

Manual and assistive tech testing

• NVDA (Windows) / VoiceOver (Mac) – Free screen readers for real-world interaction testing
• Keyboard-only navigation – Tab through your site to test focus order and usability
• Zoom and scaling – Ensure layout remains usable at 200% magnification or more
• Color contrast checkers – Test color pairings for WCAG ratios (e.g., WebAIM, TPGi)

Even small testing efforts can surface issues that make a major difference in usability, especially for people relying on assistive technologies.

Make WCAG compliance part of your digital strategy

WCAG is more than a set of technical requirements. It’s a roadmap to creating digital experiences that are inclusive, legally compliant, and genuinely user-friendly. Whether you’re building new products or auditing existing ones, aligning with WCAG 2.1 Level AA is a powerful way to reduce risk and improve reach.

You don’t have to do it all at once. Focus on high-impact fixes, build accessibility into your workflows, and use the right tools to track your progress.

The post What are the Web Content Accessibility Guidelines – and how do you meet them? appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]> https://www.iubenda.com/en/help/182116-compliance-for-international-websites/ Thu, 29 May 2025 04:50:28 +0000 https://help.iubenda.com/?p=182116 Legal documents tailored for you Multi-language legal documents and compliance for international websites Did you know that if you target users in multiple countries, your legal documents must be translated into their language? Not only to comply with legal requirements, but also to build trust with each visitor. With iubenda, you can do this easily, […]

The post compliance for international websites – prospects appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

]]>

Legal documents tailored for you

Multi-language legal documents and compliance for international websites

Did you know that if you target users in multiple countries, your legal documents must be translated into their language? Not only to comply with legal requirements, but also to build trust with each visitor. With iubenda, you can do this easily, without worrying about translation errors or manual updates.

Try iubenda now

Why choose iubenda

Translate your legal documents into multiple languages

With iubenda you can automatically translate your privacy policy, Terms and Conditions and cookie banner into multiple languages with one click. All your legal documents will always be up to date, without having to rewrite them every time you add a new language. And these are not approximate translations: we rely on legal experts and specialised translators to help you comply with regulations.

Adapt your cookie banner with geolocation

With geolocation, iubenda automatically detects the location of your users and adapts your cookie banner according to local regulations. This means it will ask for explicit consent from European users, while giving US users the option to opt-outt. So you don’t have to worry about complicated manual implementations and can maximize your consent rate.

Simplify your online privacy hurdles

Regulations and guidelines are a winding maze. Start your compliance journey with a trusted suite of features that do the hard work for you.

Cookie and Consent Banner Privacy and Cookie Policy Terms and Conditions

NEW

Website Accessibility Advanced Solutions

Back

Privacy Controls and Cookie Solution

Easily add a cookie and consent banner to your site or app to automatically block cookies and manage user preferences with Google Consent Mode built in.

Take a look

Back

Privacy and Cookie Policy Generator

Our scanner detects the services on your site to generate a fully customizable, self-updating privacy and cookie policy with lawyer-drafted text available in 15+ languages.

Take a look

Back

Terms and Conditions Generator

Follow a guided setup to create T&Cs tailored to your e-commerce, blog, app, and more with lawyer-drafted text available in 15+ languages.

Take a look

Back

Accessibility Solution

Add an AI-powered accessibility widget to your site to automatically optimize for users with disabilities and help meet EAA requirements with just one line of code.

Take a look

Back

Streamline compliance and marketing processes

Manage and store consents across multiple platforms, handle data subject requests and whistleblowing reports, optimize newsletter opt-ins, and more.

Consent Database

Store and sync consent records across multiple platforms.

Take a look

Newsletter Opt-in Booster

Boost newsletter signups with a customizable widget.

Take a look

Whistleblowing Management Tool

Establish an internal reporting channel for whistleblower reports.

Take a look

Data Subject Rights Management Tool

Handle data subject requests through a centralized, intuitive platform.

Take a look

Register of Data Processing Activities

Document data processing activities within your organization.

Take a look

Trusted by over 150,000 clients in 100+countries

“If you, like me, are part of a smart team and hate updating your privacy policy every time you add some code to your site, then iubenda is for you. It's ridiculously affordable, and super easy to use.”

Try iubenda now

The post compliance for international websites – prospects appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Legacy user? If you’re on our license-based plans (Pro and Ultra), please see the old guide here →

You can permanently cancel or temporarily pause your iubenda subscription directly from your account settings.

Your iubenda subscription is usually set to renew on a monthly/yearly basis via our auto-renewal feature.

To cancel, you’ll need to disable the auto-renewal of your subscription. Here’s how:

• Log in to your iubenda account and go to your dashboard;
• Go to the page of your website/app for which you want to manage the subscription;
• Once there, click on the “Settings” icon next to the URL title at the top (see image below);

• In the settings, go to the “Manage subscription” tab on the left-side menu;
• Scroll down and enable or disable the auto-renewal using the dedicated toggle (see image below);
• Confirm and hit “Save” on the bottom right.

In case of any issues, please get in touch with our support and we’ll gladly help you out.

See also

• Why Is the iubenda Service on a Recurring Basis?
• How Do I Update Payment Information?
• How to Delete Your iubenda Account

The post How to Cancel Your iubenda Subscription appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Heads-up! This is our legacy guide for license-based (Pro and Ultra) plans. If that doesn’t sound familiar and you’re on our most recent pricing, over here.

To temporarily pause or permanently cancel your subscription, you need to go to your iubenda account and disable auto-renewal for this subscription.

To do so, please follow the steps below:

• Go to the Account & Billing info section of your iubenda account;

• Once there, scroll down to the “Manage Plans” section;
• Select the subscription you want to cancel (click the white circle on the left, a green dot should show);
• Click the gray “Enable/disable auto-renewal” button and confirm.

In case of any issues, please get in touch with our support and we’ll gladly help you out.

See also

• Why Is the iubenda Service on a Recurring Basis?
• How Do I Update my Payment Information?
• How to Delete Your iubenda Account

The post How to Cancel Your iubenda Subscription [Legacy Guide] appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

In this guide, we’ll show you why it’s necessary to make this info easy to find and walk you through the simple steps to create a direct link that takes customers straight to the withdrawal section in your Terms & Conditions Document. That way, your customers can easily see their rights before completing a purchase.

Why Is the Withdrawal Policy Link So Important?

Many countries have laws requiring sellers to inform customers about their right to cancel orders and get refunds. Simply hiding this info inside long T&Cs is not enough. For example, a German court ruled in 2015 that the key requirement is that consumers must be clearly informed about their right of withdrawal in a manner appropriate to the means of communication used, such as an explicit and well-labeled link during the ordering process. It’s not enough to just say “see our T&Cs” — customers need an obvious, easy-to-find link.

According to the German court, this requirement is based on Article 246a, Section 4, Paragraph 1 of the EGBGB, a German legal provision that says:

“The business operator must provide the consumer with the information required under Sections 1 to 3 clearly and understandably before the consumer submits their contractual declaration.”

This means that customers should not have to search through long documents or guess where the withdrawal policy is. The right of withdrawal exists to inform customers that they even have this right. So, the information must stand out clearly during the buying process.

In other words, although incorporating a cancellation policy into the T&Cs is allowed, you must also present information about the right of withdrawal in a clear and easy-to-understand way before the customer completes their order. This can be implemented, for example, with a direct link to the relevant section within the T&Cs.

Step-by-Step: How to Create a Link to Your Withdrawal Section

You can easily add a link to your withdrawal or cancellation policy section inside your Terms and Conditions document. Here’s how:

Set Up Your Withdrawal Policy First

Before creating your withdrawal policy link, select the relevant clauses under “User rights — required by law or offered voluntarily by you” in the iubenda Terms and Conditions Generator. This ensures your Terms & Conditions document include the correct withdrawal information for the link to point to.

1. Find Your Terms and Conditions URL

Get the URL where your full T&Cs are published. It usually looks like this:

2. Add the Special Section Tag

At the end of your T&Cs URL, add #user-rights so the link points directly to the withdrawal section. Your link should look like this:

https://www.iubenda.com/terms-and-conditions/123456#user-rights

3. Create Your Link Text

Decide what you want the clickable text to say. It can be “Returns and refunds,” “Withdrawal Policy,” or anything clear for your customers.

4. Write the Full HTML Link

Use this format to create the clickable link on your website or checkout page:

<a href="https://www.iubenda.com/terms-and-conditions/123456#user-rights">Withdrawal Policy</a>

Replace the URL and link text with your own details.

5. Place the Link Where Customers See It

Add this link somewhere easy to find, such as on your checkout page or near the order confirmation button. This makes sure customers see it before completing their purchase.

<a href="https://www.iubenda.com/termini-e-condizioni/123456#diritti-dell-utente">Resi e rimborsi</a>

Making sure your withdrawal policy is easy to find isn’t just a good idea — it’s often required. The rules say you must show this information clearly and in a way that customers can understand before they finish their purchase. When you add a direct link to the withdrawal section and put it somewhere customers can easily see, like on your checkout page, you make things easier and clearer for everyone.

The post How to Create a Link That Directs Customers to Your Withdrawal Policy Section appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

But in the real world, users are far more diverse. They may have visual impairments, limited mobility, temporary injuries, low-bandwidth connections, aging-related challenges, or cognitive differences.

When digital experiences aren’t built to reflect this diversity, the result is frustration, exclusion, and, of course, lost opportunity.

Inclusive design is a methodology that challenges this status quo. It focuses on building products and services that are usable by the widest possible range of people, regardless of ability, context, or circumstance. 

Essentially, inclusive design is proactive, not reactive. It goes beyond basic accessibility by embracing human variety as a core design driver.

In this guide, we’ll explore what inclusive design really means, how it differs from accessibility, and how your organization can start putting it into practice, using proven principles, real-world examples, and actionable steps.

What is inclusive design?

Inclusive design is a design methodology that creates products and experiences that can be used by as many people as possible, regardless of circumstance, ability, background, or environment.

It recognizes that human diversity is the norm – not the exception – and that good design must accommodate that diversity

Rather than treating inclusion as an afterthought or a checkbox, inclusive design starts by identifying and addressing barriers that might exclude users. It’s about designing with a deep understanding of the full spectrum of human needs, from permanent disabilities to temporary limitations (like a broken arm or noisy environment) and situational constraints (like bright sunlight or using a device with one hand).

Importantly, inclusive design isn’t just for people with disabilities; it benefits everyone. For example, captions help people with hearing impairments, but they’re also useful for watching videos in public spaces. And voice input aids users with mobility impairments, but is now mainstream in mobile UX.

Why inclusive design matters

Inclusive design isn’t just a feel-good initiative; it’s a critical strategy for building better digital products. When done well, it leads to improved usability, stronger brand trust, and broader market reach.

It promotes equity and digital inclusion

At a societal level, inclusive design helps make sure that people aren’t left behind due to disability, age, language, or context. It’s a way to reduce digital inequality, uphold human rights, and create fairer experiences for everyone.

It expands your audience and customer base

Globally, over 1.3 billion people live with some form of disability (WHO, 2023). Add to that users with temporary limitations, older adults, or low-tech environments – and the number of people who benefit from inclusive design grows exponentially.

Designing for inclusivity doesn’t narrow your scope; it actually opens your product to more people, more use cases, and more markets.

It improves UX for everyone

When you reduce cognitive load, simplify interfaces, or clarify instructions, you’re not just helping edge-case users, you’re improving the experience for all. Inclusive products tend to be cleaner, more intuitive, and easier to use.

It supports compliance and reduces legal risk

Inclusive design principles often overlap with accessibility standards like WCAG, which are the foundation for laws like the European Accessibility Act and the ADA. Embedding inclusion into your design process can help you stay compliant and reduce risk.

Inclusive design vs. accessibility: What’s the difference?

Inclusive design and accessibility are closely related, but they’re not interchangeable.

• Accessibility refers to technical standards and legal requirements that make sure people with disabilities can access digital content and services. These are often codified in frameworks like the Web Content Accessibility Guidelines (WCAG) and are essential for compliance with regulations such as the ADA or the European Accessibility Act.
• Inclusive design, on the other hand, is a broader design philosophy. It starts earlier in the process and focuses on creating experiences that are usable by a wide range of people. It includes considerations like:
  • Language simplicity
  • Device and environmental constraints
  • Cultural context
  • Situational challenges (e.g., using one hand while holding a child)

They work best together. Accessibility is a baseline. Inclusive design takes things further, ensuring your digital products are flexible, welcoming, and effective for the widest possible audience.

Key principles of inclusive design

Inclusive design is guided by a set of core principles that help teams build products that serve the full range of human diversity. These principles can be used as both a design lens and a decision-making framework, no matter the size of your team or product.

Let’s take a look at the most widely recognized principles:

1. Recognize exclusion

Start by identifying who might be left out of your experience. Exclusion happens when we assume all users are the same, able-bodied, fluent in the product language, using modern hardware, or always online. Use empathy interviews, analytics, and testing to uncover pain points and edge cases.

2. Solve for one, extend to many

Designing for individuals with specific needs often benefits everyone. This principle flips the idea of “edge case” on its head by treating these cases as innovation drivers.

3. Learn from diversity

Inclusive design teams actively seek input from people of different backgrounds, abilities, languages, and contexts. Feedback from diverse users results in better-informed, more effective design decisions.

As a result, YouTube introduced a collapsible comment section and simplified the layout – changes that improved the experience for everyone, not just users with cognitive differences.

4. Provide equivalent experience

Users might interact with your product differently, but they should get the same core value.

5. Offer choice and control

Give users options to personalize or adapt their experience based on preference or need.

6. Prioritize clarity

Use simple language, consistent layouts, and familiar interaction patterns to reduce cognitive load.

Real-world examples of inclusive design in action

Inclusive design isn’t theoretical, it’s already improving experiences for millions of people across industries. Here are a few standout examples of how organizations have embraced inclusive design in the real world:

GOV.UK

The UK government’s digital services platform is a model of clarity and accessibility:

• Uses plain language that’s understandable by all reading levels
• Consistent, keyboard-navigable layouts
• Focus indicators and screen reader compatibility are built in
• Content designed for mobile and low-bandwidth users
  

This approach benefits not only users with disabilities but also non-native English speakers, older adults, and people with slow connections.

Microsoft’s inclusive product development

Microsoft’s inclusive design toolkit has shaped products like the Xbox Adaptive Controller, which was created with direct input from gamers with limited mobility.

• Flexible inputs and accessible packaging
• Usable by players with a range of physical abilities
• Became a UX benchmark and brand differentiator
  

Apple’s customizable UX

Apple integrates inclusive features into the core of its products:

• Dynamic text sizing and screen magnification
• VoiceOver screen reader is built into every device
• Background sounds and audio descriptions for better focus and comprehension

These tools are beneficial to users with disabilities, and also useful to people who simply prefer different interaction styles.

Airbnb’s inclusive onboarding

• Image descriptions for listings
• Language-localized support for a global user base
• Inclusive filters for finding accessible accommodation

How inclusive design improves user experience (UX)

Inclusive design doesn’t just make digital products more usable for people with disabilities – it leads to better experiences for all users.

Why? Because inclusive design principles focus on clarity, flexibility, and removing friction – goals that align perfectly with great UX.

Such as:

Reduced cognitive load

Simpler interfaces, consistent navigation, and clear language help users complete tasks faster and with less confusion. That’s especially important for users with cognitive or learning differences – but it benefits everyone, especially under pressure or on mobile.

Improved usability across devices and contexts

Designs that adapt to different screen sizes, input methods, and internet speeds are essential for people with limited access, and also crucial for global audiences, mobile-first users, and multitaskers.

Fewer errors, higher satisfaction

Clear error messages, flexible interactions (e.g., voice, keyboard, mouse), and intuitive layouts reduce user frustration and dropout rates, improving satisfaction and conversion.

Broader engagement

When products are inclusive by default, they reach more people – across abilities, languages, and cultures – leading to increased trust and market growth.

In short, inclusive design is great UX, scaled to real-world diversity.

Steps to implement inclusive design in websites and apps

Inclusive design isn’t a one-time project, it’s a mindset that should be woven into every stage of your product development lifecycle. Here’s how your organization can start building more inclusive digital experiences, step by step:

1. Audit your current experience for exclusion risks

Begin by identifying friction points in your existing website or app. Use both automated tools and manual testing to assess:

• Accessibility gaps (e.g., contrast, alt text, keyboard nav)
• Language complexity
• Navigation barriers
• Form usability

2. Involve diverse users in research and testing

Don’t rely on assumptions. Engage users with a range of abilities, backgrounds, languages, and devices in your UX research, user interviews, and us 

Their feedback will highlight problems – and reveal better design solutions you may not have considered.

3. Train your team on inclusive design principles

Help your designers, developers, and content creators understand what inclusive design looks like in practice. Build internal guidelines, share resources, and encourage team-wide ownership.

4. Bake inclusivity into your design system

Update your component library to include accessible UI patterns, alt text conventions, contrast rules, and responsive behavior. The more baked-in it is, the easier it is to scale.

5. Test early, test often

Use real devices and assistive technologies to evaluate inclusivity throughout the development process, not just at launch.

Common barriers to inclusive design (and how to overcome them)

Despite its clear benefits, inclusive design can feel challenging to implement, especially for small teams or organizations without in-house accessibility expertise. 

Here are some of the most common barriers and how to move past them:

“It’s too expensive or time-consuming.”

Reality: Inclusive design becomes costly when it’s an afterthought. But when it’s embedded from the start – during research, design, and development – it saves time and prevents expensive retrofits.

Solution: Adopt a “design for inclusion by default” mindset. Use inclusive templates and test early to avoid costly changes later.

“We don’t have the right team or tools.”

Reality: You don’t need to be an expert in usability to get started.

Solution: Use publicly available resources, tools like contrast checkers or screen reader emulators, and consult toolkits like Microsoft’s Inclusive Design Guide. When in doubt, start small and iterate.

“We’re afraid of getting it wrong.”

Reality: The only real mistake is not trying. Inclusive design is a process of learning, testing, and improving.

Solution: Get feedback from diverse users, document your decisions, and be transparent about your intent. Progress is better than perfection.

Best practices for creating inclusive content and interfaces

Inclusive design extends beyond layout and color contrast, it’s just as much about the language, structure, and interaction patterns you use. 

Here are some key practices to apply across your digital content and user interfaces:

Use plain, inclusive language

• Write for clarity – avoid jargon, idioms, and cultural references that may not translate
• Use gender-neutral language unless context requires otherwise
• Break up complex ideas into short, scannable sentences and paragraphs

Go for visual clarity and flexibility

• Maintain a minimum color contrast ratio of 4.5:1 for text and background
• Use scalable fonts and support text resizing without layout breaks
• Choose accessible typefaces (e.g., sans-serif, dyslexia-friendly fonts)

Design for different interaction styles

• Don’t rely on color alone to convey meaning (e.g., red = error)
• Make all controls accessible via keyboard and screen readers
• Use clear, descriptive link text (avoid “click here”)

Tools and resources for inclusive design

Whether you’re just starting out or scaling inclusive practices across your team, the right tools can help you move faster and smarter. Here’s a selection of practical resources to guide your journey:

Testing and simulation tools

• WAVE – Web accessibility evaluation tool for spotting common issues
• axe DevTools – Chrome extension for automated WCAG checks
• VoiceOver / NVDA – Screen readers for manual testing
• Color Oracle – Simulates color blindness for design reviews

Design and content resources

• WebAIM Contrast Checker – Test color combinations for readability
• Microsoft Inclusive Design Toolkit – Practical exercises and personas
• Google Fonts accessibility collection – Readable and scalable typefaces
• Plainlanguage.gov – Guide to clear, inclusive writing

Design that includes is design that works

Inclusive design isn’t just about checking accessibility boxes, it’s about building better, more usable products for everyone. By intentionally designing for a wider range of needs and contexts, your team can deliver experiences that are more effective, more empathetic, and more aligned with how people actually live and work.

It starts with a shift in mindset – and continues through research, collaboration, and iteration.

The post Inclusive design principles: How to build digital experiences that work for everyone appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Digital accessibility has moved beyond an add-on; it’s a legal obligation for many businesses operating in Europe. 

The European Accessibility Act (EAA), which came into full force on June 28, 2025, introduces a unified set of accessibility requirements for websites, mobile apps, and other digital products and services.

The goal? To make sure that people with disabilities can access and use digital services as easily as everyone else. But for many businesses – especially those without in-house accessibility experts – the path to accessibility can feel unclear and overwhelming:

• Who needs to comply?
• What are the specific accessibility requirements?
• How do you assess your current level of compliance?
• And what practical steps can you take to meet the standard?

This guide provides those answers. Whether you’re in legal, product, design, or development, we’ll break down the EAA’s key requirements, show how they affect your digital properties, and offer a clear framework for achieving accessibility.

Who needs to comply with the European Accessibility Act?

The EAA applies to a wide range of businesses operating in or serving consumers within the European Union. 

But which businesses does it actually affect?

The short answer: most B2C digital service providers.

You may be required to comply if you:

• Operate an e-commerce platform or sell products online
• Offer banking or financial services
• Provide transport booking systems (bus, rail, air, etc.)
• Run a media platform, including video, audio, or streaming
• Publish eBooks or digital reading tools
• Deliver telecommunications services
• Offer public-facing websites or mobile apps
• Serve EU consumers, even if you’re based outside the EU

Some common myths about compliance

You might have had these thoughts in the past, but they’re (probably) not accurate:

• “We’re too small.” → Size is usually not a determining factor for accessibility compliance (with minor exceptions).
• “We’re not in the EU.” → If your service targets or reaches EU consumers, you’re likely in scope.
• “We only sell physical goods.” → Your digital interfaces (website, checkout, app) still need to comply – as do some physical goods!
  

Key requirements for EAA compliance

The EAA doesn’t just recommend better digital experiences – it mandates them. Businesses affected by the EAA must make sure that their digital products and services are accessible to people with disabilities, based on a consistent set of requirements across EU member states.

What must be accessible?

The EAA applies to a range of digital assets, including:

• Websites and web applications
• Mobile apps
• e-commerce platforms and online stores
• Self-service terminals (e.g., ticketing machines, ATMs)
• eBooks and reading software
• Audio-visual media players
• Digital customer service interfaces

Basically, any interface a user interacts with to access or manage a service is likely covered.

What does accessible mean under the EAA?

To comply with the EAA, digital services must follow technical accessibility standards, namely:

• Conformance with the following:
  • Alt text for non-text content
  • Keyboard navigability
  • Screen reader compatibility
  • Text resize options without loss of functionality
  • Sufficient color contrast
  • Consistent navigation patterns
  • Descriptive form labels and error messages
  • Captions and transcripts for video/audio content

How the EAA affects digital services and websites

The EAA applies to more than just how information is presented; it also affects how digital services are designed, built, and maintained. This includes user flows, interface components, media content, and even the technologies used to build your site or app.

If your business relies on digital channels to deliver services – whether it’s an online shop, customer portal, mobile app, or media platform – EAA compliance must be part of your strategy.

E-commerce platforms

Online stores must allow all users to:

• Browse, select, and purchase products
  
• Read product descriptions via screen readers
  
• Navigate the checkout using only a keyboard
  
• View accessible error messages for failed form inputs

Banking and financial services

Secure portals and apps must:

• Be navigable without a mouse
• Provide accessible 2FA interfaces and forms
• Offer downloadable documents (e.g., PDFs) in accessible formats
  

Streaming platforms and digital media

Audio-visual content must include:

• Captions for spoken content
• Transcripts for audio-only files
• Interfaces that work with assistive technology
  

Design systems and navigation patterns

All services must make sure there are:

• Consistent layouts across pages
• Clear focus indicators for interactive elements
• Semantic HTML and proper heading structure for screen readers

In short, digital accessibility affects nearly every layer of the user experience. So getting on the road to compliance means designing for inclusion from the start.

Steps to achieve EAA compliance

Meeting the EAA’s requirements doesn’t have to mean a complete overhaul from day one. With a structured, phased approach, organizations can start making meaningful improvements right away – then scale toward heightened compliance.

Here’s a practical framework to guide your team.

1. Audit your digital assets

Start by assessing your website, apps, and digital products to understand where you stand. Combine:

• Automated tools like WAVE, axe DevTools, or Google Lighthouse
• Manual testing using screen readers (NVDA, VoiceOver)
• Keyboard-only navigation testing
• User testing, where possible, with real users who use assistive tech
  

2. Prioritize issues by impact and visibility

Identify the key areas of focus:

• High-traffic pages (home, product, checkout, login)
• Critical forms and user journeys
• Non-compliant media (videos, PDFs, interactive content)

NOTE: Make sure that you use WCAG 2.1 Level AA and the EAA annexes as your technical benchmark; it’s important.

3. Fix the most common accessibility barriers

Start with achievable fixes that make a big difference:

• Add alt text to all meaningful images
• Ensure form fields have labels and accessible error messaging
• Adjust color contrast and allow text resizing
• Fix heading structures for semantic HTML
• Add captions and transcripts to media content
  

4. Use iubenda’s Accessibility Widget for fast impact

The iubenda Accessibility Widget allows teams to make progress quickly:

• Adds essential accessibility enhancements
• Helps meet WCAG 2.1 Level AA criteria
• Offers a simple path to demonstrate proactive accessibility
  

5. Educate and enable your teams

Make sure that product, design, marketing, and dev teams:

• Understand the principles of accessible design
• Integrate accessibility checks into QA
• Know where to find standards and reference docs
  

6. Monitor, iterate, and maintain

Accessibility isn’t a one-off project. Make sure you build in:

• Periodic re-audits
• Feedback channels for users
• Governance processes for continuous compliance
  

The common challenges in meeting EAA standards

Many organizations recognize the need for accessibility, but run into roadblocks when they begin implementation. Understanding the most common challenges can help you avoid delays and keep your compliance roadmap on track.

1. Lack of internal expertise

Many teams – especially SMBs – lack in-house accessibility specialists. As a result, compliance can feel overly technical or overwhelming.

The solution: Start small. Use automated testing tools, free learning resources, and accessible design libraries. And when needed, consult external accessibility partners.

2. Legacy systems and outdated tech

Older websites or content management systems may not support semantic HTML, ARIA roles, or screen reader compatibility.

The solution: Prioritize critical pages and work accessibility into scheduled redesigns or updates. Tools like iubenda’s Accessibility Widget can help you start working towards an accessible path.

3. Fragmented responsibility

Accessibility often falls between teams – design, development, marketing, and legal – without a clear owner.

The solution: Assign ownership. Establish an internal lead or working group and include accessibility in your QA and content processes.

4. Misunderstanding legal obligations

Some teams assume the EAA doesn’t apply to them – or they underestimate what’s required to meet WCAG standards.

The solution: Use self-assessment checklists, review the EAA’s scope, and consult legal if needed. Remember: if you serve EU consumers, compliance is likely required.

By addressing these challenges early, your organization can make measurable progress – without getting stuck in the weeds.

Tools and resources for compliance

Whether you’re just starting your accessibility journey or looking to streamline ongoing improvements, the right tools can make all the difference. 

Here’s a selection of reliable resources to help your team achieve and maintain EAA compliance.

Accessibility testing tools

Start with automated scans to catch the most common accessibility issues:

• WAVE – Highlights contrast errors, missing alt text, and semantic structure flaws
• axe DevTools – Chrome extension for developers with actionable WCAG guidance
• Google Lighthouse – Built into Chrome DevTools, includes accessibility scoring
  

Manual testing support

Automated tools only catch 30–40% of issues. Pair them with:

• Screen readers: NVDA (Windows), VoiceOver (Mac)
• Keyboard navigation tests: Use Tab, Shift+Tab, and Enter to navigate your site
• Zoom/resizing tests: Make sure layout and content remain usable at 200% scale

Design and content resources

• Contrast checkers (e.g. WebAIM, Stark)
• Inclusive design principles from W3C and open design systems
• Alt text and media accessibility guides
  

iubenda’s Accessibility Widget

For businesses seeking an immediate step toward accessibility, iubenda’s Accessibility Widget:

• Adds key WCAG 2.1 Level AA enhancements
• Requires no redesign or replatforming
• Supports your ongoing accessibility strategy

Make accessibility a priority

Digital accessibility is no longer optional. With the European Accessibility Act’s enforcement deadline having passed on June 28, 2025, businesses across Europe – and beyond – must make sure their websites, apps, and digital services are accessible to all users.

The good news? You don’t need to do everything at once.

By understanding your legal obligations, identifying accessibility gaps, and making continuous improvements using WCAG 2.1 Level AA as your guide, your organization can reduce risk, expand its audience, and deliver a better digital experience for everyone.

Start now with a simple, scalable solution

The iubenda Accessibility Widget makes it easy to begin addressing requirements right away, without the need for a full rebuild.

Whether you’re in product, compliance, UX, or leadership, taking the first step today can save time, cost, and complexity tomorrow.

The post A complete guide to EAA compliance for digital services appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

94.8% of websites have accessibility issues. Fix them with iubenda!

According to the WebAIM report, 94.8% of homepages have accessibility issues, and the most common errors have been the same for the last five years. In June, the European Accessibility Act will come into force, and many websites will need to comply. But don’t worry: iubenda is here to help!

Discover our Accessibility Solution

What is the WebAIM Million Report?

Every year, WebAIM studies the homepages of the most popular websites to analyze their compliance with the Web Content Accessibility Guidelines (WCAG). In 2025, nearly all homepages have accessibility issues, and the most common errors have been the same for the last five years: low contrast text, missing alt text, missing labels in forms, empty links and buttons, and missing language. Simply fixing these issues could make the internet much more accessible!

What can Accessibility Solution do for you?

Our accessibility interface widget, developed in partnership with AccessiWay, helps make your website more accessible to users with various disabilities automatically – so you can get closer to complying with the EAA, other legislations, and industry guidelines (e.g., WCAG 2.1) without rebuilding your site from scratch.

Make text easier to read Ensure everyone can see your content Create a distraction-free experience

Back

Our widget gives your visitors full control over how content appears. Users can adjust font size, line height, and text alignment with a single click – helping those with visual impairments, dyslexia, or cognitive disabilities navigate your site without frustration.

Back

Not everyone perceives color the same way. Our widget provides options like dark contrast, light contrast, and monochrome views so visitors with color blindness or light sensitivity can comfortably access your website without missing important information.

Back

For many users, website animations and sounds can be overwhelming. Our orientation tools let visitors mute sounds, hide images, use reading guides, and stop animations – creating a focused browsing experience that works for people with ADHD, autism, or epilepsy.

How it works

STEP 1

Add one line of code to your website

The widget appears discreetly in the corner of your site, ready to assist all visitors with their accessibility needs immediately after installation.

STEP 2

AI begins continuous optimization

Our AI scans your site against accessibility guidelines, automatically addressing common issues and optimizing for assistive technologies.

STEP 3

Real-time accessibility adjustments

Users select their preferences and the widget instantly applies the necessary changes to make your site accessible to their needs.

Activate Accessibility Solution

Beyond compliance: see why it pays to be accessible

A more accessible website improves structure, readability, and user experience—all boosting search rankings. 73.4% of websites see increased organic traffic with accessibility improvements.

Improve your page speed with minimal setup time

Get more search traffic by improving site performance

Increase user engagement through improved usability metrics

Reduce bounce rates by creating a more usable experience for all visitors

Boosted branding

Show your commitment to serving all users by making your site accessible. Strengthen your brand reputation and attract customers who value inclusivity and equal access.

More customers

Tap into the $1.9 trillion annual spending power of people with disabilities. An accessible website opens your business to new markets and increases profit potential.

Why choose iubenda?

The most affordable tool in the market

Our widget makes your website more accessible at a fraction of the cost of the other web accessibility tools in the market.

Getting closer to accessibility compliance has never been simpler

Just paste one line of code to get started – it's that easy.

Looking for an enterprise-level accessibility solution?

If your website exceeds 1M pageviews, you need custom accessibility solutions. Our partner AccessiWay provides specialized compliance tools for enterprises with advanced accessibility requirements. Their comprehensive services include:

• Expert consulting

• Detailed accessibility auditing

• Custom implementation support

• Ongoing compliance management

Websites have until June 28, 2025 to comply with the EAA's accessibility requirements.

Start making your website more accessible with iubenda's affordable, user-friendly Accessibility Solution today, or connect with our team to learn more about our enterprise partnership with AccessiWay for advanced accessibility requirements.

Activate Accessibility Solution

Get in touch with AccessiWay

The post 94.8% of websites have accessibility issues appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

In most cases, B2B companies can breathe easy. 

If you run a purely B2B company, the chances are that the EAA does not really apply to your operations.

However, there are key exceptions worth knowing so you don’t get caught out.

In this article, we’ll clarify exactly when B2B companies need to comply with the EAA, walk through common scenarios, and offer some practical steps to reduce risk and improve accessibility where it counts.

Need to make your website more accessible? Learn how iubenda can help.

The European Accessibility Act: Focused on consumer-facing services

The goal of the EAA (Directive 2019/882) is to make sure that any products and services across the EU are accessible to people with disabilities. 

It introduces accessibility requirements for:

• E-commerce websites: Platforms where users can browse and buy goods or services online.
• Banking and financial services: Apps and websites that let consumers manage their finances or make transactions.
• Transport services: Digital booking tools for trains, buses, taxis, and other transport modes.
• E-books and digital reading platforms: Services that offer downloadable or streamable reading materials.
• Communication services like messaging or VoIP: Tools that help users communicate digitally, including video calls and online chats.

Under the law, consumers are defined as “any natural person who purchases the relevant product or is a recipient of the relevant service for purposes which are outside his trade, business, craft or profession” as per Directive 2019/882, Article 2.

This definition is key because it clearly indicates that the law targets B2C operations, not B2B interactions between companies. 

But that doesn’t mean you can stop reading if you run a B2B business. 

When B2B businesses fall outside the EAA’s scope

If your company sells exclusively to other businesses – and doesn’t engage with individual consumers – your digital properties are generally outside the scope of the EAA.

Think of tools like:

• Internal sales systems: Used only by your team to manage deals with other companies, not consumers.
• Password-protected client dashboards: Secure, login-only areas built for business customers.
• Procurement tools or vendor portals: Systems designed solely for managing supplier relationships and purchasing workflows.
• Closed B2B SaaS platforms: Software products that require account access and don’t have a public-facing component.
• Intranets or internal employee tools: Platforms only used by employees, like HR systems or internal knowledge bases.

Essentially, the rule of thumb is that as long as your interfaces are exclusively used by people acting within their trade or profession, the EAA doesn’t apply.

The operative word here is ‘exclusively’. 

So, how can you be sure you’re truly out of scope?

When B2B companies need to comply

Now here’s where it gets a little trickier. If your company offers any public-facing elements that can be used by individual consumers, they are within the EAA’s scope.

Common examples include things like:

• Marketing websites with pricing or product pages: These public pages are often visited by individual consumers researching products or services.
• Public contact or support forms: Open communication channels allow anyone to get in touch – not just businesses.
• Blogs or educational content aimed at individual users: If content is accessible to consumers and meant to inform or attract them, it’s in scope.
• Free tools or demo sign-ups without business verification: If individuals can use or trial your service without identifying as a business, accessibility requirements apply.

Even if your core offering is purely B2B, if someone can stumble across your site and interact with it as an individual, that interaction needs to meet accessibility requirements.

Mixed B2B/B2C business models: Compliance by component

Many companies operate in a hybrid model – offering B2B software or products but maintaining consumer-facing digital assets.

In these cases, compliance needs to be assessed on a section-by-section basis.

Here are some examples where this might apply: 

Asset	Is compliance required?
B2C user portal
Internal CRM
Marketing website with pricing
Sales documentation download portal (public)
Support intranet

It’s important to remember that the 2019/882 directive does not contain an explicit list of examples being in or out of scope. 

Instead, the determination hinges on whether or not the recipient qualifies as a “consumer” based on the legal definition we mentioned earlier. 

Because of this, it’s always a good idea to conduct an accessibility audit that clearly separates consumer-facing areas from internal B2B tools – so you can make sure you’re never caught off guard.

Why accessibility still matters for B2B companies

Even if your risk of legal exposure under the European Accessibility Act as a B2B company is low, accessibility is still a smart business move – no matter what kind of business you run. 

It gives you:

• Better UX for all users: Accessibility best practices make digital experiences clearer and easier for everyone – not just people with disabilities. 
• SEO and performance gains: Search engines reward accessible websites with better indexing and faster load times – so you’re more discoverable, and can offer a better experience. 
• Stronger reputation: Demonstrating inclusion supports employer branding and helps to build customer trust.
• Procurement advantage: Accessibility is increasingly a requirement in vendor selection for large enterprises.

What to do next: Steps for B2B companies

Before diving into any accessibility updates, it’s worth identifying which parts of your digital presence are actually in scope. 

While many B2B platforms are exempt, anything that can be accessed by an individual consumer needs to meet accessibility standards, such as your homepage, contact form, or pricing page.

Here’s a simple approach to get started:

• Step 1: Audit your digital presence. Look for any publicly available pages, tools, or forms that consumers might have access to.
• Step 2: Fix what’s public. Apply WCAG 2.1 standards to components like landing pages, blog posts, and contact forms.
• Step 3: Use accessibility tools wisely. Tools like iubenda’s Accessibility Widget can help with overlays and UI tweaks, but back-end fixes are still essential.
• Step 4: Publish an accessibility statement. Clarify your approach, even if only part of your site needs to comply – it shows transparency and commitment.

Getting ahead of the curve

Even if you’re not strictly required to comply with the EAA, taking proactive steps toward accessibility is good business sense. It improves usability, supports your brand’s reputation, and may even help you win contracts.

In short, it’s about making sure you’re as ready as you can possibly be. 

But remember, tools like iubenda’s Accessibility Widget are just the start. You can’t guarantee full accessibility with just one tool alone, so it’s important to make sure you’re also doing manual checks and utilizing other accessibility tools.  

More and more industries now expect a baseline level of digital accessibility – and B2B is no exception. Forward-thinking B2B companies that embed inclusive design into their workflows will be better placed to compete, adapt, and grow.

And remember, an accessible site is a user-friendly site. 

FAQs on EAA and B2B

1. Does the EAA apply to B2B-only companies?

The EAA specifically targets consumer-facing interactions. B2B-only companies are therefore out of scope.

2. What if I have a mixed audience?

You’ll need to assess each digital asset. Consumer-facing elements must comply, even if the product is B2B.

3. Are free tools or demos considered consumer-facing?

Yes – if individuals can access them without acting on behalf of a business, they fall under the EAA.

4. Is compliance mandatory for my blog?

If your blog is publicly accessible and aimed at individual users (even educational), it’s likely in scope.

5. Do accessibility overlays make me compliant?

Not on their own. Overlays improve usability, but full compliance requires fixing underlying code-level issues.

6. Are accessibility statements required for B2B companies?

Only for the consumer-facing elements. But publishing one is recommended for transparency.

7. What if I only sell to enterprises but have a public website?

The public website still needs to meet accessibility requirements, regardless of who your customers are.

8. What happens if I don’t comply?

Each EU Member State defines its own enforcement measures. This can include corrective actions, sanctions, or other consequences – depending on how the EAA has been implemented at the national level.

The post European Accessibility Act B2B guide: Are B2B companies affected? Here’s what the law says appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

But while some businesses are starting to take note of the EAA, many aren’t aware of the consequences of non-compliance, which can be severe. 

In this blog post, we’ll demystify the European Accessibility Act fines, so you have a thorough understanding of the stakes – and what steps you can take to help steer clear of the penalties.  

What happens if you don’t comply with the European Accessibility Act?

The European Accessibility Act (EAA) is a directive, not a regulation – this distinction is important. Both are binding legislative acts under EU law, but they function differently:

• A regulation (like GDPR) has a direct effect. It automatically becomes law in all EU Member States without needing to be implemented through national legislation.
• A directive, like the EAA, must be transposed into national law by each Member State. This means countries have some flexibility in how they implement it – particularly in areas like enforcement and penalties.

Who enforces the EAA?

Each Member State is required to designate one or more authorities responsible for monitoring and enforcing the EAA. These could be existing consumer protection agencies, or entirely new regulatory bodies.

Enforcement mechanisms might include audits and inspections, ongoing monitoring of digital platforms, responding to user complaints, and collaboration with EU-wide networks to share best practices. Some authorities may also carry out proactive checks, especially in high-risk sectors like finance and e-commerce.

How Member States determine fines and penalties

One of the EAA’s key features is that it sets the framework but leaves the application to individual Member States. This means that each country must create its own laws, including specific enforcement procedures and fine structures.

Although European Accessibility Act fines and penalty systems will vary, most Member States are expected to assess factors like the severity and duration of the violation, how cooperative the business is with regulators, how many users were affected, and whether there’s a history of previous violations.

Below are some examples of European Accessibility Act fines and penalties. Please note that these are subject to change as each country finalizes its implementation:

Austria

• Fines: Up to €200,000
• Additional Penalties: Repeated violations can lead to higher fines and possible suspension of services.​

Belgium

• Fines: €1,000 to €50,000
• Additional Penalties: Continuous non-compliance may lead to suspension of business operations.

Denmark

• Fines: €10,000 for initial non-compliance
• Additional Penalties: Fines increase with repeated offenses.

France

• Fines: €5,000 to €250,000
• Additional Penalties: €25,000 for any additional, related offenses as well as potential public exposure of non-compliant businesses.​

Germany

• Fines: Up to €500,000
• Additional Penalties: Businesses may need to take corrective action and face potential suspension of services.

Ireland

• Fines: €5,000 to €60,000
• Additional Penalties: Potential imprisonment for directors, managers, administration staff and other officers for up to 6 months or 18 months once indicted.

Italy

• Fines: €40,000 or 5% of annual turnover
• Additional Penalties: Potential suspension of services. 

Netherlands

• Fines: Up to €250,000
• Additional Penalties: Potential suspension of services.

Spain

• Fines: €30,000 to €600,000
• Additional Penalties: Potential suspension of services.

Sweden

• Fines: Up to €200,000.​
• Additional Penalties: Businesses will have to take corrective action and face mandatory accessibility audits to ensure compliance. 

Examples of accessibility violations and anticipated enforcement approaches

To help you better understand what might trigger enforcement action, here are a few hypothetical but plausible scenarios:

• An e-commerce website fails to provide alt text for product images, making it unusable for visually impaired users.
• A banking app is not navigable by keyboard alone, violating accessibility principles for users with motor disabilities.
• A customer support chatbot doesn’t offer an accessible fallback option like a human agent, creating a barrier for those who use assistive technologies.
• A transport-booking website provides a CAPTCHA with no accessible alternative, making it difficult for screen reader users to complete a purchase.
• A mobile app used for public services doesn’t have strong contrast and doesn’t support text resizing, excluding users with low vision.
• A video tutorial platform doesn’t provide captions or transcripts, effectively shutting out users who are hearing impaired.
• A travel company’s booking platform uses complicated, multi-step forms with no progress indicators or error messages compatible with screen readers.

In these cases, authorities could issue warnings, fines, require remedial action, or all three. The severity of the enforcement could be linked to how essential the service is and how much harm the inaccessibility causes.

Legal and financial consequences of non-compliance

Beyond the potential European Accessibility Act fines, there are broader risks to consider. 

If you’re sued for non-compliance, legal fees can mount up quickly. You might also lose contracts, particularly with government or enterprise clients that require accessibility compliance. 

What’s more, inaccessible platforms can drive customers away. Over 100 million people in the EU alone live with disability, which means your business could be missing out on a large customer base by not being accessible. 

There’s also the risk of class-action lawsuits or coordinated complaints from consumer rights organizations. Non-compliance can lead to operational setbacks, delays in product launches, and resource-draining remediation efforts that could have been avoided through early planning.

There’s no denying that the consequences of non-compliance can be severe – not just financially, but legally and reputationally as well. This means it’s all the more important to prioritize accessibility efforts now so you can avoid any unfortunate consequences once the EAA fully comes into force. 

How to avoid European Accessibility Act fines and get closer to compliance

To ensure greater compliance with the EAA, it helps to be familiar with the accessibility principles outlined by the Web Content Accessibility Guidelines (WCAG). These guidelines set the WCAG 2.1 Level AA standard.

The WCAG is based on four principles, commonly referred to as the POUR principles:

• Perceivable: Users must be able to perceive the content presented. This includes using text alternatives for non-text content, ensuring sufficient contrast, and providing captions for audio and video.
• Operable: Interfaces and navigation must be operable by all users, including those who rely on keyboards or assistive devices. Avoid content that flashes excessively, and ensure all interactive elements are usable without a mouse.
• Understandable: Content must be presented in a clear and predictable way. This includes using legible fonts, straightforward language, and consistent navigation across pages.
• Robust: Content must be compatible with a variety of current and future user agents, including assistive technologies. This means using clean, semantic HTML and following web standards for long-term compatibility.

If your business’s digital services align with these principles, you’ll increase your chances of improving your website’s accessibility and usability – and reduce the risk of receiving European Accessibility Act fines.  

Steps to help make your website and services more accessible 

Whether you’re a startup or a multinational, these practical steps can help you get closer to aligning with the EAA:

• Start with an accessibility audit. This can help you find the areas where you’re not compliant. To carry out an audit, you can use tools to carry out automated scans, as well as manual user testing. This combined approach will help you uncover both obvious and more nuanced accessibility issues – such as code-level problems that affect screen readers or usability issues that automated tools can’t detect.
• Fix high-impact issues first. In general, it’s important to focus on issues that directly affect user access to your services. For example, missing alt text, poor contrast, and inaccessible navigation – these can often be fixed quickly. Develop a roadmap for more complex fixes and make sure accessibility improvements are included in your product backlog.
• Offer multiple communication channels for users. Ensure that users can access customer support in accessible formats.
• Use semantic HTML. This helps screen readers interpret content correctly.
• Implement ARIA landmarks and roles. These can significantly improve navigation for assistive technology users.
• Ensure all forms have proper labels and instructions. This allows users with assistive tech to complete them without barriers.
• Provide text alternatives for multimedia content. This can include captions for videos, transcripts for podcasts, and audio descriptions where appropriate.
• Check color contrast and font across all pages. Make sure all text is legible in different conditions.
• Ensure your navigation is consistent and intuitive. Menus should be logically ordered and links clearly described.
• Promote keyboard accessibility. Users should be able to navigate your entire website using only their keyboard.
• Set up a regular review process. Accessibility isn’t one-and-done – it’s a continuous commitment. Build in quarterly or biannual reviews to assess progress, tackle regressions, and stay ahead of legal updates.
• Document everything. This includes audit results, internal discussions, timelines for fixes, and user feedback. Keeping detailed records helps your team stay accountable and serves as valuable proof of your efforts if authorities investigate.
• Educate your team. Make sure everyone on your team – from designers and developers to product managers and marketers – understands accessibility principles. Host regular training sessions and make accessibility a shared responsibility across departments.

Embedding accessibility into your strategy and daily workflows by using the right tools means you can reduce the risk of violations and provide a more inclusive experience for everyone.

Don’t underestimate the risks of non-compliance

The European Accessibility Act is an opportunity to make your digital experiences more inclusive, resilient, and user-friendly. 

But make no mistake: the risks of non-compliance are real. With enforcement deadlines approaching and national implementations underway, businesses must act now to prepare.

The good news is that you don’t have to go it alone. When used in combination with manual user testing and some of the other steps outlined in this blog, our Accessibility Widget makes it easier to improve your website’s accessibility and usability in terms of EAA standards. 

The post European Accessibility Act fines: What you need to know appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Recording of the webinar and useful resources

If you couldn’t attend our webinar “New accessibility requirements: How to improve your website’s accessibility with iubenda & AccessiWay” here is the recording and some useful resources to learn more about accessibility.

The post New accessibility requirements: How to improve your website’s accessibility with iubenda & AccessiWay appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

Legal documents tailored for you

Multi-language legal documents and compliance for international websites

Did you know that if you target users in multiple countries, your legal documents must be translated into their language? Not only to comply with legal requirements, but also to build trust with each visitor. With iubenda, you can do this easily, without worrying about translation errors or manual updates.

Upgrade your plan to Advanced or Ultimate

Why choose iubenda

Translate your legal documents into multiple languages

With iubenda you can automatically translate your privacy policy, Terms and Conditions and cookie banner into multiple languages with one click. All your legal documents will always be up to date, without having to rewrite them every time you add a new language. And these are not approximate translations: we rely on legal experts and specialised translators to help you comply with regulations.

Adapt your cookie banner with geolocation

With geolocation, iubenda automatically detects the location of your users and adapts your cookie banner according to local regulations. This means it will ask for explicit consent from European users, while giving US users the option to opt-outt. So you don’t have to worry about complicated manual implementations and can maximize your consent rate.

Simplify your online privacy hurdles

Regulations and guidelines are a winding maze. Start your compliance journey with a trusted suite of features that do the hard work for you.

Cookie and Consent Banner Privacy and Cookie Policy Terms and Conditions

NEW

Website Accessibility Advanced Solutions

Back

Privacy Controls and Cookie Solution

Easily add a cookie and consent banner to your site or app to automatically block cookies and manage user preferences with Google Consent Mode built in.

Take a look

Back

Privacy and Cookie Policy Generator

Our scanner detects the services on your site to generate a fully customizable, self-updating privacy and cookie policy with lawyer-drafted text available in 15+ languages.

Take a look

Back

Terms and Conditions Generator

Follow a guided setup to create T&Cs tailored to your e-commerce, blog, app, and more with lawyer-drafted text available in 15+ languages.

Take a look

Back

Accessibility Solution

Add an AI-powered accessibility widget to your site to automatically optimize for users with disabilities and help meet EAA requirements with just one line of code.

Take a look

Back

Streamline compliance and marketing processes

Manage and store consents across multiple platforms, handle data subject requests and whistleblowing reports, optimize newsletter opt-ins, and more.

Consent Database

Store and sync consent records across multiple platforms.

Take a look

Newsletter Opt-in Booster

Boost newsletter signups with a customizable widget.

Take a look

Whistleblowing Management Tool

Establish an internal reporting channel for whistleblower reports.

Take a look

Data Subject Rights Management Tool

Handle data subject requests through a centralized, intuitive platform.

Take a look

Register of Data Processing Activities

Document data processing activities within your organization.

Take a look

Trusted by over 150,000 clients in 100+countries

“If you, like me, are part of a smart team and hate updating your privacy policy every time you add some code to your site, then iubenda is for you. It's ridiculously affordable, and super easy to use.”

Upgrade your plan to Advanced or Ultimate

The post Compliance for international websites – upgrade appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

More and more services are shifting online, and as a result, businesses are expected to make their digital spaces inclusive for everyone, including people with disabilities. 

However, while many teams understand the need for accessibility, implementing it can feel overwhelming. 

What does a truly accessible website look like in practice?

Which features matter most? 

And how can your team replicate them effectively?

Don’t worry – we’re giving you the answers through concrete, real-world examples of accessibility done well. We’ll highlight websites that demonstrate key accessibility principles, from keyboard navigation and screen reader compatibility to proper alt text, captions, and readable typography. 

Whether you’re a designer, developer, marketer, or product lead, this guide will help you understand what great accessibility looks like – and how to bring it to your own site.

What is website accessibility?

Website accessibility is the practice of designing and developing digital content so it can be used and understood by everyone, including people with permanent, temporary, or situational disabilities. 

This includes users who rely on screen readers, navigate with keyboard-only input, or need adjustable text sizes, color contrast, or transcripts for audio content.

Accessible websites make sure that no user is excluded, and support users in low-bandwidth environments, older adults, and those using non-standard devices.

The primary framework used to define and evaluate accessibility is the Web Content Accessibility Guidelines (WCAG). These internationally recognized standards are built around four key principles: content must be Perceivable, Operable, Understandable, and Robust (POUR).

Accessible websites aren’t just more inclusive – they’re also easier to navigate, more SEO-friendly, and often more usable for everyone. That’s why accessibility is now considered a cornerstone of good digital experience design.

Why website accessibility matters

Accessibility matters because the web is a critical part of everyday life – and it should be usable by everyone. 

Excluding users with disabilities from digital services can create real-world barriers to banking, healthcare, education, and employment.

For many people with disabilities, the internet offers independence and access, but only if digital experiences are built to be inclusive. Whether it’s a lack of alt text, unreadable font sizes, or navigation that doesn’t work with a keyboard, even oversights that seem minor can have a significant impact.

Beyond the human case, accessibility also brings clear business benefits. Inclusive websites offer a better user experience, reduce bounce rates, and improve SEO performance. Accessible code and content often align with search engine best practices, making your site easier to find and navigate.

And then there’s compliance: regulatory frameworks like the Americans with Disabilities Act (ADA) and the European Accessibility Act (EAA) impose legal obligations – and potential penalties – for inaccessible digital platforms. It’s important to remember that accessibility isn’t a niche concern. It’s a legal, ethical, and strategic priority for any business building digital products today.

The key principles of an accessible website

Truly accessible websites follow well-established principles that support users with a wide range of needs. Let’s take a look at some of the most critical accessibility features, with practical notes on implementation (of course).

1. Keyboard navigation support

Not all users rely on a mouse – some navigate using a keyboard, switch device, or assistive tech. Ensure that all interactive elements (buttons, forms, links) can be accessed via the Tab key and that focus indicators are clearly visible.

2. Alternative text for images

Alt text provides screen reader users with image descriptions. It’s essential for conveying information visually and supporting users with vision loss.

3. Captions and transcripts for multimedia

Videos should have closed captions for users who are deaf or hard of hearing, and transcripts should be available for audio content.

4. Color contrast and readable text

Make sure foreground and background colors have sufficient contrast – aim for a minimum contrast ratio of 4.5:1 for body text.

5. Resizable text and adjustable fonts

Text should scale without breaking the layout. Make sure you’re supporting user-adjustable fonts or offer toggle settings to improve readability.

6. Screen reader compatibility

Use semantic HTML, proper ARIA labels, and structured heading hierarchies so screen readers can interpret the content logically.

7. Accessible forms and error messages

Label fields properly, provide clear instructions, and surface error messages that are both visible and announced via assistive tech.

8. Descriptive links and semantic navigation

Avoid vague labels like “click here.” Use meaningful, descriptive link text that explains the action or destination.

Real-world examples of accessible websites

Understanding accessibility in theory is one thing, but seeing it in action is another. Here are five standout examples of accessible websites, each demonstrating best practices you can adapt to your own projects.

1. GOV.UK

The UK government’s digital services site is a global benchmark for clarity, simplicity, and accessibility.

Here are the highlights:

• Fully keyboard navigable with visible focus states
• Clear, hierarchical heading structure
• Descriptive link text and logical page flow
• No reliance on color to convey meaning

2. Apple.com

Everyone loves the Apple brand – but the Apple site demonstrates how sleek design and accessibility can coexist.

Highlights:

• Semantic HTML with screen reader-friendly ARIA labels
• High color contrast and readable type across all devices
• Accessible product tours with keyboard navigation

3. BBC.co.uk

Whatever your thoughts are on the BBC, it’s long been committed to digital inclusion, especially in multimedia content.

Highlights:

• Closed captions and audio descriptions for video content
• High-contrast text with adjustable font sizes
• Responsive design for screen magnification

4. The New York Times

The NY Times combines rich media with thoughtful accessibility – in short, it’s hit the nail on the head.

Highlights:

• Text versions of multimedia features
• Structured headlines and skip links for faster screen reader navigation
• Subtle animations that don’t interfere with usability

5. Target.com

Target became a poster child for accessibility after settling a landmark ADA lawsuit – and responded with real change.

Highlights:

• Improved alt text across product imagery
• Logical tab ordering and clearly labeled forms
• Support for screen readers and keyboard navigation

How to test and improve your own website accessibility

Knowing what to fix is the first step, but it can feel like the biggest block. 

Here’s how to identify accessibility gaps on your website and start addressing them – without needing to be an expert.

1. Run an automated accessibility scan

You can start with tools like:

• WAVE (Web Accessibility Evaluation Tool)
• axe DevTools (browser extension)
• Google Lighthouse (built into Chrome DevTools)

These tools highlight common issues like missing alt text, poor contrast, or form labeling errors.

2. Perform basic manual testing

Automated scans catch a lot, but not everything. Supplement with simple manual checks:

• Keyboard-only navigation: Can you tab through all elements? Are focus indicators visible?
• Screen reader testing: Use free tools like NVDA (Windows) or VoiceOver (Mac) to test reading order, heading structure, and ARIA labels.
• Zoom in and adjust text size: Does the layout stay usable when text is enlarged?
  

3. Prioritize critical fixes

Focus on user-impacting areas first: navigation, forms, interactive elements, and key content pages. Remember, you should aim to resolve blockers before refining enhancements.

4. Make accessibility part of your workflow

Build accessibility checks into your design, content, and dev processes. Create reusable components, document standards, and test early and often.

Legal requirements and WCAG compliance

Accessibility isn’t just a best practice; it’s a legal requirement in many parts of the world. Regulatory frameworks are evolving quickly, and failure to comply can result in lawsuits, fines, or reputational damage.

In the United States: ADA

Under the Americans with Disabilities Act (ADA), websites are increasingly considered “places of public accommodation.” This means businesses – especially in retail, hospitality, and services – must make sure that their websites are accessible. Numerous high-profile lawsuits (e.g., against Domino’s, Target) have set strong legal precedents.

In the European Union: EAA

The European Accessibility Act (EAA) requires many B2C companies to make their digital products and services accessible. This includes e-commerce sites, mobile apps, banking platforms, and more.

WCAG: The global standard

Most laws reference the Web Content Accessibility Guidelines (WCAG) – specifically Level AA – as the benchmark for compliance. These guidelines provide a clear roadmap for improving accessibility across content, navigation, media, and interaction.

NOTE: Making your site WCAG-compliant minimizes legal risk and strengthens your commitment to inclusive, user-centered design.

Conclusion: Bring accessibility from intention to implementation

Website accessibility isn’t only a checklist; it’s a commitment to creating digital spaces that work for everyone. As the examples above show, inclusive design can be elegant, user-friendly, and scalable, no matter your industry or audience.

By following accessibility principles, learning from real-world models, and using the right testing tools, your team can go beyond compliance and deliver better experiences for all. 

You might want to improve an existing site or build something new – whatever you’re starting from, accessibility is a wise investment in usability, trust, and long-term success.

The post Examples of accessibility done right: real websites you can learn from appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

However, many businesses still struggle with selecting the right tools, using them effectively, or even using them at all. 

This creates a gap that can increase risks, lead to missed opportunities, and even open you up to legal exposure. 

In this guide, we’ll take a look at everything you need to know. From what web accessibility tools are, to how they support compliance with standards like WCAG, ADA, and the EAA. 

We’ll also offer practical tips and advice on implementing these tools efficiently into your workflows. 

What are web accessibility tools?

Let’s get started with the basics.

Web accessibility tools are technologies and software that help to evaluate, optimize, and monitor websites to make them more usable. This is especially true for people with disabilities or impairments. 

These tools help assist developers, designers, and compliance officers in spotting and fixing issues such as poor keyboard navigation, missing alternative text, or low color contrast. 

They contribute to aligning websites with standards like WCAG 2.1 and help businesses meet obligations under laws like the Americans with Disabilities Act (ADA) and the European Accessibility Act (EAA). 

Key features to look for in accessibility tools

Choosing the right accessibility tool is all about making sure your website is truly usable for all users.

Because an accessible site is good for everyone, not just those with disabilities. 

A good tool will not only help you detect issues but also fit naturally into your development workflow, support different types of accessibility testing, and guide you toward making meaningful improvements to your site. 

When evaluating your options, it’s a good idea to prioritize tools that offer:

• Automated and manual testing capabilities: Automated scans can help you catch common issues quickly, while manual testing captures more complex usability barriers. 
• Screen reader simulation options: Helps you experience your website the way visually impaired users would. 
• Keyboard navigation support checking: Allows users who rely on a keyboard alone to move through your site easily. 
• Color contrast analysis: Verifies that text and visual elements meet the minimum contrast ratios for readability. 
• Actionable, easy-to-understand reports: Reports that provide clear guidance on whatever issues are found and how to fix them, which reduces any guesswork. 
• Compliance checking: Helps to align your site with the major accessibility standards and legal frameworks such as WCAG 2.1, ADA, and EAA. 
• Integration with development workflows: Allows accessibility testing to be a part of your build and deployment processes automatically. 

Best web accessibility tools for testing and compliance

There’s no one-size-fits-all tool that will work for everyone. 

Different types of accessibility tools serve different needs; more often than not, a combination of tools works best. 

Automated web accessibility testing tools

Automated testing tools are great for catching many common accessibility issues quickly, consistently, and easily. 

• axe DevTools: A popular browser extension that finds accessibility issues right inside your development environment. 
• WAVE Evaluation Tool: A free, easy-to-use browser extension that highlights accessibility errors visually on your webpage. 
• Accessibility Insights: A Microsoft tool that offers both fast automated checks and guided manual assessments. 

Manual web accessibility evaluation tools

Manual testing complements automation by identifying more complex or subjective issues, like confusing navigation or poor focus order. 

• Screen reader testing: Use tools like NVDA or VoiceOver to experience your site from a non-visual perspective and manually spot gaps.
• Manual review of semantic structure: Check headings, landmarks, ARIA roles, and logical tab order directly in the HTML or using browser dev tools.
• Manual keyboard testing: Navigate your site using only the Tab, Enter, and Arrow keys to check keyboard accessibility. 

Color contrast checkers

Color contrast tools help make sure your text and visual elements are readable by users with low vision or color blindness.

• WebAIM Color Contrast Checker: Quickly test if your color combinations meet WCAG’s recommended contrast ratios. 
• Contrast Grid by EightShapes: Compare multiple text and background color combinations in one view to find the most accessible options. 

Screen readers and simulators

Testing with real screen readers helps you to validate how accessible your site’s structure and content really are. 

• JAWS: One of the most widely used screen readers globally, often considered to be the industry standard. 
• NVDA: A free and powerful screen reader for Windows that lets you experience your website as a visually impaired user would. 
• VoiceOver: Apple’s built-in screen reader, perfect for testing how your site performs on MacOS and iOS devices. 

Keyboard navigation testing tools

Since many users depend on keyboards instead of mice, good keyboard navigation is important. 

• axe DevTools’ keyboard focus tests: Identify missing focus indicators or keyboard traps that can disrupt navigation.
• Manual testing with tab/shift-tab navigation: Manually simulate a complete user journey using only keyboard controls.

How to use web accessibility tools effectively

Accessibility should always be baked into your processes, not treated as an afterthought. 

Tools are at their most powerful when they’re used proactively during the development stage. Here are a few ways you can maximize their impact and make your site as accessible as possible: 

• Integrate automated checks into CI/CD pipelines: Catch issues early by running accessibility tests automatically during the build and deployment stages.
• Schedule regular manual audits: Manually test critical workflows and pages at key stages of development. 
• Prioritize fixes based on impact: Focus first on issues that affect usability the most, like keyboard traps or unreadable text. 
• Train your team on accessibility-first principles: Make sure your designers and developers know how to avoid introducing accessibility barriers right from the start. 

Web accessibility tools FAQs

The post Which web accessibility tools do you really need? A practical guide appeared first on Compliance Solutions for Websites, Apps and Organizations | iubenda.

From unreadable text to uncaptioned videos, many websites and digital products unintentionally exclude users with disabilities. 

Although not intended, these issues have serious repercussions. They can frustrate, alienate, or completely block access for people who rely on assistive technologies, or have specific cognitive, visual, auditory, or motor needs.

The problem is, for teams without dedicated accessibility specialists, identifying and resolving these issues can feel overwhelming. The guidelines are extensive, the tools varied, and the consequences – ranging from user drop-off to legal risk – can be serious.

That’s why it’s critical to understand not only what accessibility issues are, but also how to find and fix them. 

Whether you’re a web developer, UX designer, content strategist, or product manager, this guide will walk you through the most common accessibility problems and provide actionable strategies to solve them.

Addressing these barriers is more than just compliance: it’s a commitment to digital equity and better user experiences for everyone.

But, what are accessibility issues?

Accessibility issues refer to digital design and development problems that make websites, applications, or content difficult – or even impossible – for people living with disabilities to use. These barriers affect how users perceive, navigate, and interact with digital products, often excluding individuals who rely on assistive tools or alternative input methods.

Let’s take a look at some examples: 

A user with vision loss may not be able to understand content without alternative text on images. A person with motor disabilities may be unable to complete a form that isn’t keyboard-navigable. And someone with hearing loss may miss essential information in a video that lacks captions or transcripts.

Accessibility issues are typically defined and assessed according to the Web Content Accessibility Guidelines (WCAG), a global standard that outlines success criteria across four key principles: perceivable, operable, understandable, and robust (POUR). These principles help make sure that digital content works for the widest possible range of users.

Importantly, accessibility isn’t just about screen readers or visual impairments – it covers a wide spectrum of physical, sensory, and cognitive needs. That includes neurodivergent users, aging populations, and users in temporary situations (like navigating with one hand or reading in bright sunlight).

Why fixing accessibility issues matters

Accessibility issues don’t just affect code: they affect people. 

Every barrier in your digital product can result in a user being unable to access vital information or complete a task. For the more than 1 billion people worldwide who live with some form of disability, these issues represent a significant obstacle to independence and inclusion, and, ultimately, opportunity.

But accessibility issues impact businesses, too. Exclusionary design leads to lost customers, reputational damage, and increased legal risk. In the U.S., lawsuits under the ADA continue to rise. In the EU, the European Accessibility Act is set to make digital accessibility a legal requirement for many B2C businesses in 2025.

The good news is, many accessibility best practices – like semantic HTML, descriptive alt text, and structured content – are also SEO best practices. So, fixing accessibility issues can actually improve your site’s search visibility and organic reach.

Think of it this way: accessibility isn’t just a legal or ethical checkbox. It’s a pathway to a better user experience, wider audience engagement, and long-term digital success.

Common accessibility issues in websites and digital content

Accessibility issues can appear in many forms – some are visual, others structural or interactive. Understanding the most common ones is key to building inclusive digital experiences. 

Let’s explore the top barriers users face and how they can be addressed.

Issue	Details	Solution
Lack of alt text	Alt text is fundamental for users who rely on screen readers to interpret visual content. Without it, blind or low-vision users may miss important information, especially if the image is getting across a call to action or critical context.	Always add concise, descriptive alt text to informative images. Just remember, failing to comply can lead to expensive lawsuits.
Poor color contrast	Low contrast between text and background makes it hard to read, especially for users with color vision deficiencies or older adults.	Use tools like the WAVE Accessibility Tool or axe DevTools to test color contrast ratios. Aim for a minimum ratio of 4.5:1 for normal text.
Inaccessible forms and input fields	Forms are a common point of failure for accessibility. Issues include missing or improperly associated labels, unclear error messages, and broken tabbing behavior.	Always use label tags correctly, make sure there’s a logical tab order, and provide clear, text-based error messages that are programmatically linked to input fields.
Missing or incorrect header structure	Screen readers rely on heading hierarchies (like <h1> to <h6>) to navigate pages. If headings are skipped or misused (e.g., using <div>s styled like headers), users lose context.	Use headings to reflect the logical structure of content. Only one <h1> per page, followed by nested subheadings in order (e.g., <h2>, <h3>).
Keyboard navigation issues	Many users can’t use a mouse and rely on keyboard navigation (e.g., the Tab key) to move through content. Common issues include missing focus indicators or getting “stuck” in navigation traps.	Make sure all interactive elements (links, buttons, inputs) are accessible via keyboard and that visible focus styles are preserved.
Videos with transcripts or captions	Deaf or hard-of-hearing users can’t access video content without captions. Without transcripts, users also lose the ability to scan or reference audio-based content.	Provide accurate closed captions for all spoken content and transcripts for audio or multimedia assets.
Inconsistent or confusing navigation	Navigation that’s inconsistent across pages – or overloaded with poorly grouped content – can disorient users, especially those with cognitive or learning disabilities.	Use consistent layouts, clear menu structures, and predictable interactive behaviors across all screens and breakpoints.
Auto-playing media without controls	Media that auto-plays with sound can disrupt screen reader users and trigger sensory overload, especially for neurodivergent individuals or users with ADHD.	Avoid auto-play where possible. But if used, make sure users have accessible options to pause, stop, or mute the media immediately.