Edit comment LC-2571 for Accessibility Guidelines Working Group

Quick access to LC-2464 LC-2476 LC-2490 LC-2571 LC-2572 LC-2587 LC-2588 LC-2599 LC-2600 LC-2645 LC-2685 LC-2716 LC-2720 LC-2725 LC-2727 LC-2743 LC-2758 LC-2759 LC-2760 LC-2762 LC-2763 LC-2766 LC-2767 LC-2768 LC-2769 LC-2778 LC-2779 LC-2780 LC-2876 LC-2922 LC-2941 LC-2942 LC-2964 LC-2972

Comment LC-2571

Comment Shortname:

Commenter: Makoto Ueki <makoto.ueki@gmail.com> on behalf of JIS

Message-id:

Section of the document concerned:

[Free text description]Document as a wholeIntroduction WCAG 2.0 Layers of Guidance WCAG 2.0 Supporting Documents Important Terms in WCAG 2.0 WCAG 2.0 Guidelines Principle 1: Perceivable - Information and user interface components must be presentable to users in ways they can perceive. Guideline 1.1 Text Alternatives: Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language. 1.1.1 Non-text Content: All non-text content that is prese... Guideline 1.2 Time-based Media: Provide alternatives for time-based media. 1.2.1 Audio-only and Video-only (Prerecorded): For prereco... 1.2.2 Captions (Prerecorded): Captions are provided for al... 1.2.3 Audio Description or Media Alternative (Prerecorded)... 1.2.4 Captions (Live): Captions are provided for all live... 1.2.5 Audio Description (Prerecorded): Audio description i... 1.2.6 Sign Language (Prerecorded): Sign language interpret... 1.2.7 Extended Audio Description (Prerecorded): Where paus... 1.2.8 Media Alternative (Prerecorded): An alternative for... 1.2.9 Audio-only (Live): An alternative for time-based med... Guideline 1.3 Adaptable: Create content that can be presented in different ways (for example simpler layout) without losing information or structure. 1.3.1 Info and Relationships: Information, structure, and... 1.3.2 Meaningful Sequence: When the sequence in which cont... 1.3.3 Sensory Characteristics: Instructions provided for u... Guideline 1.4 Distinguishable: Make it easier for users to see and hear content including separating foreground from background. 1.4.1 Use of Color: Color is not used as the only visual m... 1.4.2 Audio Control: If any audio on a Web page plays auto... 1.4.3 Contrast (Minimum): The visual presentation of text... 1.4.4 Resize text: Except for captions and images of text,... 1.4.5 Images of Text: If the technologies being used can a... 1.4.6 Contrast (Enhanced): The visual presentation of text... 1.4.7 Low or No Background Audio: For prerecorded audio-on... 1.4.8 Visual Presentation: For the visual presentation of... 1.4.9 Images of Text (No Exception): Images of text are on... Principle 2: Operable - User interface components and navigation must be operable. Guideline 2.1 Keyboard Accessible: Make all functionality available from a keyboard. 2.1.1 Keyboard: All functionality of the content is operab... 2.1.2 No Keyboard Trap: If keyboard focus can be moved to... 2.1.3 Keyboard (No Exception): All functionality of the co... Guideline 2.2 Enough Time: Provide users enough time to read and use content. 2.2.1 Timing Adjustable: For each time limit that is set b... 2.2.2 Pause, Stop, Hide: For moving, blinking, scrolling,... 2.2.3 No Timing: Timing is not an essential part of the ev... 2.2.4 Interruptions: Interruptions can be postponed or sup... 2.2.5 Re-authenticating: When an authenticated session exp... Guideline 2.3 Seizures: Do not design content in a way that is known to cause seizures. 2.3.1 Three Flashes or Below Threshold: Web pages do not c... 2.3.2 Three Flashes: Web pages do not contain anything tha... Guideline 2.4 Navigable: Provide ways to help users navigate, find content, and determine where they are. 2.4.1 Bypass Blocks: A mechanism is available to bypass bl... 2.4.2 Page Titled: Web pages have titles that describe top... 2.4.3 Focus Order: If a Web page can be navigated sequenti... 2.4.4 Link Purpose (In Context): The purpose of each link... 2.4.5 Multiple Ways: More than one way is available to loc... 2.4.6 Headings and Labels: Headings and labels describe to... 2.4.7 Focus Visible: Any keyboard operable user interface... 2.4.8 Location: Information about the user's location with... 2.4.9 Link Purpose (Link Only): A mechanism is available t... 2.4.10 Section Headings: Section headings are used to orga... Principle 3: Understandable - Information and the operation of user interface must be understandable. Guideline 3.1 Readable: Make text content readable and understandable. 3.1.1 Language of Page: The default human language of each... 3.1.2 Language of Parts: The human language of each passag... 3.1.3 Unusual Words: A mechanism is available for identify... 3.1.4 Abbreviations: A mechanism for identifying the expan... 3.1.5 Reading Level: When text requires reading ability mo... 3.1.6 Pronunciation: A mechanism is available for identify... Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways. 3.2.1 On Focus: When any component receives focus, it does... 3.2.2 On Input: Changing the setting of any user interface... 3.2.3 Consistent Navigation: Navigational mechanisms that... 3.2.4 Consistent Identification: Components that have the... 3.2.5 Change on Request: Changes of context are initiated... Guideline 3.3 Input Assistance: Help users avoid and correct mistakes. 3.3.1 Error Identification: If an input error is automatic... 3.3.2 Labels or Instructions: Labels or instructions are p... 3.3.3 Error Suggestion: If an input error is automatically... 3.3.4 Error Prevention (Legal, Financial, Data): For Web p... 3.3.5 Help: Context-sensitive help is available. (Level AA... 3.3.6 Error Prevention (All): For Web pages that require t... Principle 4: Robust - Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies. 4.1.1 Parsing: In content implemented using markup languag... 4.1.2 Name, Role, Value: For all user interface components... Conformance Conformance Requirements 1. Conformance Level: One of the following levels of confor... 2. Full pages: Conformance (and conformance level) is for f... 3. Complete processes: When a Web page is one of a series o... 4. Only Accessibility-Supported Ways of Using Technologies:... 5. Non-Interference: If technologies are used in a way that... Conformance Claims (Optional) Required Components of a Conformance Claim Optional Components of a Conformance Claim Statement of Partial Conformance - Third Party Content Statement of Partial Conformance - Language Appendix A: Glossary abbreviation accessibility supported alternative for time-based media ambiguous to users in general ASCII art assistive technology (as used in this document) audio audio description audio-only blinking blocks of text CAPTCHA captions changes of context conformance conforming alternate version content (Web content) context-sensitive help contrast ratio correct reading sequence emergency essential extended audio description flash functionality general flash and red flash thresholds human language idiom image of text informative input error jargon keyboard interface label large scale (text) legal commitments link purpose live lower secondary education level mechanism media alternative for text name navigated sequentially non-text content normative on a full-screen window paused prerecorded presentation primary education level process programmatically determined (programmatically determinable) programmatically determined link context programmatically set pure decoration real-time event relationships relative luminance relied upon (technologies that are) role same functionality same relative order satisfies a success criterion section set of Web pages sign language sign language interpretation specific sensory experience structure supplemental content synchronized media technology (Web content) text text alternative used in an unusual or restricted way user agent user-controllable user interface component video video-only viewport visually customized Web page Appendix B: Acknowledgments Appendix C: 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:

Touchscreen issues are covered by WCAG 2?

SC 2.1.1 requires the keyboard accessibility. What about a touchscreen interface?

For example, 'onmouseover' and 'onkeypress' don't work on the touchscreens such as iPhone and iPad.

Does WCAG 2 require the touchscreen users to buy and use a keyboard for such devices?

Proposed Change:
Just to make sure if WCAG 2 covers touchscreen issues or not. WAIC need an answer from WCAG WG in order for JIS X 8341-3:2010(our standards) to harmonize with WCAG 2. Thank you very much.

Related issues: (space separated ids)

WG Notes:

Resolution: SC 2.1.1 covers the issues of touchscreen interfaces. By requiring that all functionality be available from the keyboard, WCAG ensures that a page will work and be accessible even if onmouseover etc does not work. Everything that onmouseover accomplished would also be available through "onfocus" or some other keyboard accessible technique. Since all of the touchscreen devices known to the Working Group, including Android and iOS, also allow connection of a keyboard (wired, Bluetooth or other) such a keyboard (or AT acting as a keyboard) could be used to access the web page through that client. If a person found a device that didn’t support a keyboard, they should skip that one and use one that does. In that case the problem isn't the web page (which WCAG covers) but the device (which WCAG does not)

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