Section 508 Developer Tip Series
CMS Section 508 Program has launched a Developer Tip Series to help our Content Developers meet our Agency’s Section 508 Policy. This Tip Series provides technical guidance on information and communication technology (ICT) covered under Section 508 of the Rehabilitation Act of 1973.
This Tip Series includes guidance on the following:
JAWS Screen Reader - CMS utilizes the current version of Job Access With Speech (JAWS) to asses our technologies, applications and communications.
Color used as Sole Method to Convey Meaning (PDF) - Carries a “high impact” consideration and should be prioritized during development and remediation.
Error Handling (PDF) - Carries a “high impact” consideration and should be prioritized during development and remediation.
Field Labels (PDF) - Carries a “high impact” consideration and should be prioritized during development and remediation.
Forms Overview (PDF) - Much of a user’s online experience may include forms. Forms are a major part of using the web whether we are entering a username and password to gain access to a site/account, or filling out a sign-up/application form for car insurance.
Automated and Manual Testing Marriage (PDF)– Provides the benefits and differences for both automated and manual testing.
Color Contrast (PDF)– Carries a “high impact” consideration and thus, should be prioritized during development and/or remediation.
Focus Indicators (PDF)– Carries a “high impact” consideration and must be prioritized during development and/or remediation. They provide critical guidance on where focus is among interactive elements so that users will know what element/block of text currently has prominence.
Image and Alternative Text (PDF)– Accessible images, depending on the type, typically carry a “high impact” consideration and should be addressed during development and/or remediation.
Keyboard Accessibility (PDF)– Carries a “high impact” consideration and must be prioritized during development. One of the most important aspects of Section 508 compliance is ensuring software and web content are keyboard accessible. Essentially, all functions that can be performed with a mouse must also be executable via a keyboard.
Error Handling, Screen Readers (PDF) - Carries a “high impact” consideration and should be prioritized during development and remediation.
ARIA Overview (PDF) - Is a coding tool to use in situations where non-semantic HTML needs to be more accessible.