WAI User Agent and Web Content Coordination Page
Comments or questions on the coordination issues can be sent to the
UA Working Group,
Jon Gunderson (Chair)
Refer to 6
August update on Issues (Not yet integrated here).
Coordination Issues on the UA Issues List
- Issue
#3: Should user agents be able recognize markup for navigation bars
- Issue
#12: Recommend full implmentation of MathML
- Issue
#33: Allow the user to view header information associated with a cell
- Issue
#35: Allow the user to view the summary attribute of a table
- Issue
#43: Navigation and activation of elements with ACCESSKEY attributes
defined
- Issue
#49: Add a checkpoint that says that UAs should allow users to turn off
flicker
- Issue
#51: Language support Allow user to access alternative content
Coordination Issues with Existing Web Content Checkpoints
- Web Content Checkpoint 1.5: Until user agents render text equivalents for
client-side image map links, provide redundant text links for each active
region of a client-side image map. [Priority 3]
Status: done
- 5.3 Do not use tables for layout unless the table makes sense when
linearized. Otherwise, if the table does not make sense, provide an alternative
equivalent (which may be a linearized version). [Priority 2]
Note. Once user agents support style sheet positioning, tables should not be
used for layout.
Refer also to checkpoint 3.3.
Techniques for checkpoint 5.3
Status: done
- 7.1 Until user agents allow users to control flickering, avoid causing the
screen to flicker. [Priority 1]
Status: done
- 7.2 Until user agents allow users to control blinking, avoid causing
content to blink (i.e., change presentation at a regular rate, such as turning
on and off). [Priority 2]
Status: done
- 7.3 Until user agents allow users to freeze moving content, avoid movement
in pages. [Priority 2]
Status: open
- 7.4 Until user agents provide the ability to stop the refresh, do not
create periodically auto-refreshing pages. [Priority 2]
Status: done
- 7.5 Until user agents provide the ability to stop auto-redirect, do not use
markup to redirect pages automatically. Instead, configure the server to
perform redirects. [Priority 2]
Status: open
- 10.1 Until user agents allow users to turn off spawned windows, do not
cause pop-ups or other windows to appear and do not change the current window
without informing the user. [Priority 2]
Status: closed
- 10.2 Until user agents support explicit associations between labels and
form controls, for all form controls with implicitly associated labels, ensure
that the label is properly positioned. [Priority 2]
Status: closed
- 10.3 Until user agents (including assistive technologies) render
side-by-side text correctly, provide a linear text alternative (on the current
page or some other) for all tables that lay out text in parallel, word-wrapped
columns. [Priority 3]
Status: open
- 10.4 Until user agents handle empty controls correctly, include default,
place-holding characters in edit boxes and text areas. [Priority 3]
Status: open
- 10.5 Until user agents (including assistive technologies) render adjacent
links distinctly, include non-link, printable characters (surrounded by spaces)
between adjacent links. [Priority 3]
Status: open
- 13.2 Provide metadata to add semantic information to pages and sites.
[Priority 2]
Status: open
- 13.6 Group related links, identify the group (for user agents), and, until
user agents do so, provide a way to bypass the group. [Priority 3]
Status: open