Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Can a site REQUIRE Javascript and still be Section 508-compliant?

I think I understand HOW Javascript has to work in order to be O.K. for section 508. But I have been unable to find an answer to a related question: does my site need to work WITHOUT Javascript in order to be section 508 compliant?

To take an extreme case, if users without Javascript cannot log in, does that violate section 508 compliance? And if so, where in the text is that explained?

I know that all content has to be accessible with screenreaders, for keyboard-with-no-mouse users, etc. BUT does all content need to be accessible to users without Javascript?

like image 961
Mike Kantor Avatar asked Jun 28 '10 20:06

Mike Kantor


People also ask

What does Section 508 specifically require for accessible sites?

The US Access Board established the Section 508 standards that implement the law and provides the requirements for accessibility. Section 508 requires federal agencies to make their ICT such as technology, online training and websites accessible for everyone.

What makes a website 508 compliant?

508 Compliance is shorthand for a law that requires federal government websites to be safe and accessible for people with disabilities. This law covers a range of issues related to assisting people with different kinds of disabilities.

Is JavaScript accessible?

A web page containing JavaScript will typically be fully accessible if the functionality of the script is device independent (does not require only a mouse or only a keyboard) and the information (content) is available to assistive technologies.

What are two types of technologies included in designing accessible Section 508 systems?

Summary of Section 508 Technical Standards The standards provide criteria specific to various types of technologies, including: Computers and peripheral equipment. Information Kiosks and Transaction Machines. Telecommunications Equipment.


1 Answers

Recent surveys have found that a vast majority of users that run screen readers have JS enabled, not disabled. Granted, a screen reader does what its name implies: it reads the screen. If a screen reader doesn't know where to read, then it can't do its job. For instance, modal dialogs are probably a bad idea if you're looking to support those users, though including something like form validation probably isn't a terrible idea.

The idea is to keep items on the screen from changing too rapidly. If you update large elements of your UI frequently using JS, you're probably not going to get too great of a response from the screen reader community. On the other hand, if the majority of the JS is behind-the-scenes, then most screen reader users probably won't even notice that you're using scripts.

The list at the bottom of the link I provided above gives some great insight into the biggest problems that screen reader users face. Avoiding any situations where those scenarios might pop up (i.e.: visual CAPTCHAs, complex layouts, rapidly updated UI elements, etc.) will probably leave you in good shape.

And as always, download yourself a screen reader (there are plenty of free and open source readers available) to test out your software.

like image 79
mattbasta Avatar answered Sep 19 '22 15:09

mattbasta