W3C

Edit comment LC-2626 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-2619 Next: LC-2729

Comment LC-2626
:
Commenter: Detlev Fischer <detlev.fischer@testkreis.de>

or
Resolution status:

The Failure test just looks for meta http-equiv with value "refresh" and content > 0. I can see a scenario where the value of content is high (say, 1200 = 20 minutes) and a control is available to extend or turn off auto-refresh (e.g., via DOM scripting of the meta http-eqiv content attribute). In that case, it seems to me that SC 2.2.1 would be met. Would F41 not need to be updated to reflect that option, also in the test procedure?

Proposed Change:
Not sure - if my argument holds, the test would need to check whether a page actually get refreshed (either by inspecting the content value or, if it is done server-side, by waiting (how long a wait is sensible I am not sure, 20 mins?), and, if the page is found to refresh, look out for a control to extend or turn off the time limit. If a refresh takes place and there is a working control giving users enough time to locate it, the Failure would not apply.
(space separated ids)
(Please make sure the resolution is adapted for public consumption)


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: 2626.html,v 1.1 2017/08/11 06:39:58 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org