Thread Subject: Section 31A - May 30 Draft
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: Tom Brett
Date: Sat, Jun 02 2007 3:55 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Peter Korn: "Re: Section 31A - May 30 Draft"
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
The following provision was copied from the WIKI:
Applications shall not disrupt or disable activated features of other
products that are identified as accessibility features, where those features
are developed and documented according to industry standards. Applications
also shall not disrupt or disable activated features of any operating system
that are identified as accessibility features where the application
programming interface for those accessibility features has been documented
by the manufacturer of the operating system and is available to the product
Does the first sentence of this provision mean that I cannot develop an
application that disables a key combination unique to Jaws, such as CNTL +
ALT + RIGHT ARROW? Are assistive technology software applications
considered to be an industry standard even though these AT applications are
not considered by most developers to be mainstream?
I have talked to developers who feel that they can assign a function to any
key combination as long as it does not override a windows documented
accessibility feature. If they choose to use the CNTL + ALT + RIGHT ARROW
they have removed my ability to read table data.
What is the intent of this provision?
- Next message in Thread: Peter Korn: "Re: Section 31A - May 30 Draft"
- Previous message in Thread: None