Edit comment LC-1307 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1273 Next: LC-648

Comment LC-1307: Comment Shortname:; Commenter: Charles McCathieNevile <chaals@opera.com>; 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:
Structural/substantive issue

The specification seems to take no account of situations where in fact all
user agents relevant to a given baseline offer functionality that the
guidelines are requiring of authors.

Where this is the case (for example, SVG user agents generally provide a
mechanism to pause any animation independently of the content, and in SVG
tiny it is not possible to provide the functionality in content anyway)
the guidelines should take it into account.

I propose that the baseline section be reworked, to incorporate this type
of situation. Perhaps the most robust way of specifying this would be to
explicitly relate UAAG requirements to WCAG requirements, and note that
where there are (some expression for most or all) user agents for the
baseline which meet a given UAAG requirement the corresponding WCAG
requirement need not be met. Note that the proportion of user agents for
which this needs to be true should be at least as high, and probably
higher than that which is reasonable to justify the use of a particular
baseline in the first place.; Related issues: (space separated ids); WG Notes: [TEAMA] [] [AL] Propose to reject with comment that if there is no user agent that would allow the content to meet a specific success criterion, then the content would not be able to meet the corresponding compliance level. For example, nobody can claim to meet 2.2.3 unless there is a way to pause the content unless the activity is timing and movement essential. UAAG compliance is not necessary. Discussed in the 05 April 2007 telecon: Resolution: LC-1307 closed as proposed http://www.w3.org/WAI/GL/2007/04/05-wai-wcag-minutes.html {not-accept}; Resolution: WCAG success criteria have been written to describe the functionality that must be available, but have avoided specifying that the functionality must be provided by the user agent or by the content directly. For example, SC 2.4.1 (A mechanism is available to bypass blocks of content that are repeated on multiple Web pages) can be satisfied by providing links in the content to bypass the blocks, or by providing headings at the beginning of each section and relying on the user agent to skip the repeated content by skipping to headings.; (Please make sure the resolution is adapted for public consumption)