Edit comment LC-2454 for Accessibility Guidelines Working Group

Quick access to LC-2429 LC-2453 LC-2454 LC-2455 LC-2461 LC-2462 LC-2463 LC-2468 LC-2470 LC-2472 LC-2473 LC-2474 LC-2477 LC-2478 LC-2479 LC-2480 LC-2495 LC-2497 LC-2498 LC-2499 LC-2501

Comment LC-2454

Comment Shortname:

Commenter: Sailesh Panchang <spanchang02@yahoo.com>

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeIntroduction to Understanding WCAG 2.0 Understanding the Four Principles of Accessibility Layers of Guidance The Guidelines Success Criteria Sufficient and Advisory Techniques Text Alternatives: Understanding Guideline 1.1 Intent of Guideline 1.1 Non-text Content: Understanding SC 1.1.1 Time-based Media: Understanding Guideline 1.2 Audio-only and Video-only (Prerecorded): Understanding SC 1.2.1 Captions (Prerecorded): Understanding SC 1.2.2 Audio Description or Media Alternative (Prerecorded): Understanding SC 1.2.3 Captions (Live): Understanding SC 1.2.4 Audio Description (Prerecorded): Understanding SC 1.2.5 Sign Language (Prerecorded): Understanding SC 1.2.6 Extended Audio Description (Prerecorded): Understanding SC 1.2.7 Media Alternative (Prerecorded): Understanding SC 1.2.8 Audio-only (Live): Understanding SC 1.2.9 Adaptable: Understanding Guideline 1.3 Info and Relationships: Understanding SC 1.3.1 Meaningful Sequence: Understanding SC 1.3.2 Sensory Characteristics: Understanding SC 1.3.3 Distinguishable: Understanding Guideline 1.4 Use of Color: Understanding SC 1.4.1 Audio Control: Understanding SC 1.4.2 Contrast (Minimum): Understanding SC 1.4.3 Resize text: Understanding SC 1.4.4 Images of Text: Understanding SC 1.4.5 Contrast (Enhanced): Understanding SC 1.4.6 Low or No Background Audio: Understanding SC 1.4.7 Visual Presentation: Understanding SC 1.4.8 Images of Text (No Exception): Understanding SC 1.4.9 Keyboard Accessible: Understanding Guideline 2.1 No Keyboard Trap: Understanding SC 2.1.2 Keyboard (No Exception): Understanding SC 2.1.3 Enough Time: Understanding Guideline 2.2 Timing Adjustable: Understanding SC 2.2.1 Pause, Stop, Hide: Understanding SC 2.2.2 No Timing: Understanding SC 2.2.3 Interruptions: Understanding SC 2.2.4 Re-authenticating: Understanding SC 2.2.5 Seizures: Understanding Guideline 2.3 Three Flashes or Below Threshold: Understanding SC 2.3.1 Three Flashes: Understanding SC 2.3.2 Navigable: Understanding Guideline 2.4 Bypass Blocks: Understanding SC 2.4.1 Page Titled: Understanding SC 2.4.2 Focus Order: Understanding SC 2.4.3 Link Purpose (In Context): Understanding SC 2.4.4 Multiple Ways: Understanding SC 2.4.5 Headings and Labels: Understanding SC 2.4.6 Focus Visible: Understanding SC 2.4.7 Location: Understanding SC 2.4.8 Link Purpose (Link Only): Understanding SC 2.4.9 Section Headings: Understanding SC 2.4.10 Readable: Understanding Guideline 3.1 Language of Page: Understanding SC 3.1.1 Language of Parts: Understanding SC 3.1.2 Unusual Words: Understanding SC 3.1.3 Abbreviations: Understanding SC 3.1.4 Reading Level: Understanding SC 3.1.5 Pronunciation: Understanding SC 3.1.6 Predictable: Understanding Guideline 3.2 On Focus: Understanding SC 3.2.1 On Input: Understanding SC 3.2.2 Consistent Navigation: Understanding SC 3.2.3 Consistent Identification: Understanding SC 3.2.4 Change on Request: Understanding SC 3.2.5 Input Assistance: Understanding Guideline 3.3 Error Identification: Understanding SC 3.3.1 Labels or Instructions: Understanding SC 3.3.2 Error Suggestion: Understanding SC 3.3.3 Error Prevention (Legal, Financial, Data): Understanding SC 3.3.4 Help: Understanding SC 3.3.5 Error Prevention (All): Understanding SC 3.3.6 Compatible: Understanding Guideline 4.1 Parsing: Understanding SC 4.1.1 Name, Role, Value: Understanding SC 4.1.2 Understanding Conformance Understanding Conformance Requirements Understanding Requirement 1 Understanding Requirement 2 Understanding Requirement 3 Understanding Requirement 4 Understanding Requirement 5 Understanding Conformance Claims Understanding Levels of Conformance Understanding Accessibility Support Understanding "Programmatically Determined" Understanding Conforming Alternate Versions Understanding "Web Page" Understanding "Text Alternatives" Appendix A How to refer to WCAG 2.0 from other documents Appendix B Documenting Accessibility Support for Uses of a Web Technology Appendix C Understanding Metadata Appendix D References
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

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:

SC 4.1.1 requires limited validity checks for markup: unique ID values, proper tag nesting and closing and a check for duplicate attributes.

However, the WCAG 2 Understanding documentat suggests that conformance claim could include something along the lines of:
"The documented set of accessibility-supported content technologies relied upon for this claim includes XHTML 1.0 (Transitional), CSS 2 and JavaScript 1.2. "
Refer: example conformance claims on http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-conformance-requirements-head
Does this imply that one can make such a statement only after ensuring that markup / CSS / JS code is valid?
Please clarify whether validating the code for CSS / JS / XHTML beyond what is suggested in SC 4.1.1 is required for a conformance claim if for instance, all three technologies are used.

Related issues: (space separated ids)

WG Notes:

Resolution: No, this just says that you depend on those technologies in making your claim. That just tells the user that if they use a browser that doesn’t support JS or CSS the page might not be accessible. In the spirit of success criterion 4.1.1, any modifications made to the DOM should also preserve these same properties, e.g., elements properly nested, no duplicate IDs, etc.

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