A checklist for the European Accessibility Act: EAA topics and every WCAG A and AA criterion, with code examples for web and mobile.
70 criteria listed
No criteria found.
Requires that images, icons, charts and other non-text content have a text alternative that serves the equivalent purpose for users who cannot see or hear it.
Review criterion: Non-text ContentRequires prerecorded audio-only content (such as a podcast) to have a text transcript, and prerecorded video-only content (such as a silent demo) to have a text description or an audio track that conveys the same information.
Review criterion: Audio-only and Video-only (Prerecorded)Requires captions for the audio of prerecorded video with sound, so that deaf and hard of hearing users get the speech and meaningful sounds as synchronized text.
Review criterion: Captions (Prerecorded)Requires prerecorded video with sound to offer either audio description or a full text alternative, so blind and low-vision users get the important visual information.
Review criterion: Audio Description or Media Alternative (Prerecorded)Requires captions for all live audio in synchronized media, such as webinars and streamed events, so deaf and hard of hearing users can follow in real time.
Review criterion: Captions (Live)Requires audio description for all prerecorded video in synchronized media, narrating the important visual details that the main soundtrack does not cover.
Review criterion: Audio Description (Prerecorded)Requires that structure and relationships shown visually, such as headings, lists, tables, form labels and groups, are also available to assistive technology through code or text.
Review criterion: Info and RelationshipsRequires that when the order of content affects its meaning, the reading order in the code matches the meaningful order, so screen readers read it correctly.
Review criterion: Meaningful SequenceRequires that instructions do not rely only on shape, color, size, location, orientation or sound, so users who cannot perceive those can still follow them.
Review criterion: Sensory CharacteristicsRequires that content works in both portrait and landscape and is not locked to one display orientation, unless a specific orientation is essential.
Review criterion: OrientationRequires fields that collect information about the user, such as name, email or address, to state their purpose in code so browsers and tools can autofill them.
Review criterion: Identify Input PurposeRequires that color is not the only way to convey information, show an action or tell elements apart, so people who cannot see color still get the meaning.
Review criterion: Use of ColorRequires a way to pause, stop or control the volume of any audio that plays automatically for more than three seconds, independent of the system volume.
Review criterion: Audio ControlRequires text to have a contrast ratio of at least 4.5:1 against its background, or 3:1 for large text, so people with low vision or color deficiencies can read it.
Review criterion: Contrast (Minimum)Requires that text can be resized up to 200% without assistive technology and without loss of content or function.
Review criterion: Resize TextRequires real text instead of images of text to present information, except where the text can be customized or the image is essential, such as a logotype.
Review criterion: Images of TextRequires content to adapt to a 320 CSS pixel width (400% zoom) without losing information or needing two-dimensional scrolling.
Review criterion: ReflowRequires at least 3:1 contrast for user interface components, their states and the graphics needed to understand the content.
Review criterion: Non-text ContrastRequires that no content or function is lost when users increase line, paragraph, letter and word spacing.
Review criterion: Text SpacingRequires that tooltips and popups shown on hover or focus can be dismissed, hovered over and stay visible until the user is done.
Review criterion: Content on Hover or FocusRequires that every function can be operated from a keyboard, without needing specific timings for individual keystrokes.
Review criterion: KeyboardRequires that when focus can move into a component with the keyboard, it can also move out again with the keyboard.
Review criterion: No Keyboard TrapRequires that single-character shortcuts can be turned off, remapped to include a modifier, or are active only on focus.
Review criterion: Character Key ShortcutsRequires that users can turn off, adjust or extend any time limit set by the content, with a warning before time runs out.
Review criterion: Timing AdjustableRequires a way to pause, stop or hide moving, blinking, scrolling or auto-updating content that lasts more than five seconds.
Review criterion: Pause, Stop, HideRequires that nothing on a page flashes more than three times in any one-second period, or stays below the general and red flash thresholds, to protect people with photosensitive epilepsy.
Review criterion: Three Flashes or Below ThresholdRequires a mechanism, such as a skip link or landmarks, to bypass blocks of content that repeat on multiple pages.
Review criterion: Bypass BlocksRequires that every web page has a title that describes its topic or purpose.
Review criterion: Page TitledRequires that focusable elements receive focus in an order that preserves meaning and operability.
Review criterion: Focus OrderRequires that the purpose of each link can be determined from its text or from its programmatic context.
Review criterion: Link Purpose (In Context)Requires more than one way to find a page within a set of pages, such as navigation, search or a site map, except for pages in a process.
Review criterion: Multiple WaysRequires that headings and labels describe the topic or purpose of the content or control.
Review criterion: Headings and LabelsRequires that the keyboard focus indicator is visible whenever a keyboard-operable interface is used.
Review criterion: Focus VisibleRequires that a focused component is not entirely hidden by author-created content such as sticky headers, banners or widgets.
Review criterion: Focus Not Obscured (Minimum)Requires that functions using multipoint or path-based gestures, such as pinching or swiping, can also be operated with a single pointer.
Review criterion: Pointer GesturesRequires that pointer actions are not executed on the down-event, or can be aborted, undone or reversed, so mistakes can be cancelled.
Review criterion: Pointer CancellationRequires that the accessible name of a control contains its visible label text, so speech users can activate it by what they see.
Review criterion: Label in NameRequires that functions triggered by shaking, tilting or body motion can also be operated by controls, and that motion response can be disabled.
Review criterion: Motion ActuationRequires that anything done by dragging can also be done with a single click or tap, without dragging.
Review criterion: Dragging MovementsRequires pointer targets to be at least 24 by 24 CSS pixels, unless spacing, an equivalent, inline text, browser control or necessity applies.
Review criterion: Target Size (Minimum)Requires that the default human language of every page can be programmatically determined, for example with a lang attribute on the html element.
Review criterion: Language of PageRequires that passages and phrases in a different language than the page default are marked, so assistive technology pronounces them correctly.
Review criterion: Language of PartsRequires that when a component receives focus, it does not trigger a change of context such as opening a window or moving focus.
Review criterion: On FocusRequires that changing a control, such as a select list or check box, does not cause a change of context unless users were told in advance.
Review criterion: On InputRequires that navigation repeated across pages in a set appears in the same relative order each time, unless the user changes it.
Review criterion: Consistent NavigationRequires that components with the same function across a set of pages are identified consistently, with the same labels and text alternatives.
Review criterion: Consistent IdentificationRequires that help mechanisms repeated across pages, such as contact details, chat or an FAQ link, keep the same order relative to other content.
Review criterion: Consistent HelpRequires that automatically detected input errors identify the field in error and describe the error to the user in text.
Review criterion: Error IdentificationRequires labels or instructions wherever content asks for user input, including formats, required fields and grouped controls.
Review criterion: Labels or InstructionsRequires that when an input error is detected and a fix is known, the page tells the user how to correct it, except for security or purpose.
Review criterion: Error SuggestionRequires that legal, financial and data-changing submissions can be reversed, are checked for errors, or can be reviewed and confirmed first.
Review criterion: Error Prevention (Legal, Financial, Data)Requires that information already entered in a process is auto-populated or selectable, instead of being typed again, with limited exceptions.
Review criterion: Redundant EntryRequires that signing in does not depend on remembering, transcribing or solving a puzzle, unless an alternative or assisting mechanism exists.
Review criterion: Accessible Authentication (Minimum)Asked for complete tags, correct nesting, no duplicate attributes and unique IDs. Removed from WCAG 2.2, but still in EN 301 549 V3.2.1.
Review criterion: ParsingRequires every interface component to expose its name and role, and its states and values, so assistive technology can use it.
Review criterion: Name, Role, ValueRequires that status messages, such as results counts, confirmations and errors, are announced by assistive technology without moving focus.
Review criterion: Status MessagesWhich products and services the European Accessibility Act covers, which dates matter, and which exceptions can apply.
Review criterion: EAA scope: products and services coveredWho counts as a microenterprise, what the exemption covers for services, and what still applies to products.
Review criterion: Microenterprise exemption under the EAAThe five kinds of website and app content the EAA leaves out, and the content that is still in scope.
Review criterion: EAA content exclusions: what Article 2(4) leaves outWhen the EAA requirements apply only to the extent that compliance is not a fundamental alteration or a disproportionate burden.
Review criterion: Disproportionate burden and fundamental alterationWhat service providers must prepare, publish and keep under Article 13 and Annex V, and what a good accessibility page contains.
Review criterion: Service accessibility information under the EAAWhat the European Accessibility Act asks of online shops, from product pages and checkout to identification and payment.
Review criterion: EAA requirements for e-commerceWhat the EAA asks of banks and payment services: accessible identification, signing, security and payment, and plain language at level B2.
Review criterion: EAA requirements for consumer bankingThe six EAA requirements for e-books, plus e-readers, DRM, metadata and the EPUB technical route.
Review criterion: EAA requirements for e-books and e-readersWhich elements of air, bus, rail and waterborne transport the EAA covers, the urban exception, and the information requirements.
Review criterion: EAA requirements for passenger transportWhat the EAA asks of services that give access to audiovisual media: programme guides, subtitles, audio description and devices.
Review criterion: EAA requirements for audiovisual media accessReal-time text, total conversation, device requirements and the rules for answering emergency calls to 112 under the EAA.
Review criterion: EAA electronic communications and 112Annex I Sections I and II for consumer hardware, self-service terminals and e-readers, and the transition for existing terminals.
Review criterion: EAA hardware and self-service terminalsWhen a mobile app is covered by the EAA, how EN 301 549 treats native apps, and how to test on iOS and Android.
Review criterion: EAA and mobile apps: iOS and AndroidWhen PDFs and Office files fall under the EAA, what an accessible document needs, and how to make one.
Review criterion: EAA and documents: accessible PDFsCorpowid has been recognized by Gartner, a leading global research and advisory firm, for our innovation and performance in digital accessibility. These badges reflect our commitment to creating inclusive, AI-powered web experiences.
TR