|
1.1.1 Non Text Context
|
Images, icons, buttons, and other non-text content need meaningful text alternatives unless decorative.
|
Use a screen reader to confirm images and icon controls have appropriate accessible names or are marked decorative.
|
|
|
1.3.1 Info and Relationships
|
Structure and relationships must be programmatically available, such as headings, lists, tables, labels, and groups
|
Inspect HTML/semantics and test with a screen reader to confirm structure is announced correctly.
|
|
|
1.3.2 Meaningful Sequence
|
Content must be presented in a logical reading order when sequence affects meaning.
|
Navigate with a screen reader and keyboard. Confirm the reading and focus order match the visual order and preserve meaning.
|
|
|
2.4.1 Bypass Blocks
|
Users must be able to bypass (skip) repeated content, such as headers, navigation menus, or sidebars.
|
Check for skip links, landmarks, headings, or other mechanisms that let keyboard and screen reader users move directly to main content.
|
|
|
2.4.2 Page Titled
|
Each page must have a descriptive title that identifies the page’s purpose or topic.
|
Check the browser tab, HTML <title> element, and screen reader announcement to confirm the title is unique and descriptive.
|
|
|
2.4.4 Link Purpose (In Context)
|
The purpose of each link must be clear from the link text or its surrounding context.
(No links that just say: “Click Here”)
|
Review links with a screen reader and visually on the page. Confirm vague links such as “Click Here” or “Read More” make sense in context.
|
|
|
2.4.6 Headings and Labels
|
Headings and labels must describe the topic, purpose, or function of the content or control.
|
Review page headings and form/control labels. Confirm they are clear, descriptive, and match the content or action they identify.
|
|
|
3.3.2 Labels or Instructions
|
Forms and inputs must provide labels or instructions when users are expected to enter information.
|
Inspect each input, dropdown, checkbox, and form field. Confirm visible labels, required field indicators, format instructions, and error-prevention guidance are provided where needed. Confirm these can be discovered and announced by screen readers
|
|
|
4.1.2 Name, Role, Value
|
User interface components must expose their accessible name, role, state, and value to assistive technologies.
|
Test with a screen reader. Confirm buttons, links, menus, dialogs, tabs, and form fields announce correct names, roles, states, and values.
|
|
|
4.1.3 Status Message
|
Status messages must be announced to screen readers without moving focus, such as errors, confirmations, or loading updates.
|
Trigger status messages and test with a screen reader. Confirm updates are announced using appropriate live regions or programmatic status messaging without forcing focus changes.
|
|