Thread Subject: Re: Gaps in Web requirements - hidden elements
Note
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: Jim Thatcher
Date: Tue, Dec 19 2006 2:10 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Andrew Kirkpatrick: "Re: Gaps in Web requirements - hidden elements"
- Previous message in thread: Bekure, Blene W.: "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.
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Bekure,
Blene W.
Sent: Monday, December 18, 2006 8:54 AM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Gaps in Web requirements - hidden elements
I think we definitely do. Whether it would be modifying such codes or
using other alternatives the situation needs to be addressed.
Blene Bekure
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Sunday, December 17, 2006 8:17 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-websoftware] Gaps in Web requirements - hidden elements
Kate Walser raised the following point:
Elements that are hidden visually, but rendered by assistive
technologies - Elements that are hidden from view but still available to
the assistive technology due to how the page has been coded (e.g.,
display:none means it may not show up in the visual version of the site,
but the assistive technology doesn't interpret display:none and will
still present those elements to user). An example is a show/hide toggle
feature where the user with assistive technology never really has the
"hide" option since the assistive technology still finds the "hidden"
elements. Framework-generated sites (e.g., portals) have this problem to
a larger extent when lots of extra code is included and the assistive
technology picks it up. (may have potential synergy with 1194.22 d (info
about identity, function, etc., of element)).
Do we need to recommend adding a requirement to address this situation?
Andi
- Next message in Thread: Andrew Kirkpatrick: "Re: Gaps in Web requirements - hidden elements"
- Previous message in Thread: Bekure, Blene W.: "Re: Gaps in Web requirements - hidden elements"
WebAIM is an initiative of:
