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: Content Format Proposal


What capacities define a format that can meet the technical and functional standards? The format must provide the capacities to mark up the information to be interpreted by AT or user-agent to AT.

Proposal: Add a new section to 508 (1194.27?)

  1. When a content format supports non-text objects, an encoding mechanism shall be provided to associate non-text objects with textual descriptions displayable by a user-agent.
  2. When a content format supports multimedia, an encoding mechanism shall be provided to include synchronized text of verbal content, and audio descriptions of critical nonverbal activity displayable by a user-agent.
  3. When a content format supports color, an encoding mechanism shall be provided to identify all colors selected for text, both foreground and background displayable by a user-agent. Peter Korn: Allen Hoffman & I believe this provision is not needed; it is redundant
  4. When a content format supports 2 dimensional display of information, an encoding mechanism shall be provided to identify the logical linear reading order of the content displayable by a user-agent. Peter Korn: proposes that this provision changes to: "When a content format contains text and/or multiple graphics, an encoding mechanism shall be provided to indicate the logical linear reading order of that text and/or graphics." Peter Korn: after mailing list discussions with Sean, Loretta, Sailesh, and I, the final proposal for ths text (as of April 18, 2007) is: "A content format shall provide an encoding mechanism to indicate a logical linear reading order of all content contained within it."
  5. When a content format supports data tables, an encoding mechanism shall be provided to identify row and column headers for data tables displayable by a user-agent.
  6. When a content format supports data tables that have two or more logical levels of row or column headers, an encoding mechanism shall be provided to associate row and column headers with data cells, displayable by a user-agent.
  7. When a content format supports interactive elements, an encoding mechanism shall be provided to identify name, operation, and state, of any interactive elements displayable by a user-agent.
  8. When a content format supports links, an encoding mechanism shall be provided to identify link text displayable by a user-agent.
  9. When a content format supports embedded comments, an encoding mechanism shall be provided to identify embedded comments and associate those comment locations within the document.
  10. When a content format supports scanned images of text, an encoding mechanism shall be provided to identify text of scanned images of text, displayable by a user-agent. Note, this means allowing for inclusion of the text of a scanned image of text.
  11. When a content format supports dynamic presentations, graphs, or other extracted information, an encoding mechanism shall be provided to include data used for any dynamic presentations, graphs, or other extracted information displayable by a user-agent.

Summary of discussion on content encoding scheme proposal

  • Need to propose lanaguage for keyboard input that is sufficient to describe the requirement for the encoding format and include non-input device specific functionality for any user-interaction elements encodable?
    • Example:When an encoding scheme includes the capacity to present elements for user-interaction, a device independent interaction method shall be available which allows interactive elements to be used via a keyboard or other interface.
  • Recommendation to change the keyboard navigation/manipulation of content via language that starts with content encoding schemes and start the sentence/paragraph by talking about content viewers & content editors/creators. Perhaps a sentence that points back to the general software guidelines.
    • the process of content viewing/editing must meet all of the other software guidelines
    • must reflect color/contrast settings of desktop, must be 100% keyboard operable, etc.

Other provisions to be considered for the content encoding scheme proposal

  1. Encoding mechanism which allow programmatic input and execution of end-user scripting, shall provide access to the embedded scripts.

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