3 ms·
This has bearing on my absolutely favourite part of the Web Content Accessibility Guidelines (WCAG) 2.0: Section 2.2.1, Timing Adjustable (http://www.w3.org/TR
by chrismorgan 13y ago
This has bearing on my absolutely favourite part of the Web Content Accessibility Guidelines (WCAG) 2.0:
Section 2.2.1, Timing Adjustable (http://www.w3.org/TR/WCAG20/#time-limits-required-behaviors http://www.w3.org/TR/WCAG20/#time-limits-required-behaviors):
----
2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A)
- Turn off: The user is allowed to turn off the time limit before encountering it; or
- Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or
- Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or
- Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or
- Essential Exception: The time limit is essential and extending it would invalidate the activity; or
- 20 Hour Exception: The time limit is longer than 20 hours.
Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.
----
Yea, verily! HN isn’t even Level A (the most basic level that "everyone" should comply with) compliant. Through this, HN fails Accessibility 101. (Its text colour choices are also often dubious as far as contrast goes—that’s covered in WCAG 2.0 as well, of course.)
I simply don’t care about the technical reasons. The choice of coroutines to back all of these things has broken the basic accessibility of all the content.
- zura 13y ago> The choice of coroutines to back all of these things has broken the basic accessibility of all the content. Exactly. This is actually a good example of More is Less.
- seabee 13y agoThe choice of coroutines is not the cause of the problem, it's the decision to store session state on the server and clearing that state before the user is done. This same problem can happen in a PHP application, and it can be avoided in a Racket web framework application that uses continuations.