WCAG: Enough Time

[StephDriver]

Summary

Action Required

• Inaccessible Warning Messages #354

Context

This review considered:

1. timing adjustable
2. Pause, stop, hide

Audit Results

Timing Adjustable

There are only three relevant elements where timing might be used: the carousel, the drop down navigation and warning messages.

Of these, the carousel and navigation do not use time delays, but instead change state in response to user input.

Warning messages, for example the warning for an incorrect username and password combination, can be dismissed by the user, but does auto-clear after a short delay. There is no warning that it is about to disappear. The shortness of time before it disappeared made it impossible to inspect the element involved. But the message also causes the screen to scroll so that it is visible (as it appears at the top of the page). This is problematic in itself - the message is not near the input that triggers it, and the screen moves unexpectedly.

These are also causing a change in context, as per 3.2 Predictable. See (see #341) for discussion, and the review should also consider whether they can be programmatically determined as per 4.1 Compatible (see #331).

Pause, Stop, Hide

There is no moving, blinking or scrolling information.