Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A a11yproject.com
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The A11Y Project
  • a11yproject.com
  • Issues
  • #1282
Closed
Open
Issue created May 25, 2021 by Administrator@rootContributor

Checklist item clarifications: Questions/comments on 2 checklist items

Created by: MicheleAWilliams-A11y

Hi there, 2 questions/comments in the checklist:

Appearance > Double-check that good proximity between content is maintained



The "straw test" mentioned in the description is very useful; however, I didn't see anything else in the checklist representing 1.3.3's sensory guidance except the related "color only" guidance of 1.4.1 - Use of Color.

 

 

I know the checklist isn’t all-inclusive of WCAG 2.1 AA but I think it's worth noting other non-color characteristics such as spatial directions (e.g., “column on the left" which gets impact by browser zoomed pages and of course screen readers/braille displays) and audio cues (e.g., “record after the tone" which needs visual confirmation for deaf and hard of hearing folks).

Just seemed the additional sensory information was a good low-hanging fruit guideline to include along with color since it is a formal WCAG item as well as not always remembered (or known).

Global Code > Remove session timeouts 



The description text rightly clarifies this is about adjustable timing and starts with “If you cannot”. However, given people might (likely often) take the top point as the guideline without further reading (as I actually just experienced in working with Webflow folks on their checklist), I wondered if there was a reason to be so direct in "removing timeouts" rather than, say, "warning and extending timeouts"?

Not to say timeouts are the greatest but having worked with a bank, for instance, I can attest these timeout discussions get touchy (heavy sigh) and saying "remove them" would be considered blasphemy. Just wanted to point out this checklist item may be perceived as the place that definitively says "accessibility requires removing timeouts" in case that wasn't your intent.

Just some thoughts as an observer who saw the checklist in use by newbies. Happy to have more discussion. Thanks!

Assignee
Assign to
Time tracking