Edit comment LC-2688 for Accessibility Guidelines Working Group

Quick access to LC-2651 LC-2652 LC-2653 LC-2654 LC-2655 LC-2656 LC-2657 LC-2658 LC-2659 LC-2660 LC-2661 LC-2662 LC-2663 LC-2664 LC-2665 LC-2666 LC-2667 LC-2668 LC-2669 LC-2670 LC-2671 LC-2672 LC-2673 LC-2674 LC-2675 LC-2676 LC-2677 LC-2678 LC-2679 LC-2680 LC-2681 LC-2682 LC-2686 LC-2687 LC-2688 LC-2689 LC-2690 LC-2691 LC-2692 LC-2693 LC-2694 LC-2695 LC-2698 LC-2700 LC-2701 LC-2702 LC-2817 LC-2818

Comment LC-2688

Comment Shortname:

Commenter: Alex Li <alli@microsoft.com> on behalf of Microsoft

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeAbstract This document, "Applying WCAG 2.0 to non-Web Infor... 1. Introduction This draft document provides informative gu... Document Overview The organization of this document paralle... Understanding Key Terms There are several terms used throug... 2. Comments by Guideline and Success Criterion The sections... Principle 1: Perceivable Information and user interface co... Guideline 1.1: Text Alternatives From Guideline 1.1: Provi... Success Criterion 1.1.1: Non-text Content (Level A) From Su... Specific Benefits of Success Criterion 1.1.1 This Success... Guideline 1.2: Time-based Media From Guideline 1.2: Provid... Success Criterion 1.2.1: Audio-only and Video-only (Prereco... Success Criterion 1.2.2: Captions (Prerecorded) (Level A) F... Success Criterion 1.2.3: Audio Description or Media Alterna... Success Criterion 1.2.4: Captions (Live) (Level AA) From S... Success Criterion 1.2.5: Audio Description (Prerecorded) (L... Success Criterion 1.2.6: Sign Language (Prerecorded) (Level... Success Criterion 1.2.7: Extended Audio Description (Prerec... Success Criterion 1.2.8: Media Alternative (Prerecorded) (L... Success Criterion 1.2.9: Audio-only (Live) (Level AAA) From... Guideline 1.3: Adaptable From Guideline 1.3: Create conte... Success Criterion 1.3.1: Info and Relationships (Level A) F... Success Criterion 1.3.2: Meaningful Sequence (Level A) From... Success Criterion 1.3.3: Sensory Characteristics (Level A)... Guideline 1.4: Distinguishable From Guideline 1.4: Make i... Success Criterion 1.4.1: Use of Color (Level A) From Succe... Success Criterion 1.4.2: Audio Control (Level A) From Succ... Success Criterion 1.4.3: Contrast (Minimum) (Level AA) From... Success Criterion 1.4.4: Resize text (Level AA) From Succe... Success Criterion 1.4.5: Images of Text (Level AA) From Su... Success Criterion 1.4.6: Contrast (Enhanced) (Level AAA) Fr... Success Criterion 1.4.7: Low or No Background Audio (Level... Success Criterion 1.4.8: Visual Presentation (Level AAA) Fr... Success Criterion 1.4.9: Images of Text (No Exception) (Lev... Principle 2: Operable User interface components and naviga... Guideline 2.1: Keyboard Accessible From Guideline 2.1: Ma... Success Criterion 2.1.1: Keyboard (Level A) From Success C... Success Criterion 2.1.2: No Keyboard Trap (Level A) From S... Success Criterion 2.1.3: Keyboard (No Exception) (Level AAA... Guideline 2.2: Enough Time From Guideline 2.2: Provide use... Success Criterion 2.2.1: Timing Adjustable (Level A) From... Success Criterion 2.2.2: Pause, Stop, Hide (Level A) From S... Success Criterion 2.2.3: No Timing (Level AAA) From Succes... Success Criterion 2.2.4: Interruptions (Level AAA) From Su... Success Criterion 2.2.5: Re-authenticating (Level AAA) From... Guideline 2.3: Seizures From Guideline 2.3: Do not design... Success Criterion 2.3.1: Three Flashes or Below Threshold (... Success Criterion 2.3.2: Three Flashes (Level AAA) From Su... Guideline 2.4: Navigable From Guideline 2.4: Provide ways... Success Criterion 2.4.1: Bypass Blocks (Level A) From Succ... Success Criterion 2.4.2: Page Titled (Level A) From Succes... Success Criterion 2.4.3: Focus Order (Level A) From Succes... Success Criterion 2.4.4: Link Purpose (In Context) (Level A... Success Criterion 2.4.5: Multiple Ways (Level AA) From Suc... Success Criterion 2.4.6: Headings and Labels (Level AA) Fro... Success Criterion 2.4.7: Focus Visible (Level AA) From Suc... Success Criterion 2.4.8: Location (Level AAA) From Success... Success Criterion 2.4.9: Link Purpose (Link Only) (Level AA... Success Criterion 2.4.10: Section Headings (Level AAA) From... Principle 3: Understandable Information and the operation... Guideline 3.1: Readable From Guideline 3.1: Make text cont... Success Criterion 3.1.1: Language of Page (Level A) From S... Success Criterion 3.1.2: Language of Parts (Level AA) From... Success Criterion 3.1.3: Unusual Words (Level AAA) From Suc... Success Criterion 3.1.4: Abbreviations (Level AAA) From Suc... Success Criterion 3.1.5: Reading Level (Level AAA) From Su... Success Criterion 3.1.6: Pronunciation (Level AAA) From Su... Guideline 3.2: Predictable From Guideline 3.2: Make Web p... Success Criterion 3.2.1: On Focus (Level A) From Success C... Success Criterion 3.2.2: On Input (Level A) From Success C... Success Criterion 3.2.3: Consistent Navigation (Level AA) F... Success Criterion 3.2.4: Consistent Identification (Level A... Success Criterion 3.2.5: Change on Request (Level AAA) From... Guideline 3.3: Input Assistance From Guideline 3.3: Help u... Success Criterion 3.3.1: Error Identification (Level A) Fro... Success Criterion 3.3.2: Labels or Instructions (Level A) F... Success Criterion 3.3.3: Error Suggestion (Level AA) From... Success Criterion 3.3.4: Error Prevention (Legal, Financial... Success Criterion 3.3.5: Help (Level AAA) From Success Cri... Success Criterion 3.3.6: Error Prevention (All) (Level AAA)... Principle 4: Robust Content must be robust enough that it... Guideline 4.1: Compatible From Guideline 4.1: Maximize com... Success Criterion 4.1.1: Parsing (Level A) From Success Cr... Success Criterion 4.1.2: Name, Role, Value (Level A) From S... 3. Comments on Conformance The WCAG2ICT Task Force has not... 4. Comments on Definitions in WCAG 2.0 Glossary in Appendix... B. References No references documented yet.
or

Refinement of the section concerned:

Status:

open proposal pending resolved_yes resolved_no resolved_partial other assigned to Nobody Abma, Jake Abou-Zahra, Shadi Allan, Jim Auclair, Christopher Avila, Jonathan Babinszki, Tom Bailey, Bruce Bernard, Renaldo Bernier, Alex Blake, Matthew Boudreau, Denis Brewer, Judy Butler, Shari Campbell, Alastair Carlson, Laura Chakravarthula, Srinivasu Cirrincione, Pietro Conway, Vivienne Cooper, Michael Crutchfield, Elizabeth Deltour, Romain Dick, Wayne Ding, Chaohai Dirks, Kim Dixit, Shwetank Draffan, E.A. Duggin, Alistair Eggert, Eric Elledge, Michael Faulkner, Steve Ferraz, Reinaldo Fiers, Wilco Fischer, Detlev Foliot, John Garrish, Matt Garrison, Alistair Gower, Michael Guarino Reid, Loretta Hakkinen, Markku Haritos-Shea, Katie Henry, Shawn Hoffmann, Thomas Horton, Sarah Isager, Kasper Jensen, Tobias Christian Johansson, Stefan Johlic, Marc Johnson, Rick Jones, Crystal Joys Andersen, Wilhelm Kapoor, Shilpi Keim, Oliver Kirkpatrick, Andrew Kirkwood, John Kiss, Jason Kraft, Maureen Ku, JaEun Kurapati, Sujasree Lauke, Patrick Lauriat, Shawn Lee, Steve Lemon, Gez Li, Alex Li, Kepeng Li, Liangcheng Loiselle, Chris Lowney, Greg Lui, Edwina Lund, Adam Ma, Jia MacDonald, David Mace, Amanda Manser, Erich Martin, Debra McCormack, Scott McMeeking, Chris McSorley, Jan Milliken, Neil Montgomery, Rachael Mueller, Mary Jo nicole, windmann Niemann, Gundula Nurthen, James O Connor, Joshue Oh, Jeong-Hun Panchang, Sailesh Pandhi, Charu Pasi, Aparna Patch, Kimberly Philipp, Melanie Pluke, Mike Pouncey, Ian Repsher, Stephen Rochford, John Runyan, Marla Savva, Andreas Sawczyn, Steve Schnabel, Stefan Seeman-Kestenbaum, Lisa Sims, Glenda Singh, Avneesh Skotkjerra, Stein Erik Sloan, David Smith, Alan Smith, Jim Solomon, Adam Spellman, Jeanne F Strobbe, Christophe Suprock, Greg Swallow, David Thompson, Kenneth Thyme, Anne Ueki, Makoto Vaishnav, Jatin Vanderheiden, Gregg Venkata, Manoj Wahlbin, Kathleen Wang, Can WANG, WEI White, Jason Zelmanowicz, Erica Zerner, Adam Zhang, Mengni

Type: substantive editorial typo question general comment undefined

Comment:

WCAG 2.0 conformance requirements may be in conflict with other standards' conformance requirements
Due to the inherently incomplete nature of WCAG in the context of non-web ICT, it cannot be used in isolation as a standard of its own for non-web ICT. Since other standards contain conformance requirements in conflict with that of WCAG 2.0. Section 508, for example, contains the best meet provision which conflicts with WCAG 2.0 conformance requirements number 1, 2, and 3. We advise WCAG2ICT TF to recognize that such conflicts can be highly counterproductive and that the audience must take caution in applying WCAG 2.0 conformance requirements to other standard development effort and that it may be more suitable to use the relevant success criteria and not the conformance requirements.

Related issues: (space separated ids)

WG Notes:

Proposed Resolution: We have not yet developed additional guidance on conformance. We plan to work on this topic soon and will consider these comments at that time. We are sending responses to all comments received from you in order to close out issues on this older draft and incorporate edits into the next draft. At this time we have not completed discussion of the conformance issues you raise. We intend to consider your comments during this process, and invite you to review this issue and submit additional comments if needed in the next draft. @@@ send but don't close comment

(Please make sure the resolution is adapted for public consumption)