Accessibility Testing

This project is compliant with Section 508. While Section 508 has fewer specs than the Web Content Accessibility Guidelines, WCAG is expected to be incorporated into Section 508 soon, so we can preemptively up our game by striving to achieve compliance with WCAG 2.0 Level AA (Intermediate).

These guidelines are detailed below:

Guideline	Notes
1.1.1 – Non-text Content Provide text alternatives for non-text content	test
1.2.1 – Audio-only and Video-only (Pre-recorded) Provide an alternative to video-only and audio-only content	N/A
1.2.2 – Captions (Pre-recorded) Provide captions for videos with audio	N/A
1.2.3 – Audio Description or Media Alternative (Pre-recorded) Video with audio has a second alternative	N/A
1.2.4 – Captions (Live) Live videos have captions	N/A
1.2.5 – Audio Description (Pre-recorded) Users have access to audio description for video content	N/A
1.3.1 – Info and Relationships Logical structure
1.3.2 – Meaningful Sequence Present content in a meaningful order
1.3.3 – Sensory Characteristics Use more than one sense for instructions
1.4.1 – Use of Colour Don’t use presentation that relies solely on colour
1.4.2 – Audio Control Don’t play audio automatically	N/A
1.4.3 – Contrast (Minimum) Contrast ratio between text and background is at least 4.5:1	Can check using automated tools
1.4.4 – Resize Text Text can be resized to 200% without loss of content or function
1.4.5 – Images of Text Don’t use images of text
2.1.1 – Keyboard Accessible by keyboard only
2.1.2 – No Keyboard Trap Don’t trap keyboard users
2.2.1 – Timing Adjustable Time limits have user controls
2.2.2 – Pause, Stop, Hide Provide user controls for moving content	N/A
2.3.1 – Three Flashes or Below No content flashes more than three times per second
2.4.1 – Bypass Blocks Provide a ‘Skip to Content’ link
2.4.2 – Page Titled Use helpful and clear page titles
2.4.3 – Focus Order Logical order
2.4.4 – Link Purpose (In Context) Every link’s purpose is clear from its context
2.4.5 – Multiple Ways Offer several ways to find pages
2.4.6 – Headings and Labels Use clear headings and labels
2.4.7 – Focus Visible Ensure keyboard focus is visible and clear
3.1.1 – Language of Page Page has a language assigned	Can check using automated tools
3.1.2 – Language of Parts Tell users when the language on a page changes
3.2.1 – On Focus Elements do not change when they receive focus
3.2.2 – On Input Elements do not change when they receive input
3.2.3 – Consistent Navigation Use menus consistently
3.2.4 – Consistent Identification Use icons and buttons consistently
3.3.1 – Error Identification Clearly identify input errors
3.3.2 – Labels or Instructions Label elements and give instructions
3.3.3 – Error Suggestion Suggest fixes when users make errors
3.3.4 - Error Prevention (Legal, Financial, Data) Reduce the risk of input errors for sensitive data
4.1.1 – Parsing No major code errors	Can check using automated tool
4.1.2 – Name, Role, Value Build all elements for accessibility	Can check using automated tool