E-mail List Archives
Re: css off
From: Chris Hoffman
Date: Aug 25, 2009 8:20PM
- Next message: Despain, Dallas: "Re: css off"
- Previous message: Randi: "Re: Alternative CAPTCHA"
- Next message in Thread: Despain, Dallas: "Re: css off"
- Previous message in Thread: Despain, Dallas: "css off"
- View all messages in this Thread
I see two issues here. The first is how much authority Section 508
should have over modern Web applications. Section 508 was drafted long
before folks started turning divs into dialog boxes and pulling in
resources with Ajax and JSON-P, so maybe we shouldn't expect it to
apply, especially if we start distinguishing "Web pages" from "Web
applications". Section 508 can still reign over the pages, while newer
standards like WCAG-2 and ARIA can be used for compliance for
One caveat that comes with that approach is that Section 508 _also_
governs computer applications (albeit in a different subsection than
the one that covers Web pages), so that calling what you've developed
an application instead of a page doesn't necessarily get you off the
hook for compliance.
The second issue is whether 1192.22(d) (saying that a page should be
readable with CSS turned off) is achievable with a reasonable amount
of effort in a modern Web application. I think that it is. There is no
reason that divs that will be used as dialog boxes can't be included
in the document in positions and an order that makes logical sense, or
even be kept as separate pages that get pulled in with Ajax requests.
Getting it all to work may take some experimentation and a bit of
unorthodox coding (especially if you are using a CMS), but it would be
well worth it.
First, just because JAWS 10 has ARIA support doesn't mean that every
other assistive technology application out there supports it. I'm
willing to bet that there are plenty of well-aged screen readers out
there in the field (WebAIM's survey results notwithstanding; I have a
feeling they were skewed somewhat by the audience), and to them, a
Second, there's that oft-talked-about group of people who browse with
developer [grin]), screen readers or not. Their dialogs look like
And finally, suppose I want to print a page to read later, complete
with all its attachments and extra bits and pieces. My ink jet doesn't
do modal windows yet, so it would be great if everything I printed was
in an order that made sense.
On Tue, Aug 25, 2009 at 7:56 PM, Despain, Dallas< <EMAIL REMOVED> > wrote:
> Section 1194.22 (d) Of the section508 guidelines say that
> "Documents shall be organized so they are readable without requiring an associated style sheet."
> I thought that the spirit of this law is to make sure that the reading order is correct regardless of stylesheet? Our QA department is taking it literally and testing functionality of our pages with css off (using the "disable styles" function of the wave toolbar)
> This is causing problems because
> We are using web2.0 style dialogs in our application similar to these:
> JAWS respects and doesn't announce things with display:none applied, which I think is pretty much essential to designing web 2.0 pages.
> When you turn styles off in that page, it's hard to navigate because the dialog content shows up inline with the rest of the content and it's hard to tell where the dialogs begin and where they end.
> What do you guys think? Is it reasonable to expect these types of dialog to work and make sense with css off? I didn't see an equivalent wcag2.0 "css off" requirement except perhaps it can be implied form 1.3.2 Meaningful Sequence, and 2.4.3 focus order.
> Is this Section 1194.22 (d) an outdated guideline?