This document:Public document·View comments·Disposition of Comments·
Nearby:Mobile Web Best Practices Working Group Other specs in this tool Mobile Web Best Practices Working Group's Issue tracker
Quick access to LC-1578 LC-1579 LC-1580 LC-1581 LC-1582 LC-1583 LC-1585 LC-1586 LC-1587 LC-1588 LC-1589 LC-1591 LC-1592 LC-1593 LC-1594 LC-1596 LC-1597 LC-1598 LC-1599 LC-1600 LC-1601 LC-1602 LC-1604 LC-1605 LC-1606 LC-1607 LC-1608 LC-1609 LC-1610 LC-1611 LC-1612 LC-1613 LC-1614 LC-1615 LC-1616 LC-1617 LC-1618 LC-1619 LC-1620 LC-1621 LC-1622 LC-1623 LC-1624 LC-1625 LC-1626 LC-1627 LC-1628 LC-1629 LC-1630 LC-1631 LC-1632 LC-1633 LC-1634 LC-1635 LC-1636 LC-1637 LC-1638 LC-1639 LC-1640 LC-1641 LC-1642 LC-1643 LC-1644 LC-1645 LC-1646 LC-1647 LC-1648 LC-1649 LC-1650 LC-1651 LC-1652 LC-1653 LC-1654 LC-1655 LC-1656 LC-1658 LC-1659 LC-1660 LC-1661 LC-1662 LC-1663 LC-1664
Previous: LC-1604 Next: LC-1589
The draft states: "This test does not determine whether the user is able to opt out of refresh." Is the possibility of opting out going to be covered elsewhere? Using <meta http-equiv="refresh" content="..." /> fails three different success criteria of the Web Content Accessibility Guidelines 2.0 (see failure F40 in "Techniques for WCAG 2.0" [2]). This is because screen readers will start reading from the top of the page again when the page refreshes, thereby taking away control from the user over his interaction with a page. Server-side redirects [3] are preferable, but WCAG 2.0 currently also allows client-side redirects if they have no timeout: see techniques G110 (Using an instant client-side redirect [4]) and H76 (Using meta refresh to create an instant client-side redirect [5]).