The following tests can be used to quickly check the accessibility of web pages (and PDF documents). Complete testing will still need to be performed by experienced testers using assistive technologies, but these tests can help you catch and correct many errors prior to final testing.
If you can, use the W3C HTML Validator (http://validator.w3.org) to validate your code. Make sure there are no errors about tags being omitted or incorrect.
Bonus: In the Validator, under More Options, check Show Outline, validate, scroll down to the Document Outline, and check that headings are present and in the right order.
|Disable Styles||In your browser, disable styles (e.g., View menu: Style: No Style), and check that headings are large & bold, lists have bullets or numbers, and the order of content is correct.|
|High Contrast||In Windows, activate high contrast (Control Panel: Accessibility Options: Display: Settings: High Contrast Black, then Left Alt + Left Shift + Print Screen to toggle); check that all text responds to color changes and that no important information disappears.|
|Contrast||Download and use the Colour Contrast Analyzer (https://developer.paciellogroup.com/resources/contrastanalyser/) to check the contrast ratio for each combination of text and background colors. Check for a minimum of 4.5:1 for regular test and 3.0:1 for large text.|
|Images||Download and use the Web Accessibility Toolbar (https://developer.paciellogroup.com/resources/wat/) or a similar browser extension to turn off images and show alt text. Check that decorative images do not have alt text, images of words have alt text that includes the same words, and image links have alt text that identifies the link's destination.|
|Multimedia||For any videos, check that they show, or have an option to show, closed captions. (For any audio recordings, check that there is a text transcript.)|
|Form Fields||Use the mouse to click on each form field label; focus should jump to the associated field. Confirm that each field has an associated label. If a field does not have a visible label, hover the mouse pointer over the field and check that it has an appropriate title attribute, which will appear as a tool tip. (If it doesn't have either of these, have a developer check the code for aria-label attributes.)|
|Tab Order & Link Text||Use the Tab key to move through all links and form fields. Confirm that you can tab to all fields in the expected order and that the text of each link is unique and understandable.|
|Custom Controls||Try to operate any interactive elements (drop-down menus, tab pages, etc.) using only keyboard commands (e.g., Tab key, up/down arrows, space bar, etc.). Check that all can be operated using only the keyboard without any unexpected results. See ARIA Authoring Practices Design Patterns (http://www.w3.org/TR/wai-aria-practices/#aria_ex) for a complete list of standard keyboard commands.|
|PDF Documents||Open PDF documents in Adobe Reader and save as "accessible text" (File: Save as Text). Open the text file and confirm that all text is present and in the right order.|
|PDF Forms||Hover the mouse pointer over each form field and check that an appropriate label appears as a tool tip. Tab to each field and check that it can be operated using the keyboard.|