Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

Understanding Timeouts #785

Closed
awkawk opened this issue Mar 2, 2018 · 3 comments
Closed

Understanding Timeouts #785

awkawk opened this issue Mar 2, 2018 · 3 comments

Comments

@awkawk
Copy link
Member

awkawk commented Mar 2, 2018

The 2.2.6 Timeouts (AAA) SC has draft Understanding content that can be viewed at Understanding Timeouts.

Please review the Understanding document and submit a comment on this issue for any changes that are needed to the content.

@lseeman
Copy link
Contributor

lseeman commented Apr 22, 2018

suggest we rewrite"When there is a chance to extend a time limit, it should be noted that many users, within 20 seconds, cannot read instructions to extend a time limit. Using simple text can reduce the time it takes to read these instructions."4
to
"When there is a chance to extend a time limit, many users will require a few minites to read the instructions. When the time given to read the warning and instructions is short (such as 20 seconds) users with language or reading disabilities will not be able to extend the time limit. Using simple text can reduce the time it takes to read these instructions.

The best way to conform

@alastc
Copy link
Contributor

alastc commented Apr 23, 2018

Note comment from #830:

I initially thought that 2.2.6 should be made a technique of 2.2.1. On closer reading, I see now the hole it's trying to fill. Please include something near the beginning of the Intent section of each SC to clarify the difference.

@michael-n-cooper
Copy link
Member

This issue was moved to w3c/wcag#349

Understanding Document Content automation moved this from In progress to Done Jun 12, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

4 participants