Thread Subject: Re: Thoughts on Current Web Proposal
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: Bekure, Blene W.
Date: Mon, Mar 26 2007 8:00 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Fratkin, Mike: "Re: Thoughts on Current Web Proposal"
- Previous message in thread: Debbie Cook: "Re: Thoughts on Current Web Proposal"
- Messages sorted by: Author | Thread | Date
I couldn't agree anymore! I do not think it should be dropped.
Blene W. Bekure
-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Debbie
Cook
Sent: Tuesday, March 27, 2007 10:48 AM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Thoughts on Current Web Proposal
Don wrote:
5. I am wondering if we should delete the frames requirement 1194.22(i).
At least for screen readers, definitive frame naming is helpful, but no
longer a major issue in terms of site navigation and comprehension.
DC: Ironic that we've been concerned about accommodating people who are
deaf-blind but would unintentially toss out the much larger population
of people with both vision and learning limitations. No, I wouldn't make
more of this standard than it is, but I most certainly wouldn't drop it.
It definitely provides meaningful orientation until screen readers
become smart enough to stop reading this invisible text altogether. Wish
we could actually prohibit the use of frames, but of course that's way
out of bounds.
- Next message in Thread: Fratkin, Mike: "Re: Thoughts on Current Web Proposal"
- Previous message in Thread: Debbie Cook: "Re: Thoughts on Current Web Proposal"