WCAG 2.1 Success Criteria Submission Requirements

From Mobile Accessibility Task Force

[2.1 Success Criteria]

Deadline: December 1, 2016

  1. Success Criteria Text: If suggesting a wording change to an existing success criteria, write the complete SC text and indicate the changes by surrounding new text with "@@". For example (just an example), "1.4.3 Contrast (Minimum): The visual presentation of @@text, images of text, and icons@@ has a contrast ratio of at least 4.5:1, except for the following: (Level AA)".
  2. Success Criteria Level: A/AA/AAA
  3. Glossary: Suggested glossary definitions or changes.
  4. Associated Principle and Guideline or Proposal for New Guideline
  5. Success Criteria Intent: What users benefit from the content successfully addressing it.
  6. User benefits: Clear information about how the proposal will benefit users, along with justification and evidence of the benefits. Include links to research.
  7. Test Procedure: Description of how this SC can be tested.
  8. Technique Titles: Possible technique titles which could be used to satisfy the SC.

Template

https://github.com/w3c/wcag21/wiki/Proposals-for-new-Success-Criteria

Mobile Success Criteria (14 New SCs and 14 weeks until deadline)

  1. New Guideline: Pointer Accessible: Make it easier for users to operate touch and pointer functionality.
    1. Pointer: All functionality can be operated with pointer input (Level A)
    2. Target Size: The size of the target in relation to the visible display at the default viewport size is at least: (Level AA)
    3. Pointer gestures (Level AA)
  2. New Guideline: Inputs with Assistive Technology
    1. Keyboard with AT (that remaps key input) (Level ?)
    2. Touch with Assistive Technology (Level ?)
    3. Input-agnostic (Level ?)
    4. No Focus Trap (Level ?)
    5. (No) accidental activation (Level ?)
    6. Speech Input: All functionality of the content (including touch and gesture) is operable through the keyboard, and does not obstruct a user's ability to access the keyboard commands through speech input. (Level A)
    7. Single key shortcut alternative: The user can adjust any single key shortcut to an alternative control of a string of symbols and letters.
  3. New Guideline: Advanced Input
    1. Pointer inputs with additional sensors
    2. Device sensors
  4. New Guideline: Make content usable in device orientations.
    1. Orientation: Orientation of the content is not locked to landscape or portrait, except where orientation is essential.
  5. Guideline 4.1 Compatible: Maximize compatibility with current and future user agents, including assistive technologies.
    1. Non-interference of AT: Content does not interfere with default functionality of platform level assistive technology (Level A)

Timeline

Success Criteria Priority Assigned to Deadline Reviewed by Taskforce URL of Proposal
M1: Pointer Patrick September 13 X https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m1.md
M2: Target Size X Marc August 18th X M2: Target Size https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m2.md
M3: Pointer gestures X Patrick September 13 X https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m3.md
M4: Keyboard with AT (that remaps key input)  X Patrick X https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m4.md Note: May add language about "AT that is relied upon" (in conformance stmt) or limiting it to Platform AT once in WCAG WG
M5: Touch with Assistive Technology X David August 18th X M5: Touch with Assistive Technology https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m5.md
M6: Concurrent input mechanisms (was: Input-agnostic / Additional inputs reliant on assistive technologies) X Patrick X - adjusted scope https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m6.md
M7: No Focus Trap X Patrick DROP for 2.1- revisit for WCAG 2.2 or Silver https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m7.md
M8: (No) accidental activation X David August 18th X M8: (No) accidental activation https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m8.md
M9: Pointer inputs with additional sensors (was: Advanced pointer input) X Patrick X https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m9.md
M10: Device sensors (was: Device inputs) X Patrick X https://github.com/w3c/Mobile-A11y-Extension/blob/gh-pages/SCs/m10.md
M11: Speech Input X Kim X M11 Proposed Speech Input
M12: Single key shortcut alternative Kim X M12a Proposed Single Key Shortcut Alternative, M12b Proposed Speech Command Mechanism
M13: Orientation Jonathan X https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/Proposed_SC_Orientation
M14: Non-interference of AT Chris Nov 3 X https://github.com/chriscm2006/Mobile-A11y-Extension/blob/m14/SCs/m14.md
M15: Change of content David Sep 27 X Programmatic notification is provided for each change in content that indicates an action was taken or that conveys information
M16: Notification of Loading/Busy David Oct 27 After initial page load, programmatic notification is provided for each visual indicator that content is loading or the page is busy.
Retrieved from "https://www.w3.org/WAI/GL/mobile-a11y-tf/wiki/index.php?title=WCAG_2.1_Success_Criteria_Submission_Requirements&oldid=3842"