page considers checkpoints for web content.
It covers -
Jakob Nielsen has persuasively called
for a pragmatic approach to online accessibility, accommodating
aspirations to universal access with a recognition of
different audiences, skills and priorities.
This page does not provide a definitive set of rules or
points for validation. Instead, we've included it on the
site to encourage thought.
The following list is derived from the Checklist of
Checkpoints for Web Content Accessibility Guidelines 1.0
developed by the World Wide Web Consortium's Web Accessibility
highlighted earlier in this guide.
It is grouped by priority, with priority one being most
a text equivalent for every non-text element (eg via
alt-text) - images/graphics (inc spacers), animations,
applets, frames, scripts, audio and video. Include
redundant text links for each active region of a server-side
image map and use
client-side image maps instead of server-side image
maps, except where the regions cannot be defined with
an available geometric shape.
that all information conveyed with colour is also available
without colour, eg from context or markup.
identify changes in the natural language of a document's
text and any text equivalents (eg captions).
documents so they may be read without style sheets.
the clearest language appropriate for a site's content.
row and column headers in data tables and use markup
to associate data cells and header cells in
tables that have two or more logical levels of row or
each frame to facilitate identification and navigation.
that equivalents for dynamic content are updated when
the dynamic content changes.
that pages are usable when scripts, applets, or other
programmatic objects are turned off or not supported.
If this is not possible, provide equivalent information
on an alternative accessible page.
that foreground and background colour combinations provide
sufficient contrast when viewed by a user with "colour
deficits" or on a black & white screen
use markup rather than images to convey information,
when an appropriate markup language exists
documents that validate to published formal grammars.
style sheets to control layout and presentation
relative rather than absolute units in markup language
attribute values and style sheet property values
header elements to convey document structure and use
them according to specification
up quotations and lists (avoid quotation markup for
formatting effects such as indentation)
do not cause pop-ups or other windows to appear and
do not change the current window without informing the
large blocks of information into more manageable groups
where natural and appropriate
identify the target of each link
metadata to add semantic information to pages and sites.
information about the general layout of a site (eg a
site map or table of contents).
navigation mechanisms in a consistent manner.
not use tables for layout unless the table makes sense
when linearised. If a table is used for layout, do not
use any structural markup for the purpose of visual
the expansion of each abbreviation or acronym in a document
where it first occurs.
the primary natural language of a document.
a logical tab order through links, form controls, and
keyboard shortcuts to important links (including those
in client-side image maps), form controls, and groups
of form controls.
include non-link, printable characters (surrounded by
spaces) between adjacent links
navigation bars to highlight and give access to the
information so that users may receive documents according
to their preferences (eg language, content type, etc)
related links and identify the group (for user agents)
search functions are
provided, enable different types of searches for different
skill levels and preferences
distinguishing information at the beginning of headings,
paragraphs and lists
information about document collections (ie documents
comprising multiple pages)
text with graphic or auditory presentations where they
will facilitate comprehension of the page
a style of presentation that is consistent across pages.