WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: "no JavaScript" alternative

for

From: Birkir R. Gunnarsson
Date: Mar 14, 2011 5:48AM

Hi Mike

Just a thought. According to the WebAIM screen reader survey (that was
published just a few days back) something like 98% of screen reader
users have Javascript enabled in their browsers.
All modern screen readers should work fine with Javascript content, so
it seems like a better use of resources to concentrate on better
usability and accessibility, rather than support the very small
percentage of users who, for some reason, are using outdated browsers
or very old screen reader software, or choose to turn Javascript off.
Of course, in the perfect world, you should be able to do both, but I
think it is nearly impossible to always accommodate everyone.
Perhaps, if Javascript is disabled and the page can detect that, in
addition to the helpline banner displaying, you could say "this page
has detected that you have Javascript disabled. We appologize for the
inconvenience but some of this page's functionality relies on
Javascript for its operations. If you want to enable Javascript in
your browser, please see page (x)".
This is assuming you find a good page that explains how to enable
Javascript in different browser types and versions.
This might be overkill, but it is always nice to get as specific an
error message as possible, ideally with links to solutions.
Good luck with the project.
-Birkirbrowsers

On 3/13/11, mikeyb leeds < <EMAIL REMOVED> > wrote:
> Hello everyone,
>
> I have a question regarding websites that are accessible, but parts rely on
> JavaScript being enabled.
>
> I am thinking of creating some functional parts of a website e.g a
> calculators, which are accessible, but will not work without JavaScript
> enabled. The stats I've found show more than 99.5% of visitors have
> JavaScript enabled.
>
> So the behaviour would be as follows:
> 1. If viewed with a device without JavaScript enabled, a banner would be
> displayed saying something like "Please call our 24 hour help line for more
> information".
> 2. If viewed in "accessible" or "mobile" device mode, a lean page, with
> text and very few images is displayed.
> 3. If viewed in desktop mode with JavaScript enabled, there would be more
> visual content, but the pages remain accessible.
>
> I currently have a development choice …
> Unfortunately we have a system which makes it extremely difficult to change
> server side content functionality (e.g. php/jsp) as this is done by another
> department but easy to change (html, css and javascript) . So we can either
> spend considerable effort maintaining our "none JavaScript" versions of
> things like calculators or use a lot less effort to create a site with
> better accessibility, usability and features for all users with JavaScript
> enabled devices using a "webservice".
>
> For the sake of argument please consider two types of applications:
>
> One you use weekly like a bank balance or investment portfolio, and,
>
> One which you access very occasionally, like twice a year, e.g. insurance
> details.
>
> So given the choice, which would you prefer?
>
> Solution "A" has a version which works when JavaScript is disabled.
> Solution "B" displays a help desk number when JavaScript is disabled, but
> offers better usability and accessibility, and overtime better
> functionality.
>
> P.S I know you may be thinking you'd like to do Solution "C", better
> usability, accessibility and functionality even when JavaScript is
> disabled... me too! unfortunately we only have a fixed amount of resources.
>
> Can those of you who have JavaScript disabled please shout up and tell me
> what your are using!
>
>
> Thanks for your help.
>
> Mike
>