Thread Subject: Re: Proposal 21(b) Focus
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: Fratkin, Mike
Date: Thu, Nov 16 2006 5:40 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Fratkin, Mike: "Re: Proposal 21(b) Focus"
- Previous message in thread: Jonathan Avila: "Re: Proposal 21(b) Focus"
- Messages sorted by: Author | Thread | Date
A agree with Jonathan that a focus requirement has to be included into
the web information and application provision. This has been an
on-going issue with web applications and should be addressed at this
time. The need for web based material to properly identify focusable
material to the browser is necessary as well as forcing focus to enable
keyboard users to have focus established in application logical
positions. This will help to enable comparable access with mouse users.
Mike Fratkin
Social Security Administration
[Jonathan wrote]I have to disagree on this. I believe web standard
should cover focus. Web applications can provide visual focus and may
need to provide programmatic focus. For example, I can make a simulated
menu with div tags. I can make the menu keyboard accessible by using
JavaScript events such as watching for key presses. However, there is
no way for a browser to know that the div tags should be focusable and
it can't be held responsible for providing visual focus. In this case
the web application should be responsible for exposing the visual focus
such as a highlight and for telling the browser to expose programmatic
focus. At the very least we need a standard requiring web based
material to properly identify focusable material to the browser.
However, I think this would allow a loop-hole for inaccessible web
content.
If the WAI roadmap was actually implemented by all browsers and there
was a way for simulated controls to tell browsers to expose and show
focus this wouldn't be an issue. However, we must consider that we may
need to deal with older technology where something like this is
currently not possible.
In addition, I think any focus standard should cover focus being
forcibly shifted without user knowledge.
Jonathan
- Next message in Thread: Fratkin, Mike: "Re: Proposal 21(b) Focus"
- Previous message in Thread: Jonathan Avila: "Re: Proposal 21(b) Focus"
WebAIM is an initiative of:
