EAA Compliance Checklist: EN 301 549 Web Requirements

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.

Provide alternatives for time-based media: transcripts for audio, audio description or text for video.

Captions are provided for all prerecorded audio content in synchronized media.

An alternative for time-based media or audio description is provided for prerecorded video content.

Audio description is provided for all prerecorded video content.

Information, structure, and relationships conveyed through presentation can be programmatically determined.

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

Instructions provided for understanding and operating content do not rely solely on sensory characteristics.

Content does not restrict its view and operation to a single display orientation.

The purpose of each input field collecting information about the user can be programmatically determined.

Color is not used as the only visual means of conveying information.

If audio plays automatically for more than 3 seconds, provide a mechanism to pause or stop it.

Text has a contrast ratio of at least 4.5:1 (3:1 for large text).

Text can be resized without assistive technology up to 200% without loss of content or functionality.

If the same visual presentation can be made using text, images of text are not used.

Content can be presented without loss of information or functionality at 320px width without two-dimensional scrolling.

Visual information required to identify UI components and graphical objects has at least 3:1 contrast.

No loss of content or functionality when users adjust text spacing properties.

Additional content triggered on hover/focus is dismissible, hoverable, and persistent.

All functionality is available from a keyboard.

Keyboard focus can be moved away from any component using only the keyboard.

Single-character keyboard shortcuts can be turned off or remapped.

Users can turn off, adjust, or extend time limits.

Moving, blinking, or scrolling content can be paused, stopped, or hidden.

Web pages do not contain anything that flashes more than three times per second.

A mechanism is available to bypass blocks of content repeated on multiple pages.

Web pages have titles that describe topic or purpose.

If navigation sequence affects meaning, focusable components receive focus in an order that preserves meaning.

The purpose of each link can be determined from the link text alone or with programmatically determined context.

More than one way is available to locate a web page within a set of web pages.

Headings and labels describe topic or purpose.

Any keyboard-operable user interface has a visible keyboard focus indicator.

When an element receives keyboard focus, it is not entirely hidden due to author-created content.

All functionality using multipoint or path-based gestures can be operated with single-pointer.

For functionality operated using a single pointer, at least one of the following is true: no down-event, abort or undo, up reversal, essential.

For UI components with visible text labels, the accessible name contains the visible text.

Functionality triggered by device motion can be operated by user interface components.

All functionality that uses a dragging movement can be achieved by a single pointer without dragging.

The size of the target for pointer inputs is at least 24 by 24 CSS pixels.

The default human language of each web page can be programmatically determined.

The human language of each passage or phrase can be programmatically determined.

When any component receives focus, it does not initiate a change of context.

Changing the setting of any UI component does not automatically cause a change of context unless the user has been advised.

Navigation mechanisms repeated on multiple pages occur in the same relative order.

Components with same functionality are identified consistently.

If help mechanisms are included on multiple pages, they occur in the same relative order.

If an input error is automatically detected, the item in error is identified and the error is described.

Labels or instructions are provided when content requires user input.

If an input error is detected and suggestions are known, they are provided.

For pages with legal commitments or financial transactions: reversible, checked, or confirmed.

Information previously entered by the user is auto-populated or available for selection.

Cognitive function tests are not required for any step in authentication unless alternatives are provided.

For all UI components, the name and role can be programmatically determined; states, properties, and values can be set programmatically.

Status messages can be programmatically determined without receiving focus.