Thread Subject: Re: Proposal 21(b) Focus
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: Fratkin, Mike
Date: Thu, Nov 16 2006 5:55 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Barrett, Don: "Re: Proposal 21(b) Focus"
- Previous message in thread: Fratkin, Mike: "Re: Proposal 21(b) Focus"
- Messages sorted by: Author | Thread | Date
I agree that these are the two specific areas that I have mentioned in the past but do not feel that it should be restricted to just these two examples. Again, if the purpose of Section 508 is to provide comparable access, we should strive to have both web and software applications enable keyboard users the same efficiency and productivity as mouse users. Continually placing focus at the top of a screen in multi-page applications like electronic learning, electronic travel, benefits, etc. is just not comparable.
[Don Barrett wrote] A more realistic and narrowly focused alternative specifically related to web focus might be:
When a web page allows for the conducting of a search of the site or its corresponding database which results in the delivery of a search results page, scripting or other technology shall be used to force the focus to the beginning of the search results.Â In addition, when forms are refreshed after being submitted on-line which contain error messages resulting from that submission, the focus shall be forced to the beginning of the error message displayed on the page.Â Â Â
I think we only want to force web focus in those two very specific instances. Rex made it clear that industry would have some great concern if we pushed for more than that.