Are you covered by the EAA?

You should care if the following apply…

<aside> 📌 This is you

• [ ] You have a business that operates in the EU or targets an EU audience and has an online presence
• [ ] You have an annual revenue of over €2 million or more than 10 employees
• [ ] You have any of the following products or services**:**
  • [ ] Computers and operating systems;
  • [ ] ATMs, ticketing and check-in machines;
  • [ ] Smartphones;
  • [ ] TV equipment related to digital television services;
  • [ ] Telephony services and related equipment;
  • [ ] Access to audio-visual media services such as television broadcast and related consumer equipment;
  • [ ] Services related to air, bus, rail and waterborne passenger transport;
  • [ ] Banking services;
  • [ ] E-books;
  • [ ] E-commerce </aside>

If you have ticked all of main boxes, the EAA will apply to you and you need to be compliant by June 28th, 2025.

<aside> ❓ Frequently Asked Questions (FAQ)

• What is the EAA 2025?
• How does it relate to User Experience? </aside>

<aside> 💡 Strategic To Dos

• [ ] List all products and services that fall under the EAA.
• [ ] Do an accessibility review of these products and services.
• [ ] Use automated testing (should catch about a third of all issues).
• [ ] Manual testing: see technical list.
• [ ] Make a plan for fixing all the issues one by one.
• [ ] Prioritize and set an order in which to fix the issues.
• [ ] Set deadlines for all steps.
• [ ] Assign responsibilities for different tasks.
• [ ] Write an accessibility statement listing all non-accessible content and post it on your website/app until it's fixed.
• [ ] Retest your products/services after fixing the issues.
• [ ] Introduce automated testing (use tools such as: *Google Lighthouse, Pa11y, HTML_CodeSniffer, WAVE, Accessibility Insights, ColorBlindly, axe*).
• [ ] Manual testing: verify keyboard navigation, screen readers, color contrast, and get input from actual users with disabilities.
• [ ] Revise your accessibility statement.

</aside>

<aside> ⚙️ Technical To Dos

• [ ] Provide Effective Alt Text for Non-Text Content

  This ensures that non-decorative images, media, applets, and other non-text content are accessible to users of assistive technologies, such as screen readers.

• [ ] Make All Content Keyboard Accessible

  Consider that some users may not be able to use a mouse.

• [ ] Create Accessible Forms

  Ensure your forms are effective, user-friendly, and logical. Clearly label fields, provide necessary information and instructions, and identify any form entry errors, such as empty required fields.

• [ ] Use Moving, Flashing, or Blinking Content Cautiously

  Content that blinks more than three times per second may trigger seizures in visitors with epilepsy.

• [ ] Implement WAI-ARIA for Dynamic Elements

  Ensure that any content changes occurring without a page reload are clearly communicated to users of assistive technology.

• [ ] Ensure Page Titles Are Descriptive

  Page titles should accurately reflect the content.

• [ ] Provide Unique and Descriptive Link Text

  Ensure all links have descriptive names and anchor text that clearly identify their destinations.

• [ ] Properly Mark Up Headings

  Assist visitors, especially those using assistive technology who may override or disable CSS, in understanding the relationships between different sections of the page.

• [ ] Avoid Imposing Time Limits

  Consider that some individuals may need more time to complete tasks.

• [ ] Choose Colors with Sufficient Contrast

  Ensure your content is easily perceivable by all visitors. Use tools like this Color Contrast Checker to select effective color combinations.

</aside>

Stop by and say “Hi!”

This checklist was created by Amina Belabbes, UX / UI designer. Find me on LinkedIn.