Web Accessibility Checklist
Checklist to verify the web page content if it is accessible or not.
Related roles:
- Automated QA testing
- Manual QA testing
- Informative images have short, descriptive alt text and all decorative images have empty alt attributes
<alt="">. - Headings must be meaningful and used to create a hierarchical structure (heading levels must not be skipped).
- Layout does not use
<table>. - All pages that contain tables to convey relational data markup are using either
scopeoridwithheaders. - Items of information and definitions are properly structured as ordered
<ol>, unordered<ul>or definitions lists<dl>. - The reading order of the page is logical and intuitive.
- The visual presentation of text and images of text on all pages has a contrast ratio of at least 4.5:1.
- Users are able to resize (for example, zoom in) up to 200%, without loss of content or functionality
- Page content reflows on mobile devices (by changing the viewport size, 320px and up) as zoom increases up to 400%.
- Interactive elements (links, buttons, menus, expand and collapse toggles, etc) always receive focus when using keyboard.
- Static content (like headings, paragraphs, list items, etc) should not receive focus by default when using keyboard.
- A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
- Web pages have unique titles that describe topic or purpose.
- The purpose of each link can be determined from the link text.
- The language of the page and content is programmatically determined.
- All form elements have an associated
label. - Refer to the WET form validation page for generic validation and error message handling for Web forms.
<br>tags are not used to create whitespace; CSS is used instead.- Use the W3C Markup Validation Service to validate page markup.
Page details
- Date modified: