Edit comment LC-894 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1032 Next: LC-1209

Comment LC-894: Comment Shortname:; Commenter: Susan Lesch <lesch@w3.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:
Congratulations on your Last Call.

One comment that you may have received from others: If the
principles [1] were maintained outside the guidelines [2], then
the guidelines might be easier to find and comprehend. The
guidelines would then have thirteen whole numbers.

Maybe [1] could say which guidelines developed from which
principle. Below is just a text outline. I wonder if the spec
adheres to its subject -- the guidelines -- if implementers may
find the guidelines easier to follow over time.

Hope this helps.

For [1]:
========

* Principle 1: Content must be perceivable (Guidelines 1-4).

* Principle 2: Interface components in the content must be
operable (Guidelines 5-9).

* Principle 3: Content and controls must be understandable
(Guidelines 10-11).

* Principle 4: Content should be robust enough to work with
current and future user agents (including
assistive technologies) (Guidelines 12-13).

For [2]:
========

* Guideline 1: Provide text alternatives for all non-text content.

* Guideline 2: Provide synchronized alternatives for multimedia.

* Guideline 3: Ensure that information and structure can be
separated from presentation.

* Guideline 4: Make it easy to distinguish foreground information
from its background.

* Guideline 5: Make all functionality operable via a keyboard
interface.

* Guideline 6: Allow users to control time limits on their reading
or interaction.

* Guideline 7: Allow users to avoid content that could cause
seizures due to photosensitivity.

* Guideline 8: Provide mechanisms to help users find content, orient
themselves within it, and navigate through it.

* Guideline 9: Help users avoid mistakes and make it easy to correct
mistakes that do occur.

* Guideline 10: Make text content readable and understandable.

* Guideline 11: Make the placement and functionality of content
predictable.

* Guideline 12: Support compatibility with current and future user
agents (including assistive technologies).

* Guideline 13: Ensure that content is accessible or provide an
accessible alternative.

[1]
http://www.w3.org/TR/2006/WD-WCAG20-20060427/intro.html#overview-design-principles
[2] http://www.w3.org/TR/2006/WD-WCAG20-20060427/guidelines.html

Best wishes for your project.; Related issues: (space separated ids); WG Notes: [EDITORZ] Discussed in the 24 August 2006 telecon: Unanimous Consent: Editors: LC-815, LC-894&LC-1000, LC-973, LC-1060 Team B: LC-609, LC-777, LC-778, LC-915, LC-984, LC-1012, LC-1127, LC-1131 Team C: LC-787 http://www.w3.org/WAI/GL/2006/08/24-wai-wcag-minutes.html Response from commenter: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007May/0124.html; Resolution: The working group considered making this change to the numbering scheme. However, we felt that it is important to have a different numbering scheme between WCAG 1.0 and WCAG 2.0 since both sets of guidelines are likely to be in use in various contexts at the same time.; (Please make sure the resolution is adapted for public consumption)