Testing Content for Accessibility Compliance
- Christina Lutz-Hatfield
Table of Contents
Overview
Editing Content and Testing for Accessibility Compliance
Whenever content has been edited it needs to be re-tested for accessibility compliance.
User Testing
User testing is a standard practice for ensuring accessibility compliance.
Accessibility Testing
The only way to know if your website is compliant with the city's Digital Accessibility and Inclusion Standards is to test it and complete an accessibility audit.
Types of Accessibility Tests
An accessibility audit is generally performed through a combination of automated and manual testing.
Automated testing:
An automated test involves using a software tool that will automatically scan your website for potential accessibility issues.
An automated test will scan and evaluate your website for potential accessibility issues.
Will scan the code against the WCAG guidelines which are the foundation for the DAIS.
May report false positives.
Review the automated test report and identity if they are valid issues.
An automated test will only identify 30-40% of issues.
Manual testing involves:
testing with a screen reader
conduct keyboard only testing
mobile testing
Screen Reader Testing
A screen reader will read out loud the web page content to the user.
A screen reader interacts with the web page by using different keyboard keystrokes.
JAWS is the most popular screen reader. Windows based and requires a paid license.
NVDA is a free, open source screen reader.
Please see more detailed information on screen reader testing.
Keyboard Testing
Users who rely on only using a keyboard to access online content.
Keyboard only users are not able to use a mouse.
Keyboard only users will use different keystrokes to navigate a web page and activate interactive elements.
Will use the TAB key to navigate through links, buttons and form controls.
Please see our keyboard testing guide that includes common keystrokes for different web interactions.
Mobile Testing
Website content must be fully accessible on mobile devices, including the use of mobile screen readers.
iOS and Android mobile devices both have built in screen readers. VoiceOver and TalkBack.
Mobile screen reader users use different tapping and swiping gestures to navigate through a web page and interact with site content.
Please see our mobile testing guide for more detailed information on how to conduct mobile testing.
User Testing
Test your website with real users to validate accessibility compliance.
1. Define Your Test Objectives
Determine what you want to achieve with the testing:
Identify specific areas or features to test.
Decide which disabilities or impairments you want to focus on (e.g., visual, auditory, motor, cognitive).
2. Recruit Participants
Find participants who represent a range of disabilities:
People with Disabilities: Involve individuals who have the types of disabilities you are testing for.
Assistive Technology Users: Include users of screen readers, magnifiers, voice recognition software, etc.
Diverse Demographics: Ensure a variety of ages, tech-savviness, and backgrounds for a comprehensive perspective.
3. Develop Testing Scenarios
Create realistic tasks and scenarios that users would typically perform with your product or service. Make sure these tasks cover key functionalities and areas of interest.
4. Prepare Testing Environment
Ensure the testing environment mimics real-world conditions as closely as possible:
Set up assistive technologies and adaptive devices that users typically use.
Ensure accessibility of the testing tools and environment.
5. Conduct the Test
Moderated Testing: Facilitate sessions where you observe users completing tasks, providing help as needed while gathering feedback.
Unmoderated Testing: Allow users to complete tasks on their own while recording their interactions and feedback.
Remote Testing: Conduct tests via online platforms to reach participants in various locations.
6. Collect and Analyze Data
Quantitative Data: Gather data on task completion rates, time taken, errors made, and other measurable metrics.
Qualitative Data: Collect feedback on user experience, difficulties encountered, and suggestions for improvement.
7. Identify Issues and Prioritize
Analyze the data to identify accessibility issues:
Categorize issues based on severity and impact.
Prioritize fixes based on how critical they are for users with disabilities.
8. Implement Changes
Work with your design and development teams to address the issues identified. Ensure changes are tested for effectiveness and compliance.
9. Iterate and Repeat
Accessibility testing should be an ongoing process:
Conduct regular testing as you make updates or changes.
Stay updated with changes in accessibility guidelines and best practices.
10. Document and Report
Prepare a report detailing:
The testing process.
Findings and issues identified.
Recommendations for improvements.
Changes made based on feedback.
Resources
Conducting an Accessibility Audit