WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JavaScript always On?

for

From: Greg Gamble
Date: Jul 11, 2013 11:17AM

No, they're moving the ability to disable JS to the config page. It can still be disable, but you need to go to about:config and update the "javascript.enabled" preference. The current link under tools > options > content is going to be removed.

Any plugins should continue to work, but not sure on that.

Greg

-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of <EMAIL REMOVED>
Sent: Thursday, July 11, 2013 9:37 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] JavaScript always On?

Greg Gamble wrote:

> Since Firefox is removing the ability to disable JavaScript soon

Wait, removing it in the sense that it will break NoScript?

> Personally, I think it's a good thing. We'll no longer need to design pages that fallback gracefully any more.

If they are actually going to disable the ability to turn off
JavaScript, this is a terrible thing. First of all, Firefox is
not the only browser, so we will certainly still need to design
pages that fall back gracefully (not to mention the
JavaScript/SEO issues).

Additionally, as a person with accessibility needs,
I have to control JavaScript very tightly, because of all of the
pages where bad JS prevents keyboard manipulation in the browser
(e.g. capturing keystrokes that are commonly used browser
keystrokes). For example, the default Google homepage is
completely uncontrollable by keyboard without disabling
JavaScript, because the search box captures every single
keystroke. (You can disable that functionality, only if you have
the desire and authority to set Google preferences for that
browser, and not everyone has those.).

Deborah Kaplan
Accessibility Team Co-Lead
Dreamwidth Studios