UX Accessibility Checklist

The interface can be used in all screen orientations (Portrait and Landscape mode).
1.3.4 Orientation (AA)

The layout is responsive and adapts to the viewport size. Should at a minimum to 320 x 568 size.
1.4.10 Reflow (AA)

UI components and graphical objects have a contrast ratio of at least 3:1 against the adjacent color
1.4.11 Non-Text Contrast (AA)

Small text (up to 24px regular or less than 18,5px bold) have a contrast ratio of at least 4,5:1 against the adjacent color.
1.4.3 Contrast (Minimum) (AA)

Large text (at least 24px regular and 18,5px bold) have a contrast ratio of 3:1 against the adjacent color.
1.4.3 Contrast (Minimum) (AA)

Links and graphs are identified by something more than color.
1.4.1: Use of Color (A)

Headings, labels and buttons are informative.
2.4.6 Headings and Labels (AA)

The page has a headline that describes the main content of the page.
1.3.1 Info and Relationships (A)

Instructions do not rely on sensory characteristics (e.g click on the right button etc.)
1.3.3: Sensory Characteristics (A)

There are no images of text. Logotypes are considered essential as long as they don’t act as a heading.
1.4.5 Images of Text (AA)

Components having the same functionality is used and identified consistently. In general, use the same terminology on the site
Example: Do not use two different labels for the same function e.g Download and Share with the same graphical element, and make sure to use the same link text to the same destination.3.2.4: Consistent Identification (AA)

Row or column headings are easily distinguishable and marked
1.3.1: Info and Relationships (A)

Check if tables need descriptive title (mandatory)
1.3.1: Info and Relationships (A)

Avoid moving, blinking and scrolling content like carousels and background videos that start automatically. If there are such elements it must be possible to pause them
2.2.2 Pause, Stop, Hide (A)

Provide a way to pause or stop moving elements or animations if they last longer than 5 seconds
2.2.2 Pause, Stop, Hide (A)

The tab order is logical. Focus should not go in an unexpected order
2.4.3 Focus order (A)

Required input field is marked up with color, text and programmatically associated
1.4.1: Use of Color (A)

All errors in forms are described in text.
3.3.1 Error identification (A)

All interface elements requiring user input have a visible label
3.3.2 Labels or instructions (A)

Provide important instructions or cues for input fields so that users know what input data is expected.
3.3.2 Labels or instructions (A)

Errors are described in text with information on how to correct those error (if possible)
Example: 3.3.1 requires that the error message have a textual description, while 3.3.3 requires that the description also contains information on how to correct the error.3.3.3 Error suggestions (AA)

Important forms let the user review, edit and confirm data before submitting.
Example: This applies to all forms that involve a legal contract or financial transactions.
3.3.4 Error prevention (AA)