Many web developers, graphic designers and others in technology and media will eventually meet a project that must follow the Section 508 standards or other website accessibility rules. The Section 508 standards can be intimidating for a beginner, as they carry a lot of legal implications. While Section 508 is constitutionally binding only for the United States federal agencies and for the ones who are funded federally, often an organization that provides public services might request a website or software that needs to meet the requirements for Section 508.
Approximately 20% of all Americans have some form of physical limitation; of them, about half of those are contemplated to be severe disabilities. By ignoring the accessibility demands of your audience, any business will inevitably lower the page views, lower (if not isolate) the target audience and eventually limit the website statistics.
Whether working for the federal government, a private company, or a nonprofit, the Section 508 standards and accessibility best practices serve all users, which should be met well before the design or development of the website is executed.
What is Section 508?
Section 508 is an amendment to the United States Workforce Rehabilitation Act of 1973 which was further amended in 2001. It is a federal law that mandates that all electronic and information technology developed, procured, maintained or used by the federal government must be accessible to people with disabilities; the Section 508 standards are the technical rules that say how. 508 Compliance, hence, involves developing a website that people with restricted vision or blindness, deafness, seizure disorders, and other kinds of physical disabilities can use.
Along with the revisions to the Federal Acquisitions Regulations (FAR), the Electronic and Information Technology (EIT) Accessibility Standards were also published. With the law in place, federal employees with disabilities or any members of the public sector using national information and technology will now have the same access as others to any website.
Who Needs to Meet the Section 508 Standards?
All organizations and businesses should make it a priority to meet the Section 508 standards on their official website, even when the law does not force them to.
Not only does a 508-compliant website make any business accessible to more leads with potential customers with disabilities, but failing to fulfil the same might result in a costly lawsuit for a company.
Depending on the current website condition, you have to decide what you need to do to satisfy 508 compliance. While some websites may only need only a few changes to be appropriately accessible, many others are likely to require a complete website redesign.
Updates to the Section 508 standards
The accessibility requirement for ICT, mentioned in Section 508 of the Rehabilitation Act 1973, was amended, and the absolute rule was given in January 2017 by the US Access Board. The revised Section 508 standards now have the following objectives:
- Improving the accessibility of information technology for people with various disabilities
- Keeping up with the continually changing technology and modernization of the gadgets
- To ensure that the requirements in the standards are more accessible to follow and understand for everyone
- To ensure that the conditions conform to what is required by other international standards
The Section 508 standards have three main elements to meet:
- Technical – these conditions make sure that the coding of software, website, operating systems, and others are compatible with the assistive technologies.
- Functional – these elements ensure that apart from the extension to the technical coding, the entire system is ready for someone with a disability.
- Support – these requirements ensure that support documents and alternative information are equally accessible by people with physical disabilities.
Every information and communication technology (ICT), which involves a website, digital document, web app, agency, or even contractor, is expected to completely comply with the updated Section 508 Standards from January 18th, 2018. Here are some of the significant changes in the Section 508 revised standard:
Understanding the Functionality
As per the revised rule, products should be organized per their feature rather than their type to keep up with technological progress. If your application or website is inaccessible due to the use of software or technology which is not recognized under Section 508 Standard, or if it is difficult because the technical compliance fails to translate it to a suitable user experience, the website is required to review the Functional Performance Criteria to understand Section 508 compliance. Functional Performance Criteria commands that you grant options that can inscribe the type(s) of disability that is unable to access your ICT.
Adoption of WCAG AA 2.0
The revised Section 508 standards incorporate WCAG 2.0 AA by reference, the same standard used globally. Similar to Section 508, WCAG 2.0 AA does not give particular tasks which the webmasters must meet to make a website accessible and compliant. Instead, the guidelines describe what available sites must do, with a focus on functionality rather than form. This gives webmasters the capability to execute a solution that works best for their needs.
Section 255, Telecommunication Act
Section 255 is the standard that controls the telecommunication service providers along with the equipment manufacturers. This standard was updated to take into account the current improvements in telecommunication technologies, particularly mobile and smartphone technologies. This rule now also regulates the software and apps which are integrated into handheld mobile devices. The Section 508 standards expect all telecommunication devices to comply with Section 255 as well.
Expanded Marketplace
The revised standard incorporates all the related international standards, including WCAG 2.0 (Web Contents Accessibility Guidelines) and EN 301 549 (European Commission ICT Standards). They are used to create web standards, and clarify the suitability of websites, software, and electronic documents, and facilitate the creation of a broader marketplace for easy technological solutions worldwide.
We are Here to Help You
Clients who need the Section 508 standards met in their websites, documents or software will expect you to have proficiency and experience with them. So, if you expect to list Section 508 as one of your skills, you might consider getting in touch with the experts who will help you to adhere to those accessibility standards.
After going through this article, are you trying to reach a thoughtful conclusion? Accessibility of websites for all users, including those with any form of physical disability, is crucial regardless of the content of the site. Would you like to get further information on ways to make your website accessible? Are you excited to know the performance of your website when tested on accessibility standards? Are you looking for expert web accessibility services in India?
Section 508 standards: frequently asked questions
What do the Section 508 standards require in practice?
For web content, conformance with the WCAG 2.0 Level A and AA success criteria, which the revised rule incorporated by reference in 2017. The same requirement extends to electronic documents such as PDFs, to software user interfaces and to support documentation. In practice, teams now test against WCAG 2.1 or 2.2 AA, because those versions include everything in 2.0.
Do the Section 508 standards apply to private companies?
Directly, only when a company sells ICT to a federal agency or receives federal funding. Indirectly, yes: agencies must buy accessible products, so vendors who cannot show conformance – usually through a VPAT completed as an Accessibility Conformance Report – lose the contract.
What is the difference between the Section 508 standards and the ADA?
Section 508 binds federal agencies and their suppliers, while the ADA applies to state and local governments and to businesses open to the public. Both lean on WCAG, so the fixes are the same; the legal route and the people who can complain are different.
How is conformance with the Section 508 standards documented?
With a Voluntary Product Accessibility Template (VPAT) completed as an Accessibility Conformance Report (ACR). It lists every applicable criterion and states whether the product supports it, partially supports it or does not. Procurement officers read the ACR before they read anything else.
How do I check a website against the Section 508 standards?
Run an automated scan (axe, WAVE or Lighthouse), then test by keyboard and with screen readers such as JAWS and NVDA, and check PDFs with Acrobat’s accessibility checker. Our web accessibility case study shows a full audit of this kind, step by step.
Are the Section 508 standards updated regularly?
The last major refresh was the 2017 rule, effective January 2018, which replaced the original 2000 standards. The U.S. Access Board has since signalled that a future update will point to a newer WCAG version, so building to WCAG 2.2 AA today is the safest way to stay ahead of the next revision of the Section 508 standards.
The Ananyoo Team can help you to estimate the performance of your website against WCAG 2.0 through a free scan that will deliver a detailed report about the findings. Our experts offer a free 30-minute consultation which can be further utilized to take care of the concerns of your website accessibility. Visit our website to get in touch with our experts!
Leave a Reply