Section 508
Section 508 requires United States federal agencies to make their mobile apps accessible for everyone. This means that federal employees with disabilities are able to do their work with accessible apps. Section 508 also means that a person with a disability applying for a job with the federal government or a person who is using an agency’s app, has access to the same accessible information and resources available to anyone.
What does this mean for you as a developer?
What you have to do to comply is laid down in chapter E207.2 of Section 508. It basically means you need to confirm to the Success Criteria of WCAG 2.0 Level A and Level AA. An overview of all Succes Criteria that apply is listed immediately below. Followed by an explanation of the structure of Section 508.
Succes Criteria that an app must meet at least
- Success Criterion 1.1.1 - Non-text Content - Level A
- Success Criterion 1.2.1 - Audio-only and Video-only (Prerecorded) - Level A
- Success Criterion 1.2.2 - Captions (Prerecorded) - Level A
- Success Criterion 1.2.3 - Audio Description or Media Alternative (Prerecorded) - Level A
- Success Criterion 1.2.4 - Captions (Live) - Level AA
- Success Criterion 1.2.5 - Audio Description (Prerecorded) - Level AA
- Success Criterion 1.3.1 - Info and Relationships - Level A
- Success Criterion 1.3.2 - Meaningful Sequence - Level A
- Success Criterion 1.3.3 - Sensory Characteristics - Level A
- Success Criterion 1.4.1 - Use of Color - Level A
- Success Criterion 1.4.2 - Audio Control - Level A
- Success Criterion 1.4.3 - Contrast (Minimum) - Level AA
- Success Criterion - 1.4.4 Resize text - Level AA
- Success Criterion 1.4.5 - Images of Text - Level AA
- Success Criterion 2.1.1 - Keyboard - Level A
- Success Criterion 2.1.2 - No Keyboard Trap - Level A
- Success Criterion 2.2.1 - Timing Adjustable - Level A
- Success Criterion 2.2.2 - Pause, Stop, Hide - Level A
- Success Criterion 2.3.1 - Three Flashes or Below Threshold - Level A
- Success Criterion 2.4.2 - Page Titled - Level A
- Success Criterion 2.4.3 - Focus Order - Level A
- Success Criterion 2.4.4 - Link Purpose (In Context) - Level A
- Success Criterion 2.4.6 - Headings and Labels - Level AA
- Success Criterion 2.4.7 - Focus Visible - Level AA
- Success Criterion 3.1.1 - Language of Page - Level A
- Success Criterion 3.1.2 - Language of Parts - Level AA
- Success Criterion 3.2.1 - On Focus - Level A
- Success Criterion 3.2.2 - On Input - Level A
- Success Criterion 3.3.1 - Error Identification - Level A
- Success Criterion 3.3.2 - Labels or Instructions - Level A
- Success Criterion 3.3.3 - Error Suggestion - Level AA
- Success Criterion 3.3.4 - Error Prevention (Legal, Financial, Data) - Level AA
- Success Criterion 4.1.1 - Parsing - Level A
- Success Criterion 4.1.2 - Name, Role, Value - Level A
Apps do not need to conform to 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation and 3.2.4 Consistent Identification. However, we recommend that you still try to meet these criteria.
Depending on the functionalities of your app, you might need to meet additional requirements from other chapters.
Section 508 structure
The Section 508 standard consists of 7 chapters.
Chapter 1 provides general information, referenced standards and definitions.
Chapter 2 contains scoping requirements, information about providing access to all functionality, information about functional performance criteria and requirements for electronic content, hardware, software and support documentation and services.
Chapter 3 contains functional performance criteria for users without vision, with limited vision, without perception of colour, without hearing, with limited hearing, without speech, with limited manipulation, with limited reach and strength and with limited language or cognitive and learning abilities.
Chapter 4 contains requirements for hardware.
Chapter 5 contains requirements for software.
Chapter 6 contains requirements for support documentation and services.
Chapter 7 contains referenced standards.