Subset of WCAG 2.0 Techniques Applicable to Mobile without Changes that need language update

From Mobile Accessibility Task Force

Reference

WCAG 2.0 Techniques Applicable to Mobile without Changes

WCAG 2.0 techniques

(Note: changes to understanding are here: [[WCAG 2.0 understanding that needs language update]

Changes needed

  • G14 example 4 "press the button labeled Go to submit your results and proceed to the next step" might be too specific to large screen – such long instructions would not be appropriate for mobile - Kim Patch



  • G58 Description, 4th sentence: "The link can be immediately before or after the synchronized media content" implies large screen. Suggest "The link can be immediately before or after, or can be overlaid on synchronized media content." - Kim Patch


  • G59 Description, 2nd paragraph, 2nd sentence:"tabbing through content" might be too specific to laptop. Suggest "navigating through content sequentially such as by pressing the tab key or swiping in a given direction". - Kim Patch



  • G98 Non-mobile comment: The example has three bullet points, which implies three examples, but it looks like the second bullet point is part of the first example, so the second bullet point should be removed. A more general comment about examples and bullets: the document would generally be more useful if the examples were numbered instead of bulleted and so could be referred to by number. Examples that contain steps could be labeled with alphabet letters to avoid numbers within numbers. - Kim Patch



  • G107 Description, second paragraph: "clicking on a link", and first example, "clicks(or uses spacebar) on a button". Suggest replacing these with "clicking on or touching a link" and "clicks (or touches or uses a spacebar) on a button" to make it obvious that mobile is included. - Kim Patch

Task force discussion November 28, suggest using "activate" to cover all of the above.



  • G112 Non-mobile comment on style: Example 3 is difficult to parse, "Definition: The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this specification…". Suggest putting keywords in quotes: "Definition: The key words "must", "must not", "required", "shall", "shall not", "should", "should not", "recommended", "may", and "optional" in this specification…" - Kim Patch


  • G128 Indicating current location within navigation bars: All the examples imply large screen and Example 3 is specific to mouse. Suggest adding an example that provides a good equivalent solution for smallscreen/touch so mobile is fully covered. - Kim Patch 2014-11-10


  • G131 Providing descriptive labels: Example 1 and 3 imply large-screen, mouse and keyboard. Suggest the following modifications: Example 1:… The controls can be operated using mouse, keyboard or touch. The controls are labeled “Zoom in (Ctrl + Shift + L)" and “Zoom out (Ctrl + Shift + R), or are labeled "+" and "-" and keyboard shortcut tips appear when the user activates the help overlay. Also note grammar correction above – "and" should be lowercase. Example 3: A purchasing form includes several fields that are required. In addition to identifying the field, the label for each required field includes an indicator that the field is required such as the word “required" in parentheses. - Kim Patch 2014-11-10


  • G133 Providing a checkbox on the first page of a multipart form that allows users to ask for longer session time limit or no session time limit: Checkbox seems overly narrow, maybe even the wrong example here – the "or" implies a radio button. On a small screen another indicator, such as a drop down might be more appropriate. Suggest the following modification: Description …"by providing a control such as a checkbox to request additional time…" - Kim Patch 2015-01-15


  • G140: Separating information and structure…: Nonmobile comment on grammar. "Such as" and "etc." are redundant. Description, first paragraph: Suggest removing "etc." from the two phrases that begin with "such as". Example 1: Suggest removing "etc." from the two phrases that begin with "such as". - Kim Patch 2015-2-2


  • G146: Using liquid layout: Nonmobile comment on grammar. Description: #2 Suggest changing "… floating boxes, which wrap" to "… floating boxes that wrap" [note that comma is removed]. - Kim Patch 2015-2-2


  • G148: Not specifying background color…: Nonmobile comment on grammar. Description, second paragraph suggest changing "…set their user agent…" to "…set their user agents…" [note plural]. - Kim Patch 2015-2-2


  • G152: Setting animated gif images…: Nonmobile comment on grammar. Description, fourth paragraph. Suggest changing punctuation in "Truncate this number down to the nearest integer, do not round up to the next integer, to ensure that the image will stop within five seconds." to "Truncate this number down to the nearest integer (do not round up to the next integer) to ensure that the image will stop within five seconds." - Kim Patch 2015-2-2


  • G153: Making the text easier to read: Nonmobile comments on grammar. Description, first sentence. Suggest changing "not difficult" to "easy". Description, fifth bullet. Change "…no more than two conjunction" to "…no more than two conjunctions" [note plural]. Description, seventh bullet. Change "… other terms with a specialized meaning…" to "… other terms with specialized meanings…" [note plural]. - Kim Patch 2015-2-2


  • G155: Providing a checkbox…: Nonmobile comment on grammar. Examples, second bullet point, second sentence. Suggest changing "… users to enter new accounts and verify that they are the owner…" to "… users to enter new accounts and verify that they are the owners…" [note plural]. Examples, third bullet point, second sentence. Suggest changing "… The user is taken to a page where the information they have submitted…" to "… The user is taken to a page where the information the user has submitted…" - Kim Patch 2015-2-2
Retrieved from "https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/index.php?title=Subset_of_WCAG_2.0_Techniques_Applicable_to_Mobile_without_Changes_that_need_language_update&oldid=3877"