Outdated Content!

The Protocols and Formats Working Group is no longer chartered to operate. Its work will continue in two new Working Groups:

  • https://www.w3.org/WAI/APA/ Accessible Platform Architectures, to review specifications, develop technical support materials, collaborate with other Working Groups on technology accessibility, and coordinate harmonized accessibility strategies within W3C; and
  • https://www.w3.org/WAI/ARIA/ Accessible Rich Internet Applications, to continue development of the Accessible Rich Internet Applications (WAI-ARIA) suite of technologies and other technical specifications when needed to bridge known gaps.

Resources from the PFWG remain available to support long-term institutional memory, but this information is of historical value only.

This Wiki page was edited by participants of the Protocols and Formats Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

WTAG/Meet User Needs

From Protocols and Formats Working Group Wiki
Jump to: navigation, search


This is a preliminary draft to document how user needs are met in various ways. For each user need, ways to meet it are proposed for:

  • Technologies
  • Content Authors
  • User Agents

Other categories may be included later. Many user needs can be met in more than one way. The mechanism to meet user needs in one of the above areas may require support from one or more of the other areas.

This version of the resource is primarily to show the structure, not yet a comprehensive documentation of how user needs can be met.

User Need Technology Content Author User Agent
Text Alternatives
  • Provide a mechanism for author to create text alternatives and associate with content
  • Define parseable and semantically rich content encoding that supports automated creation of text alternatives
  • Create text alternative content and associate with primary content using features of the content technology
  • Encode content using a content technology that is sufficiently rich that machines can create useful automated text alternatives
  • Expose text alternatives provided by the author
  • Create automated text alternative content based on the semantics of the primary content
Color Contrast
  • Provide color definition features that allow authors to set colors to meet requirements
  • Provide color definition features that allow users to override author-set colors
  • Provide color definition semantics that allow colors of common object types to be globally remapped easily
  • Use only colors that meet luminosity contrast guidelines
  • Provide a feature to allow users to request "high contrast" mode
  • Provide a feature to allow users to define their own color preferences
  • Use semantically defined color mappings to allow user global preferences to be easily applied
  • Provide a "high contrast" mode that overrides author colors
  • Provide a feature for users to override author colors
  • Support semantically defined color mappings to allow users to define global preferences that are easily applied across a range of content
Retrieved from "https://www.w3.org/WAI/PF/wiki/index.php?title=WTAG/Meet_User_Needs&oldid=995"