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.

Break Content out from Device Provisions?

Contents

ISSUE: Break Content out from Device Provisions

Description of issue

Currently Content is treated like a characteristic. But the WebSoft group is finding that content needs to be handled separately and is developing the provisions for content separately. Our structure doesn't treat content well either way. Also you don't really have the ability to provide direct access to content for many disabilities. Since content doesnt have a physical form, content would often require AT for many disabilities.

NOTES

three types of products around content

  • tools that create content
  • tools the present the content (players, browsers)
  • content itself


Break this issue into three parts

  1. physical devices
  2. software players
  3. Content


Content here refers to content that is and E&IT product. Paper documents would not be an E&IT product though E&IT products may include paper docs - they are not what we are referring to here as content.

Proposed solution

Make Content a separate category like Documentation. It could then be clear those provisions only apply there (unless cited elsewhere).

Resolution 4/2/07

Move content to a new section.

  • different groups create content and the tools to view it.
  • these are not two characteristics of the same product (like hardware, software, telecom etc can be)


Explore ways to separate Software and Hardware issues where they differ

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