Thread Subject: Re: note for focus cursor

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: Sean Hayes
Date: Wed, Sep 12 2007 6:10 PM

Peter, I don't disagree, and I think part one of my proposed wording captured that.

I think requiring an application to make up for the shortcomings of a platform is not realistic. Providing recognition for those that do is more subtle, and I wouldn't necessarily be against that, however if 508 requires platforms to do this, and is effective then there should be no need.

If an application deliberately sets out for whatever reason to deviate from a platform that in the ordinary case conforms, then yes it ought to take responsibility itself.

Also I think Gregg's wording suffers from some flaws as follows:

- I provide an application, whose 'mode of support' is to use an optional $5000 widget library from example.com, however without this 'mode', (which the agency forgets to purchase) it does not support the platforms built in mechanism. This passes.

- Or we might have the situation where the platform's 'mode of support' is to only install applications that conform, but then the agency installs applications whose 'mode of support' is to rely on the platform. This also passes.


Maybe:
"Platform software must provide at least one mode that
provides a highly visual indication of which user interface
object currently has the keyboard focus. Application software
that has a keyboard operable user interface must respect high
visibility focus settings provided by the platform."

Sean Hayes
Incubation Lab
Accessibility Business Unit
Microsoft

Office: +44 118 909 5867,
Mobile: +44 7875 091385

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University