-
Type:
Improvement
-
Status:
Resolved
-
Priority:
Minor
-
Resolution:
Incomplete
-
Affects Version/s:
None
-
-
- All ONCLICK handlers should have an equivalent ONKEYPRESS handler.
Some users are unable to use a mouse, so use the keyboard instead. Add
an equivalent keyboard event handler to help these users.
- All ONMOUSEDOWN handlers should have an equivalent ONKEYDOWN handler.
Some users are unable to use a mouse, so use the keyboard instead. Add
an equivalent keyboard event handler to help these users.
- All ONMOUSEOUT handlers should have an equivalent ONBLUR handler. Some
users are unable to use a mouse, so use the keyboard instead. Add an
equivalent keyboard event handler to help these users.
- All ONMOUSEOVER handlers should have an equivalent ONFOCUS handler.
Some users are unable to use a mouse, so use the keyboard instead. Add
an equivalent keyboard event handler to help these users.
- All ONMOUSEUP handlers should have an equivalent ONKEYUP handler. Some
users are unable to use a mouse, so use the keyboard instead. Add an
equivalent keyboard event handler to help these users.
- IFRAME tags must have alternative content. To cater for screen readers
that don't support frames, place some text in the IFRAME tag. For
example: <iframe src='file.htm'>Alternative content</iframe>
- IMG tags must have an ALT attribute. Add an ALT attribute describing
each image, which screen readers read aloud. Spacer images and purely
decorative images should use ALT=''.
- No TITLE attributes found for the frames on these pages. Add a TITLE
attribute to each FRAME and IFRAME element (e.g. TITLE="Main
Content"). Screen readers read out the TITLE letting the user decide
which frame to visit.
- Provide a way to skip repetitive navigation links. Without a skip
link, screen readers read out the navigation links on every page
before reading the page content. Headings can be a substitute in
limited circumstances, but they're not used by all screen reader
users, and many other assistive technology users have no way to
navigate via headings. Add a "Skip to Content" link at the start of
the document hidden offscreen by CSS, and made visible on focus, so
it's available to keyboard and screen reader users: <a
class="accessible" href="#main">[Skip to Content]</a>
- This form control has no associated LABEL element. Add a LABEL tag
with the FOR attribute set to the id of this control. This allows
screen readers to tell the user what each control does.
- This form has fields without LABEL elements or TITLE attributes.
Screen readers use LABEL elements or TITLE attributes to describe form
fields to non-sighted users. Without these, forms are very hard to use
with a screen reader. Forms designed to be completed online shall
allow people using assistive technology to access the information,
field elements, and functionality required for completion and
submission of the form, including all directions and cues.
