Edit comment LC-1208 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1062 Next: LC-836

Comment LC-1208: Comment Shortname:; Commenter: Al Gilman <Alfred.S.Gilman@IEEE.org>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
equivalent facilitation does not only apply to future technologies, or only to technologies outside your baseline.
This is a principle that applies across the board.

Compare with comments on "one strike and you're out" roll-up in the comments on the conformance scheme.

Proposed Change:

re-write the document and conformance scheme so that it is obvious that the remedy for a potential problem may come at a different level of aggregation from where the potential problem was noticed.

For example, a CAPTCHA in the login process may be worked around by a totally different login process. In other words the failure of access is local to the image but the affordance of accommodation or relief is through equivalence at the task, not the image, level.

For another example, a diagram in SVG may afford the user a navigable structure of focusable elements. If these represent the notional objects in the scene, and they are suitably titled and otherwise annotated with properties and relationships, the text equvalent for the image may be provided at a lower level of aggregation by providing text associated with the parts of the image.

So the relief may be at a higher or lower level of aggregation from the perception of a possible problem (recognition of a match to the selector or applicability-condition I would call the "left-hand-side" of a rule e.g. success criterion).; Related issues: (space separated ids); WG Notes: [TEAMB] [] Discussed in the 01 February 2007 telecon: resolution: accept as amended http://www.w3.org/WAI/GL/2007/02/01-wai-wcag-minutes.html Response: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0108.html; Resolution: Currently there is no requirement that the work-around be at the same level of aggregation on a web page, as long as it is on the same page (see definition of web page) so equivalent facilitation is permissible at a different layer of aggregation (as long as it is at the same URI). For instance, in the case of the CAPTCHA example you gave, the different login process would conform as long as it could be reached from where the CAPTCHA is situated.; (Please make sure the resolution is adapted for public consumption)