This checklist will not make your website completely accessible. Full accessibility requires training and a nuanced approach. This checklist is a collection of legal requirements and best practices to help people with limited accessibility training make websites more accessible. For content like text, images, graphics, and audio/video, refer to the “Basic checklists” at accessibility.ucsd.edu/checklists.
If you're creating web content using templates and modules within Hannon Hill Cascade Server (supported by IT Services), then accessibility standards are already optimized. Do not override or add new styles, text sizing, colors, or other formatting!
Semantic HTML elements are used (e.g., <header>, <nav>, <main>, <article>, <footer>) to help screen readers interpret content correctly.
Appropriate HTML tags are used (like <table> for tabular data and <p> for paragraphs) instead of generic <div> or <span> tags.
ARIA attributes (Accessible Rich Internet Applications) are used to enhance accessibility, such as role="banner", role="navigation", or role="button" where necessary.
A skip link is used to provide quick access to the main content of each page. This allows a person to easily bypass globally repeated content such as a website's primary navigation or persistent search widget. The skip link is visible when focused.
Viewport zoom is not disabled.
The autofocus attribute is not used.
Extending timeout sessions is allowed.
Links do not open in a new tab or window. If they must, indicate that in the link text. E.g. “See pricing in a new tab”.
Path-based gestures with a pointer or finger are not used unless absolutely necessary.
All pointer executions use the up-event, not the down-event.
Focusing or changing the settings on user interface components doesn’t change context or meaning of the paged unless the user has been advised of the behavior before using the component.
Multiple components with the same functionality are identified consistently.
Labels or instructions are provided when content requires user input.
For pages that cause legal, financial, or user-data changes, the data is validated and the user has an opportunity to check the submissions and modify or reverse them.
Status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.
Colors or sensory characteristics are not used alone to convey meaning.
User interface components have a contrast ratio of at least 3:1 against adjacent color(s).
User interface components do not contain anything that flashes or blinks more than three times in any one-second period — strobe effects should never be used.
User interface components with labels that include text or images of text have a name that contains the text that is presented visually.
A link to an accessibility statement and/or contact information for recipients who need assistance or further accommodations is provided.
Long or complicated forms are broken into sections.
Autocomplete is available for common elements like name, address, and phone number.
Form errors are clearly presented with specific details above the form upon a failed submission. Make sure the error messages clearly correspond to the related fields. Dynamic error messages from data-validated fields are even better.
The website is tested with screen readers like NVDA, JAWS, or VoiceOver to ensure it is navigable and all elements are read correctly.
The website has been tested on different web browsers (Chrome, Firefox, Internet Explorer, Safari) and devices (desktop, tablet, mobile) to ensure proper rendering and accessibility.
All content is accessible without a mouse. Navigate through your website using only the keyboard (Tab, Shift+Tab, Enter, Space) to ensure this.
SiteImprove has been used to confirm an accessibility score of at least 95% for level A and 90% for AA.
Ensure appropriate proximity of elements using The Straw Test.