Imagine your phone is switched off while making a payment inside a mobile store. You ask them to charge your phone just enough to make the purchase, but the store owner denies it. Wouldn’t that frustrate you? A similar situation arises when government websites are inaccessible to people with impairments. Thus, the Section 508 law was made to address this issue. In this blog post, we will review the basics of the 508 law, delve into types of testing and end with best practices.
Table of Contents
What is Section 508?
Section 508, a part of the Rehabilitation Act of 1973, mandates equal access to electronic and information technology for people with disabilities. It includes all types of Information and Communication Technology(ICT), including websites, mobile apps, online training material, and documents. In 2018, a new rule was implemented that mandates adherence to the Website Content Accessibility Guidelines (WCAG) 2.0 standard for Section 508 compliance.
WCAG 2.0 Level AA is the higher standard that most federal websites and other ICT need to meet. Compliance is crucial ethically, as it ensures equal access to electronic and information technology for website owners with federal grants or contracts, as well as for business purposes.
What Content Types Are Tested for Section 508 Compliance?
Section 508 Compliance covers various aspects of a website, including:
- Text alternatives for images (e.g., alt text).
- Keyboard navigation and focus order.
- Color contrast and visual design.
- Accessible multimedia (captions, transcripts).
- Document accessibility (e.g., PDFs).
- Website material, software, records, tables, worksheets, and presentations with audio and video. Website material includes all elements on a website, evaluated for responsiveness and effectiveness on all platforms and devices.
Software developers may perform 508 compliance testing to identify bugs, usability concerns, and assess accessibility features. For instance, tables and worksheets might be interpreted differently by assistive technologies.
Consequences of non-compliance with Section 508
Organizations that fail to meet accessibility standards risk lawsuits, financial penalties, and damage to their reputation. Initial violations can result in fines up to $55,000, with subsequent violations reaching $110,000. Non-compliant organizations may also lose federal funding.
Inaccessible ICT limits the ability of employees and customers with disabilities to engage effectively with the organization. Additionally, public perception may suffer, as the brand could be seen as insensitive to accessibility, leading to decreased customer trust and loyalty. Ensuring accessibility benefits everyone by promoting equal access for all.
Here are some case studies that showcase the dire consequences of non-compliance:
Electronic Arts (EA) Inc.
Rafael Cordero, a blind user, sued EA in May 2022 for not making its website fully usable and accessible to blind and visually impaired users, citing issues with screen-reading software preventing free navigation, item descriptions, and prices.
DraftKings
Robert Jahoda, a visually impaired user, sued DraftKings in June 2022 for inaccessibility due to the company’s website not being compatible with screen-reading software, requesting compliance policy changes and attorney fees payment.
How to test for Section 508 compliance?
Effective Section 508 compliance testing requires a blend of automated tools, manual evaluation, and user testing to ensure digital content is accessible to individuals with disabilities and meets both legal and usability standards.
Manual testing involves reviewing various accessibility criteria that require human judgment and interaction with assistive technologies. This process helps assess website features and technologies for WCAG compliance, providing qualitative insights and identifying barriers for disabled users. However, manual testing can be time-consuming and costly.
In contrast, automated testing focuses on quantitative data, offering quick results at a lower cost. Tools such as Axe, WAVE, Google Lighthouse, and Tenon are commonly used for this purpose. While automated tools are efficient, they should be complemented by manual testing for a more thorough evaluation.
Hybrid testing combines both manual and automated methods to deliver faster, more comprehensive results.
User testing is also crucial, involving individuals who rely on assistive technologies like screen readers, magnifiers, or speech recognition software to ensure the content meets their accessibility needs.
Best practices to make website 508 compliant
Making a website 508 compliant involves implementing several best practices to ensure accessibility for individuals with disabilities. Here are some key practices to follow:
Understand and implement WCAG Standards which include:
Provide Text Alternatives for Non-Text Content:
Use alt text for all images, provide captions for videos, and include transcripts for audio. Decorative images should have empty alt attributes (alt=””).
Ensure Keyboard Accessibility:
Make sure users can navigate the site with a keyboard using a logical tab order and visible focus indicators for interactive elements.
Ensure Proper Color Contrast:
Ensure sufficient contrast between text and background (at least 4.5:1 for normal text), and don’t rely solely on color to convey meaning.
Create Accessible Forms:
Label form fields clearly, provide error feedback, and ensure forms are keyboard-accessible.
Establish a clear and logical navigation structure throughout your website to enhance accessibility, particularly for users with cognitive disabilities. Organize navigation links as list items, making it easier for them to find information.
Make Multimedia Accessible:
Provide captions and transcripts for videos, and ensure multimedia controls are accessible via keyboard or assistive technologies.
Implement Responsive Design:
Ensure the website works across devices and screen sizes, with legible, accessible content
Use Section 508 compliance checker:
Use a Section 508 compliance checker or WCAG guidelines to ensure your website meets accessibility standards. Regularly test and update your design with both automated tools and manual audits..
- Use a 508 compliance checklist based on WCAG standards to track accessibility progress.
- Implement standard HTML elements to ensure users can easily navigate and understand the website’s flow.
- Follow user-friendly website design and navigation and ensure it is compatible with Assistive Technologies (AT)
- Regularly test your website for accessibility across different browsers to ensure consistent performance.
- Create user-friendly interactive elements and responsive designs that work well across various viewport sizes.
- Regularly audit digital content (websites, documents, etc.) and include usability testing with individuals with disabilities to improve accessibility.
- Ensure that Voluntary Product Accessibility Template (VPAT) reports are submitted on time for transparency and compliance.
How can an accessibility partner help?
Section 508 Testing: A Holistic Approach
- Section 508 testing requires money, time and specialization, which can be solved by collaborating with accessibility partners like AEL Data to remediate it.
- An accessibility partner will employ automated testing tools and manual evaluations for all ICT, including assistive technologies, with the help of testing by users with disabilities.
- Each functionality will be tested, ranging from simple aspects such as alt text and navigation flow to more complex issues like embedded content accessibility.
- Providing a detailed report with recommended remediations for each issue, prioritized for your convenience.
- Clear and jargon-free report with direct access to our experts even after the project is completed.
- Assistance with completing the VPAT when needed.
- Finally, providing staff training to ensure long-term maintenance of accessibility standards.
Wrapping up
In summary, our blog described how to test for Section 508 compliance, including the content types covered under the law. It focuses on manual & automated testing of websites with best practices for 508 compliance. Additionally, we discuss the penalties for non-compliance through popular case studies. Lastly, we listed out best practices for making websites section 508 compliant and the importance of collaborating with accessibility partners.
