Thread Subject: Re: Gaps in Web requirements - hidden elements
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Andrew Kirkpatrick
Date: Tue, Dec 19 2006 2:25 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: Jim Thatcher: "Re: Gaps in Web requirements - hidden elements"
- Messages sorted by: Author | Thread | Date
> It used to be that screen readers ignored display:none and
> visibility:hidden styles. That is not true anymore at least
> with the last two versions of JAWS and Window-Eyes. These
> both respect these styles.
Jim is simplifying the situation intentionally, but of course it wasn't
that clear cut either. There were lots of implementation details that
impacted whether JAWS ignored these, such as how the CSS was referenced
in the HTML (@import, inline css, using the link element, etc.).
I believe that AT should honor the intent of display:none, which is to
not voice content styled with that, but I'm not sure how that would fit
into a guideline. I can see how it might fit into an accessibility API
whether the information is available to AT from the user agent though...
- Next message in Thread: None
- Previous message in Thread: Jim Thatcher: "Re: Gaps in Web requirements - hidden elements"