Technique Development Assignments

From Mobile Accessibility Task Force
Jump to: navigation, search

This page catalogs Mobile A11y Task Force proposed new mobile techniques and proposed changes to existing WCAG techniques. Changes to the existing WCAG Techniques were discussed in 2014, but are not currently active work.

Resources and instructions

Proposed Mobile Techniques

Technique Status Assigned to Success Criteria Type Priority Task Force Review WCAG Working Group Review
M001: Defining the hover, focus, selected and touch (regular, long) states M001 Github Repo In Progress Kathy W 2.1.1, 3.2.1 or 3.2.2, UAAG 1.3 Sufficient Incomplete Incomplete
M002: Providing adequate touch target size / Ensuring that touch targets are large enough to touch accurately without magnification M002 Github Repo Ready for Review Alan Smith 2.1.1, 1.4.4, Principle 2 Advisory Incomplete Incomplete
M003: Activating elements via the touchend event M003 Github Repo Ready for TF review Detlev 2.1.1, 3.2.1 Sufficient Incomplete Incomplete
*M004: Providing clear indication that elements are actionable / Design actionable objects to look actionable M004 Github Repo Ready for TF review Detlev Guidelines 2.1 or Principle 2 Advisory Incomplete Incomplete
M005: Providing instructions for custom functions and gestures M005 Github Repo - Henny 3.3.2, 2.1.1 Sufficient, Failure Incomplete Incomplete
*M006: Specifying input type for numerical or character data M006 Github Repo Incorporate into G89 G89 1.3.1 Sufficient Incomplete Incomplete
M007: Supporting the characteristic properties of the platform (e.g. zoom, larger font, captions) M007 Github Repo Submitted Alan Smith Best Practice or Principle 4 Advisory Incomplete Incomplete
*M008: Setting the virtual keyboard to the type of data entry required M008 Github Repo In Progress Jon Avila 1.3.1, 4.1.2 Advisory Incomplete Incomplete
*M009: Adapting the length of link texts to viewport width M001 Github Repo - Unassigned 1.4.8 Advisory Incomplete Incomplete
M010: Allowing users to interact using device buttons (e.g. arrow keys, ok button) M009 Github Repo - Unassigned 2.1.1 or Principle 2 Advisory Incomplete Incomplete
*M011: Ensuring that the interface can be used with a physical keyboard M011 Github Repo Incorporate with G202 Unassigned 2.1.1 Sufficient Incomplete Incomplete
*M012: Including shortcuts to allow users to jump to sections of the page M012 Github Repo - Unassigned 2.4.5 Advisory Incomplete Incomplete
M013: Providing a way for users to change font size M013 Github Repo - Marc J 1.4.4 Advisory Incomplete Incomplete
*M014: Ensuring that navigation works on different screen sizes M014 Github Repo - Unassigned 2.1.1 Sufficient Incomplete Incomplete
*M015: Providing a way for users to see what page they are on M015 Github Repo - Alistair Garrison 2.4.8 Sufficient Incomplete Incomplete
M016: Providing vertical navigation mechanisms that work without horizontal scrolling on narrow width screens M016 Github Repo Ready for TF review Detlev 1.4.4 Advisory Incomplete Incomplete
M017: Providing the open/closed state information in the menu icon M017 Github Repo In Progress David 1.3.1, 4.1.2 Sufficient Incomplete Incomplete
M018: Ensuring that menu can be zoomed to 200% M018 Github Repo - Unassigned 1.4.4 Sufficient Incomplete Incomplete
M019: Providing media metadata M019 Github Repo - Unassigned 1.2.1, 1.2.2, 1.2.3, 1.1.1 Advisory Incomplete Incomplete
M020: Providing instructions for form data types M020 Github Repo - Unassigned 3.3.2 Advisory Incomplete Incomplete
M021: Setting viewport meta setting to allow magnification to 200% M021 Github Repo In Progress Kathy W 1.4.4 Sufficient Incomplete Incomplete
M22: Spacing Between elements M022 Github Repo REMOVED Marc J Incomplete Incomplete
M023: Set the HTML virtual keyboard to the type of data entry required. M023 Github Repo In Progress Jon Avila SC 3.3.2 Advisory Medium Incomplete Incomplete
M024: Set the iOS virtual keyboard to the type of data entry required. M024 Github Repo In Progress Jon Avila SC 3.3.2 Advisory Medium Incomplete Incomplete
M025: Set the Android virtual keyboard to the type of data entry required. M025 Github Repo In Progress Jon Avila SC 3.3.2 Adivsory Medium Incomplete Incomplete
M026: M026 Github Repo In Progress SC Medium Incomplete Incomplete
M027: Providing touch access for custom controls M027 Github Repo In Progress Detlev Fischer SC 2.5.1 Medium Incomplete Incomplete
M028: Using standard One Touch controls M028 Github Repo In Progress Jon A SC Medium Incomplete Incomplete
M029: Touch events are only triggered when touch is removed from a control M029 Github Repo In Progress Chris M SC Medium Incomplete Incomplete
M030: Multiple elements M030 Github Repo SC 2.5.4 Medium Incomplete Incomplete
Specifying a system font in web content to support platform text resize without browser or platform assistive technology zoom.: Proposed Jon A SC Medium Incomplete Incomplete
FM001 Failure of 2.5.3 Failure of 2.5.3 Modified Touch due to all content and functionality not being available by touch gesture when built-in assistive technology is active New Success Criteria 2.5.1 Failure complete incomplete
FM002 Failure of 2.5.1 Failure of 2.5.1 Touch: All functions available by touch are still available by touch after system assistive technology that remaps touch gestures is turned on. (Level A) In Progress Chris M New Success Criteria 2.5.1 Failure incomplete impcomplete
FM003 Failure of 2.5.1 Component can be opened but cannot be closed with touch when a system screen reader is running. (Level A) In Progress Marc J New Success Criteria 2.5.1 Failure incomplete impcomplete
FM004 Failure of 2.5.4 Touch target is less than 44 pixels by 44 pixels. (Level A) In Progress Marc J New Success Criteria 2.5.4 Failure incomplete impcomplete
FM005 Failure of 2.5.4 Touch target is less than 44 pixels by 44 pixels at the default viewport size.(Level A) In Progress Marc J New Success Criteria 2.5.4 Failure incomplete impcomplete 
* Not yet in Technique lists

Providing touch access for custom controls

Existing WCAG Techniques that Apply to Mobile

General

Need to Discuss

  • G1: Adding a link at the top of each page that goes directly to the main content area (not applicable) Jeanne Spellman 16 Jan 2014; Jon Avila (reconsider applicability)
Technique Status Assigned to Priority Text Example Live Example(s) Test Procedure Original Technique (if applicable)
G4 Allowing the content to be paused and restarted from where it was paused Approved by WCAG Working Group 23 Sept 2014 Jon Avila - No Change Completed No Change No Change G4
G9: Creating captions for live synchronized media Approved by WCAG Working Group 14 Oct 2014 - DONE Jon Avila - No Change Proposed No Change No Change G9
G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes - unassigned - No change Proposed No change No change G10
G17: Ensuring that a contrast ratio of at least 7:1 exists between text (and images of text) and background behind the text No Change needed Alan Smith - Complete Incomplete Incomplete Incomplete G17
G21: Ensuring that users are not trapped in content Approved by WCAG Working Group 07 Oct 2014 Jon Avila - Proposed No Change No Change Proposed G21
G53: Identifying the purpose of a link using link text combined with the text of the enclosing sentence Approved WCAG Working Group - 21 Oct 2014 Alan Smith - Complete Incomplete Incomplete Incomplete G53
G60: Playing a sound that turns off automatically within three seconds Rejected - no changes will be made Alan Smith - Complete Incomplete Incomplete Incomplete G60
G61: Presenting repeated components in the same relative order each time they appear Approved by WCAG Working Group 21 Oct 2014 Alan Smith - Complete Incomplete Incomplete Incomplete G61
G68: Providing a short text alternative that describes the purpose of live audio-only and live video-only content - Alan Smith - Incomplete Incomplete Incomplete Incomplete G68
G78: Providing a second, user-selectable, audio track that includes audio descriptions Approved by WCAG Working Group 14 Oct 2014 - DONE Jon Avila - Unchanged Unchanged Unchanged Proposed G78
G82: Providing a text alternative that identifies the purpose of the non-text content Survey 09 Oct 2014 Jon Avila - Incomplete Incomplete Incomplete Incomplete G82
G83: Providing text descriptions to identify required fields that were not completed Survey 08 Sept 2014 Alan Smith - No change Incomplete Incomplete Incomplete G83
G84: Providing a text description when the user provides information that is not in the list of allowed values Survey 08 Sept 2014 Alan Smith - No change Incomplete Incomplete Incomplete G84
G85: Providing a text description when user input falls outside the required format or values Survey 29 Sept 2014 Kathy W - Proposed Proposed No Change No Change G85
G87: Providing closed captions - Brent Shiver - Incomplete Incomplete Incomplete Incomplete G87
G88: Providing descriptive titles for Web pages - unassigned - Incomplete Incomplete Incomplete Incomplete G88
G89: Providing expected data format and example - Detlev Fischer - Incomplete Incomplete Incomplete Incomplete G89
G90: Providing keyboard-triggered event handlers Sent to WCAG Working Group - 16 Oct 2014 Kathy W - Incomplete Incomplete Incomplete Incomplete G90
G142: Using a technology that has commonly-available user agents that support zoom - Detlev Fischer - Incomplete Incomplete Incomplete Incomplete G142
G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text Survey 01 Sept 2014 Detlev Fischer - Incomplete Incomplete Incomplete Incomplete G145
G162: Positioning labels to maximize predictability of relationships Sent to WCAG Working Group - 23 Oct 2014 Kathy W - Completed Incomplete Incomplete Incomplete G162
G183: Using a contrast ratio of 3:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them - Jan Richards - Incomplete Incomplete Incomplete Incomplete G183
G202: Ensuring keyboard control for all functionality Approved by WCAG Working Group 14 Oct 2014 - DONE Jan Richards - Incomplete Incomplete Incomplete Incomplete G202

HTML

Technique Status Assigned to Priority Text Example Code Live Example(s) Test Procedure Original Technique (if applicable)
H2: Combining adjacent image and text links for the same resource - Kathy W - Incomplete Incomplete Incomplete Incomplete H2
H24: Providing text alternatives for the area elements of image maps - Unassigned - Incomplete Incomplete Incomplete Incomplete H24
H32: Providing submit buttons - Tom Babinszki - Incomplete Incomplete Incomplete Incomplete H32
H36: Using alt attributes on images used as submit buttons - Kathy W - Incomplete Incomplete Incomplete Incomplete H36
H63: Using the scope attribute to associate header cells and data cells in data tables - Detlev Fischer - Incomplete Incomplete Incomplete Incomplete H63
H73: Using the summary attribute of the table element to give an overview of data tables - Unassigned - Incomplete Incomplete Incomplete Incomplete H73
H83: Using the target attribute to open a new window on user request and indicating this in link text - Unassigned - Incomplete Incomplete Incomplete Incomplete H83
H87: Not interfering with the user agent's reflow of text as the viewing window is narrowed - Unassigned - Incomplete Incomplete Incomplete Incomplete H87
H89: Using the title attribute to provide context-sensitive help - Unassigned - Incomplete Incomplete Incomplete Incomplete H89
H91: Using HTML form controls and links - Unassigned - Incomplete Incomplete Incomplete Incomplete H91
H92: Including a text cue for colored form control labels - Unassigned - Incomplete Incomplete Incomplete Incomplete H92

CSS

Technique Status Assigned to Priority Text Example Code Live Example(s) Test Procedure Original Technique (if applicable)
C12: Using percent for font sizes - Unassigned - Incomplete Incomplete Incomplete Incomplete C12
C15: Using CSS to change the presentation of a user interface component when it receives focus - Unassigned - Incomplete Incomplete Incomplete Incomplete C15
C20: Using relative measurements to set column widths so that lines can average 80 characters or less when the browser is resized - Unassigned - Incomplete Incomplete Incomplete Incomplete C20
C23: Specifying text and background colors of secondary content such as banners, features and navigation in CSS while not specifying text and background colors of the main content - Unassigned - Incomplete Incomplete Incomplete Incomplete C23
C25: Specifying borders and layout in CSS to delineate areas of a Web page while not specifying text and text-background colors - Unassigned - Incomplete Incomplete Incomplete Incomplete C25

Client Scripting

Technique Status Assigned to Priority Text Example Code Live Example(s) Test Procedure Original Technique (if applicable)
SCR30: Using scripts to change the link text - Unassigned - Incomplete Incomplete Incomplete Incomplete SCR30
SCR31: Using script to change the background color or border of the element with focus - Unassigned - Incomplete Incomplete Incomplete Incomplete SCR31
SCR34: Calculating size and position in a way that scales with text size - Unassigned - Incomplete Incomplete Incomplete Incomplete SCR34
SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons - Unassigned - Incomplete Incomplete Incomplete Incomplete SCR35
SCR37: Creating Custom Dialogs in a Device Independent Way Revised - Survey 29 Sept 2014 Detlev Fischer - Proposed No Change No Change Proposed SCR37

Failures

Technique Status Assigned to Priority Text Example Code Live Example(s) Test Procedure Original Technique (if applicable)
F19: Failure of Conformance Requirement 1 due to not providing a method for the user to find the alternative conforming version of a non-conforming Web page - Unassigned - Incomplete Incomplete Incomplete Incomplete F19
F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying the contents - Unassigned - Incomplete Incomplete Incomplete Incomplete F25
F54: Failure of Success Criterion 2.1.1 due to using only pointing-device-specific event handlers (including gesture) for a function - Unassigned - Incomplete Incomplete Incomplete Incomplete F54
F55: Failure of Success Criteria 2.1.1, 2.4.7, and 3.2.1 due to using script to remove focus when focus is received - Unassigned - Incomplete Incomplete Incomplete Incomplete F55
F69: Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured - Unassigned - Incomplete Incomplete Incomplete Incomplete F69
Retrieved from "https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/index.php?title=Technique_Development_Assignments&oldid=3868"