- All pages on this site follow priorities 1 & 2 guidelines of the W3C Web Content Accessibility Guidelines.
- All pages on this site validate as XHTML 1.0 Strict.
- All pages on this site use structured semantic markup.
H2tags are used for main titles,
H3tags for subtitles. For example, on this page, JAWS users can skip to the next section within the accessibility statement by pressing ALT+INSERT+3.
Web pages on http://www.earl-thompson.co.uk include 4 different areas:
- A header bar that includes the main navigation between sections of the site,
- A "side bar" that may contain navigation for pages in the current section,
- A main content area,
- A footer.
When CSS (Cascading Styles Sheet) are not applied to a document (or when using a screen reader), the 4 areas are read in the above order.
This site uses the
accesskey attribute. Most browsers support jumping to specific links by typing keys defined on the web site. On Windows, you can press ALT + an access key; on Macintosh, you can press Control + an access key.
Note: Internet Explorer requires you to press ALT + an access key + Enter to access linked documents.
This site has been built with a dedicated print stylesheet. This ensures that printed pages only contain information applicable to print and also expands upon the text by providing URLs of items linked to within the text.
- Unless they are purely decorative items, all images used on this web site have suitable
- Content should be usable/accessible with images "off" (disabled).
- Many links have title attributes which describe the link in greater detail, unless the text of the link already fully describes the target.
- Links are written to make sense out of context.
- The first link in every document is a "SkipNav"; it is to skip directly to what is considered the main section of the page (the content). We have implemented this feature in a way that it allows Internet Explorer users to tab through (past that target link).
- URLs are permanent whenever possible.
- All form controls are appropriately and explicitly labelled.
- We provide an email address as an alternative form of access for our online forms.
- Forms on this site can be accessed through an access key (1).
- Form validation routine does not rely on client-side script.
- We are using non obtrusive client-side scripts.
Pop up Windows
- Browsers with Popup Blockers should be able to access these external documents.
- This site uses cascading style sheets for visual layout.
- This site uses only relative font sizes, compatible with the user-specified "text size" option in visual browsers.
- If your browser or browsing device does not support stylesheets at all, the content of each page is still readable.
- Any information conveyed through the use of color is also available without color (i.e. text based).
How to modify this site to fit your needs
These links explain the many ways you can make the web more accessible to you.
- W3 accessibility guidelines, which explains the reasons behind each guideline.
- W3 accessibility techniques, which explains how to implement each guideline.
- W3 accessibility checklist, a busy developer's guide to accessibility.
- U.S. Federal Government Section 508 accessibility guidelines.
- JAWS, a screen reader for Windows. A time-limited, downloadable demo is available.
- Home Page Reader, a screen reader for Windows. A downloadable demo is available.
- Lynx, a free text-only web browser for blind users with refreshable Braille displays.
- Links, a free text-only web browser for visual users with low bandwidth.
- Opera, a visual browser with many accessibility-related features, including text zooming, user stylesheets, image toggle. A free downloadable version is available. Compatible with Windows, Macintosh, Linux, and several other operating systems.
- HTML Validator, a free service for checking that web pages conform to published HTML standards.
- Web Page Backward Compatibility Viewer, a tool for viewing your web pages without a variety of modern browser features.
- Lynx Viewer, a free service for viewing what your web pages would look like in Lynx.