Testable Statements for Each Pattern

From Cognitive Accessibility Task Force

Objective 1: Help Users Understand What Things are and How to Use Them

Pattern Proposals for WCAG Related WCAG SC
Make the Purpose of Your Page Clear
  • 2.4.2 Page Titled
  • 2.4.6 Headings and Labels
  • 2.4.10 Section Headings
Use a Design that the User is Likely to Recognize and Understand None
Use a Consistent Visual Design
  • 3.2.3 Consistent Navigation
  • 3.2.4 Consistent Identification
Make Each Step Clear
  • 1.3.2 Meaningful Sequence
  • 2.4.8 Location
Clearly Identify Controls and Their Use
  • Questions raised in the WCAG github issue 36 discussion:
    • Defining controls
    • Link purpose. "The purpose of each link can be determined from the link text alone or..."
      • Difference: how do I know it is a link?
        • E.g. can I ask all links to be underlined and blue if this is not their automatic state?
        • I know something is a link because:
            • Underlined and blue (or purple if a visited link) – if I have vision.
            • Announces as link – if using text-to-speech tool.
            • Cursor change.
    • Consistent Identification. Components that have the same functionality within a set of content are identified consistently.
      • If unusual, even if consistent, this does not make it easy to identify.
    • Labels or instructions are provided when content requires user input.
    • If style selected requires instructions, slows down person using them.
  • 1.3.5 Identify Input Purpose
  • 1.3.6 Identify Purpose
  • 2.4.9 Link Purpose
Make the Relationship Clear Between Controls and What They Affect None
Use Symbols that Help the User
  • 1.1 Text Alternatives


Objective 2: Help Users Find What They Need

Pattern Proposals for WCAG Related WCAG SC
Make it Easy to Identify the Most Important Tasks and Features of the Site None None
Ensure the Hierarchy of the Site and Menu Structure is Logical, Easy to Identify and Navigate
  • 2.4.6 Headings and Labels
  • 1.4.13 Content on Hover or Focus
Use a Clear and Understandable Page Structure
  • 1.3.1 Info and Relationships
Ensure the Most Important Things on the Page are Easy to Find * On coga github: critical-features.html and WCAG issue 39
  • 1.3.5 Identify Input Purpose
  • 1.3.6 Identify Purpose
Break Media into Chunks None
Provide Search
  • 2.4.5 Multiple Ways


Objective 3: Use Clear and Understandable Content

Pattern Proposals for WCAG Related WCAG SC
Use Clear Words
  • 3.1.3 Unusual Words
  • 3.1.4 Abbreviations
  • 3.1.5 Reading Level
  • 3.1.6 Pronunciation
Use a Simple Tense and Voice
  • 3.1.5 Reading Level
Avoid Double Negatives or Nested Clauses
  • 3.1.5 Reading Level
Use Literal Language
  • 3.1.5 Reading Level
Keep Text Succinct
  • 3.1.5 Reading Level
Use Clear, Unambiguous Text Formatting and Punctuation None
Include Symbols and Letters Necessary to Decipher the Words None
  • 1.4.8 Visual Presentation (loose)
  • 3.1.5 Reading Level
Provide Summary of Long Documents and Media None
Separate Each Instruction
  • 1.3.2 Meaningful Sequence
Use White Spacing
  • Use clear spacing between letters, words, sentences, lines, paragraphs and blocks of text.
  • Text is not fully justified and on coga github: visual-presentation.html, WCAG issue 51 and PR number 113.
  • 1.4.8 Visual Presentation
  • 1.4.12 Text Spacing
Ensure Foreground Content is not Obscured by Background None None
Explain Implied Content None * 3.1.5 Reading Level
Provide Alternatives for Numbers None


Objective 4: Help Users Avoid Mistakes or Correct Them

Pattern Proposals for WCAG Related WCAG SC
Ensure Controls and Content Do Not Move Unexpectedly None
  • 2.3.3 Animation from Interactions
  • 3.2.1 On Focus
  • 3.2.2 On Input
  • 3.2.5 Change on Request
Let Users Go Back
  • 3.3.6 Error Prevention (All)
Notify Users of Fees and Charges at the Start of a Task None
Design Forms to Prevent Mistakes
  • 2.4.3 Focus Order
  • 2.4.7 Focus Visible
  • 3.3.2 Labels or Instructions
  • 3.3.3 Error Suggestion
Make it Easy to Undo Form Errors
  • 3.3.1 Error Identification
  • 3.3.4 Error Prevention (All)
Use Clear Visible Labels None
  • 3.3.2 Labels or Instructions
Use Clear Step-by-step Instructions None
Provide Flexible Form Inputs
  • 3.3.4 Error Prevention (All)
Avoid Data Loss and "Time Outs"
  • 2.2.3 No Timing
  • 2.2.5 Re-authenticating
  • 2.2.6 Timeouts
Provide Feedback None
Keep Users' Information Safe and Help Users Understand Known Risks None
Use Familiar Metrics and Units None None


Objective 5: Help Users to Maintain Focus

Pattern Proposals for WCAG Related WCAG SC
Limit Interruptions None
Make Short Critical Paths None None
Avoid Too Much Content None
Provide Information So a User Can Complete and Prepare for a Task None None


Objective 6: Ensure Processes Do Not Rely on Memory

Pattern Proposals for WCAG Related WCAG SC
Provide a Login that Does Not Rely on Memory or Other Cognitive Skills None
Allow the User a Simple, Single Step, Login None None
Provide a Login Alternative with Less Words None None
Let Users Avoid Navigating Voice Menus None
Do Not Rely on Users Memorizing Information None


Objective 7: Provide Help and Support

Pattern Proposals for WCAG Related WCAG SC
Provide Human Help None
Provide Help and Alternative Content for Complex Information and Tasks
  • 3.3.5 Help
Clearly State the Results and Disadvantages of Actions, Options, and Selections None None
Provide Help for Forms and Non-standard Controls
  • 3.3.5 Help
Make It Easy to Find Help and Give Feedback None
Provide Help with Directions None
Provide Reminders None


Objective 8: Support Adaptation and Personalization

Pattern Proposals for WCAG Related WCAG SC
Let Users Control When the Content Changes
  • 2.2.4 Interruptions
Enable APIs and Extensions
  • 2.2.4 Interruptions
  • 2.5.4 Motion Actuation
Support Simplification None
Support a Personalized and Familiar Interface None
Retrieved from "https://www.w3.org/WAI/GL/task-forces/coga/wiki/index.php?title=Testable_Statements_for_Each_Pattern&oldid=2343"