Test or evaluate your website accessibility
You may use one of the following programs to evaluate accessibility issues in a particular website program and design:
- WAVE Web Accessibility Evaluation Tool (http://wave.webaim.org/): Freely available tool to support testing accessibility from WebAIM.
- WAVE Toolbar (http://wave.webaim.org/extension/): Because no data is sent to WAVE server, can be used to evaluate content that is password protected, dynamically generated or scripted, or on an intranet.
Other Tools: W3C Web Accessibility Evaluation Tools List (https://www.w3.org/WAI/ER/tools/)
Evaluate form accessibility and usability
- Check to make sure all necessary instructions and cues are provided.
- Check that form controls are associated with a label element.
- Check that groups of checkboxes and radio buttons are associated using field set and leg end.
- Check that the form can be completed and submitted with a keyboard only.
- When tabbing through the form, make sure the navigation order is logical and consistent with the
visual order of the form.
- Check that error recovery is functional after form validation.
- Alert the user to the presence of the error in an obvious and accessible manner.
- Allow the user to easily access the form controls that need to be modified.
- If certain form fields are required, the field should be labeled accordingly, and configured to alert
the screen reader.
- After submitting the form, user will need to be alerted to submission confirmation and any
- Allow resubmission and revalidation of the form (http://webaim.org/techniques/formvalidation/).
- The use of CAPTHCA is inaccessible and should not be used to validate submissions.
- Use tables for tabular data, not for layout because tables add additional verbosity to screen reader
- Use of ARIA roles and landmarks to enhance the ability of screen reader users to navigate and
interact with content.
- Make dynamic content accessible (https://webaccess.berkeley.edu/resources/tips/web-
Test with a Screen Reader
Screen reader users navigate using functions that are more sophisticated than just reading the page. Testing with a screen reader can be useful to get a sense for how navigation, forms, and dynamic content are working.