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: Andi Snow-Weaver
Date: Wed, Sep 19 2007 8:30 AM

Norm,

Programmatic exposure of the focus is clearly required in the AT
Interoperability provision. [1]

We could add a note recommending linking the two but I don't see that it is
necessary and it's adds length to something that is already being
criticized for being too long.

[1] http://teitac.org/wiki/EWG:Draft_Sept_14#3-U_-_AT_Interoperability

Andi




"Robinson, Norman
B - Washington,
DC" To
<Norman.B.Robinso "TEITAC Web/Software Subcommittee"
= EMAIL ADDRESS REMOVED = > < = EMAIL ADDRESS REMOVED =
Sent by: >
teitac-websoftwar cc
= EMAIL ADDRESS REMOVED =
itac.org Subject
Re: [teitac-websoftware] note for
focus cursor
09/19/2007 08:07
AM


Please respond to
TEITAC
Web/Software
Subcommittee
<teitac-websoftwa
= EMAIL ADDRESS REMOVED =
g>






Andi,

What about the link to the API/programmed interface/OS
accessibility layer? I'm think the below works for functions but won't
necessarily work when talking about assistive technologies (e.g., MAGic
auto focuses on the system event and drives the magnified focus to the
object based on MSAA/window widget events).

1. It isn't "the user interface" of the program that is
providing this, it is my assistive technology.
2. I can create a program that meets the below wording, yet
doesn't use the accessibility API on my OS/platform and that would be
very bad for use of assistive technologies.

Regards,


Norman B. Robinson
Section 508 Coordinator
IT Governance, US Postal Service
phone: 202.268.8246

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