If the navigation is not visible, this link will take you to it.
Checklist
Please note that whilst this checklist follows the WCAG 1.0 specification closely, such a conformance is not a guarantee for accessibility. Many more details go into creating a site which does not hinder anyone, but as a much published standard we have used the WCAG as our baseline.
This document was last revised Wednesday, 6th of October 2004.
WCAG 1.0, Priority 1 Checklist
| No. | Complies | Comment |
|---|---|---|
| 1.1 | Yes |
All graphical elements have been supplied with text equivalents
through the use of the alt and – if need be –
the longdesc attributes. The content of these are sensible
and works well in non-visual user agents.
|
| 2.1 | Yes |
Colour has in general not been used to carry information on this site.
The exception is the hover-effect on links, but we have kept the
underline, and added extra title information when needed.
|
| 4.1 | Yes |
Links pointing from one linguistic alternative to another have been
clearly marked using the hreflang attribute. All
content which do not match the overall natural language of a document has
been marked with the lang attribute.
|
| 6.1 | Yes | Whilst CSS has been used extensively for layout purposes, all content linearise properly and is fully available without style-sheets being present or supported. |
| 6.2 | n/a | No dynamic elements are used on this site. |
| 7.1 | Yes | All possible effort has been put into avoiding constructions which may cause flicking of the screen. This includes choosing a not quite white background colour in an attempt to avoid difficulties that spring from low horizontal refresh rates on older monitors and graphics cards, alternatively TV sets. |
| 14.1 | Yes | The language used have been chosen to remain clear while still effectively communicate. Whether this has been successful is difficult to measure in any objective manner. All documents have been checked for syntactical and grammatical errors. |
| 1.2 | n/a | No server-side image maps have been used. |
| 9.1 | n/a | See 1.2 |
| 5.1 | Yes |
All tables use
HTML's
th and td elements to identify column- and
row headers.
|
| 5.2 | Yes |
Data tables present on this site are generally non-complex. The
HTML
thead, and tbody elements have been used to
group rows.
|
| 12.1 | n/a | No frames have been used on this site. |
| 6.3 | n/a | No scripts have been used on this site. |
| 1.3 | n/a | No multimedia presentations have been used on this site. |
| 1.4 | n/a | See 1.3 |
| 11.4 | n/a | The above Priority 1 checkpoints are all either non applicable or satisfied. |
WCAG 1.0, Priority 2 Checklist
| No. | Complies | Comment |
|---|---|---|
| 2.2 | Yes | The background and foreground colours are chosen for maximum contrast whilst still minimising unpleasant effects on low end monitors due to low refresh rates. |
| 3.1 | Yes | Markup, not images, have been used for all appropriate purposes. |
| 3.2 | Yes | All HTML and CSS data validate against published, formal, standards as described in the about this site document. |
| 3.3 | Yes | All layout has been implemented with CSS. |
| 3.4 | Yes |
Relative units - em, px, and % -
has been used for all purposes. All documents using the px
unit has been extensively tested and the content deemed to render
satisfactory in a variety of resolutions and window sizes. No font size
has been set using the px unit. Note that the right
hand menu has been given a pixel-based width equal to that of the
logotype. We have tested this, and found it to be working well up to
UA text scaling factor of 450%. Using
third party screen magnifying devices present no difficulty.
|
| 3.5 | Yes |
Header elements – h1 through h6 –
has been used to mark up all logical header information. These
elements have not been used for any other purpose.
|
| 3.6 | Yes |
Lists, and list items, have been structured using the ol,
ul, dl, li, dt and
dd elements. These elements have not been used for
other purposes.
|
| 3.7 | Yes |
Quotations have been marked up using blockquote and
q according to their nature. These elements have not been
used for other purposes. Citations have been included if the source can
be reached by an
URI.
|
| 6.5 | n/a | No dynamic content exist on this site. |
| 7.2 | n/a | No content blink or otherwise move about. |
| 7.4 | n/a | No document auto-refreshes periodically or at all. |
| 7.5 | Yes | Only server-side redirects per the HTTP 1.1 specification is in use on this site. |
| 10.1 | Yes | No links open in new windows, either by Javascript or HTML/ XHTML. |
| 11.1 | Yes | W3C technologies have been used throughout the site; the latest versions when appropriate. |
| 11.2 | Yes | No deprecated elements of W3C specifications have been used. |
| 12.3 | n/a | No large groups of information exist which has not been already divided into separate documents. |
| 13.1 | Yes |
Every link has been clearly marked through the use of natural language
as link texts. These are meaningful out of context. Additional
information has been provided through the title attribute.
|
| 13.2 | Yes |
Meta-data has been provided for every single document by way of the
HTML
meta element and
Dublin Core.
|
| 13.3 | Yes | A comprehensive site map has been provided. |
| 13.4 | Yes | Navigational mechanisms are consistent across all documents. |
| 5.3 | n/a | No tables have been used for layout purposes. |
| 5.4 | n/a | See 5.3 |
| 12.2 | n/a | See 12.1 |
| 10.2 | Yes | All form controls have labels, and these are correctly positioned. |
| 12.4 | Yes | All form controls have labels, and these are explicitly associated. |
| 6.4 | n/a | See 6.3. |
| 7.3 | n/a | No content move about on this site. |
| 8.1 | n/a | See 6.3. |
| 9.2 | n/a | See 6.3. |
| 9.3 | n/a | See 6.3. |
WCAG 1.0, Priority 3 Checklist
| No. | Complies | Comment |
|---|---|---|
| 4.2 | Yes |
All abbreviations and acronyms have been clearly marked up as such
by use of the abbr and acronym elements
from
HTML. In
each case the title attribute has been used to specify
the expansions. If the natural language of the expanded form is different
from the document language, this has been marked by the
lang attribute.
|
| 4.3 | Yes |
The primary, natural, language has been identified through the use of
HTTP's
Content-Language header, as well as
HTML
lang.
|
| 9.4 | Yes | A logical tab order has been created, allowing users of supporting browsers to cycle in a natural order through the navigational and content links. |
| 9.5 | Yes | Keyboard shortcuts have been provided to the most essential documents on the site. The details of these shortcuts can be found in the help section. |
| 10.5 | Yes | A single, non-link but printable, character - specifically ',' (comma) - has been included between every adjacent link. |
| 11.3 | n/a | Only one language - English - is available. |
| 13.5 | Yes | A text-compatible navigational bar has been included to clearly point out where in the document hierarchy the user is at every time. |
| 13.6 | Yes |
Note: the example use to group elements in the Web Content
Accessibility Guidelines technical examples is invalid under
HTML 4.01 Strict. We
have, instead, chosen to group the navigation using the DIV
element and supplying this with a unique identification string.
|
| 13.7 | Yes | Simplified search functions are in place on all pages, and a more advanced search form can be reached by way of the sitemap or navigation. |
| 13.8 | n/a | See 13.7 |
| 13.9 | Yes | |
| 13.10 | n/a | No ASCII art has been used on this site. |
| 14.2 | In cases where we have judged it necessary, graphical elements have been used to emphasise the content. | |
| 14.3 | Yes | The look-and-feel of this site is identical from document to document. |
| 1.5 | n/a | No image maps are in use on this site. |
| 5.5 | Yes | All tables have been provided with comprehensive summaries. |
| 5.6 | Yes | All table headers has been provided with abbreviations. |
| 10.3 | n/a | Text on this site has not been laid out in columns. |
| 10.4 | Yes | Form controls have default, place-holding, values. |