Timeline for How should time limits be communicated to screen reader users?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2020 at 10:51 | history | edited | CommunityBot |
Commonmark migration
|
|
| Aug 31, 2016 at 9:20 | comment | added | SteveD | Someone using a screen reader is at a big disadvantage to non-screen reader user, so your design needs to level the playing field. 2.1.1 tells you everything you need to know, even with the design constraints you just mentioned. This UX:SO is not supposed to answer "how to implement" questions, but aria live regions and alerts will solve your screen reader problem. Have you read the Intent of 2.2.1 w3.org/TR/UNDERSTANDING-WCAG20/… | |
| Aug 31, 2016 at 1:37 | comment | added | Jessica Knight | Great -- I missed these parts of WCAG! However, this doesn't directly address the question -- how do we communicate the time limits in a convenient/non-disruptive way? We're handling time extensions as suggested in Understanding 2.2.1: "In cases where timing is not an intrinsic requirement but giving users control over timed events would invalidate the outcome, a third party can control the time limits for the user (for example, granting double time on a test)." Thus, the student can't extend their own time once the test starts, so a dialog with time remaining doesn't seem like the right way! | |
| Aug 30, 2016 at 9:14 | history | answered | SteveD | CC BY-SA 3.0 |