I reviewed
and for
inclusion in the document in the Conformance section.

The information about "recognized" must be in a normative section. The
introduction is not normative. we could write a paragraph explaining
'recognized' in the introduction just explaining the concept. Putting
something like Jan's proposal or Eric's rewrite (or a combination) in the
conformance claim section makes 'recognized' normative.

Proposal placement in the conformance section.

In order to conform the following requirements must be met:

1. Unrecognizable content: Any success criteria that refer to semantic
features of web content  (e.g., text alternatives to non-text content,
headings, keyboard commands, time limits, etc.) will only apply when those
features are implemented according to standard semantics for the web
content technology. When those features are implemented via other means
(e.g., custom scripting, plugin, applet, etc.), the content features are
not considered recognizable and the success criteria do not apply.

2. User agent  systems: As per the UAAG 2.0 definition of user agent,
several software tools (identified in any conformance claim) can be used in
conjunction to meet the requirements. For example, a base user agent could
make use of plug-in to provide certain functionality and a web-based user
agent may rely on base user agent features (e.g., keyboard navigation, find
functions, etc.).

3. Developer control: The success criteria only apply to the user agent
user interface as it is provided by the developer. They do not apply to any
subsequent modifications by parties other than the developer (e.g., user
modifications of default settings, third-party plug-ins).

Proposal: placement in the introduction

User agents are a collection of technologies, some are native to the user
agent and some are hosted by the user agent (e.g. examples). Technologies
native to the user agent communicate directly with accessibility
application programming interfaces. These native technologies are called
‘recognized’ methods of rendering content and interaction controls.
Technologies that are not native, that is their processes are invisible to
the user agent. Hence, they are unrecognized by the user agent and are not
communicated to accessibility application programming interfaces.

Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264
"We shape our tools and thereafter our tools shape us." McLuhan, 1964

Received on Thursday, 29 August 2013 23:26:26 UTC