Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional and up-to-date details on the updates to section 508 and section 255 can be found at the Access Board web site.

Web and Software: February 7

Contents

Miscellaneous

API Requirements Proposal

Summary of mailing list discussion

  • Question about editable table cells already addressed by Peter
  • The proposal intentionally does not define a minimum set of roles. What should happen if new roles are created such as would be the case with a custom control in Java?
    • Some accessibility APIs, such as Java and UNIX, have a predefined set of roles that AT understands but the decisions about what these are should be left to the designers of the API.
    • Developers who create new roles, aka custom controls, should coordinate with AT vendors to support the new controls.

Summary of meeting discussion

  • AT community involvement - none yet but ATIA and vendors plan to review it.
  • Although the proposal is structured differently than the ISO 8.6 section, the requirements in the proposal are harmonized with those in ISO. ISO grouped the interoperability requirements together in a section because closed products don't need to meet these requirements.
  • Issues raised:
    • An accessibility API is an example of an accessibility service but there could be other methods.
    • Is the boundary requirement necessary on a character basis? ISO doesn't require this but some ATs need it in order to highlight or underline characters.
    • IT should not decide what the AT should do. Underlining is a bad idea for low vision.
    • AT vendors are generally in favor of APIs but not sure it should be required in 508.
    • Even when both IT and AT support the same API, customization is often still required.
    • Concern for the burden this places on small platforms such as those designed for mobile devices. The proposal is targeted at desktop platforms. Could be used to derive something for mobile.

Conclusion:

  • Favor an approach that encourages the use of APIs but also allows other methods to be used to achieve interoperability with AT.
  • Don't want to get too specific in 508 but encourage IT and AT vendors to keep adding to supplementary guidance material.
  • Sub-subcommittee, including AT vendors, is continuing to refine the proposal

Cognitive Presentation

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