- All pages on this website currently define the following access keys:
1 - Home page
0 - This accessibility statement
- In 2004 I intend to add additional access keys to all pages.
- Most browsers support jumping to specific links by typing access keys defined on the website. On Windows, you can press ALT + an access key; on Macintosh, you can press Control + an access key.
- I am aware that I have some page refresh links using the structure
<META HTTP-EQUIV="REFRESH" CONTENT="0;URL=index.shtml">, and I am looking at replacing these during 2004.
- This website uses a small number of 'related links' to aid navigation in text-only browsers. For instance these appear at the top of the page when viewed with Lynx. Netscape 6 and Mozilla users can also take advantage of this feature by selecting on the View menu: Show/Hide, Site Navigation Bar, Show Only As Needed (or Show Always). I intend to extend the use of relative links in this website during 2004.
- All of my Land's End to John O'Groats pages have
- All of the pages on this website have
- All photographs and images used in this site include descriptive
ALT attributes, except for purely decorative graphics which have null
- This website uses a cascading style sheet to define its visual layout.
- If your browser or browsing device does not support stylesheets at all, the content of each page is still readable.
- The HTML code for my menu system appears at the end of the HTML file, and therefore does not clutter the start of the display on a text only browser.
- Acronyms (like HTML) appear on visual browsers with a dotted line underneath them. If you hovver over the acronym, an expanded explanation of the acronym is displayed.
- This site does not yet use relative font sizes. This is an area that I intend to improve in 2004.
Natural Language Identification
- All pages on this website specify the natural language of their content. This helps users in a number of ways. One example is that search engines can use this information to select which pages to provide in their results when a user has specified a preferred language. Another example is that speech synthesisers can determine how to pronounce web page content more easily. I identify the natural language in the HTML code just after the DOCTYPE declaration using the
<HTML LANG="en"> structure. Almost the whole site is written in English (
LANG="en") with only a couple of pages in Czech (
- For foreign names and words embedded within a paragraph of a natural language, I use the
<SPAN LANG="cs">Václav Havel</SPAN> construction within the paragraph.
- All pages on this site are compliant to the W3C HTML 4.01 Strict standards. This can be fully verified by automated tests at the W3C website. See my standards compliancy page for more details.
- All pages on this site are compliant to the W3C CSS standards. This can also be fully verified by automated tests at the W3C website. See my standards compliancy page for more details.
- This website is not yet compliant to the W3C Accessability Guidelines. I will be working on this during 2004. See my standards compliancy page for more details.
- All pages on this site use structured semantic markup.
<H1> tags are used for main titles,
<H2> tags for subtitles. For example, on this page, JAWS users can skip to the next section within the accessibility statement by pressing ALT+INSERT+3.
- 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.
W3C Accessibility guidelines V1.0
In the future I would like to be able to claim compliancy against the W3C Accessability Guidelines V1.0. These 14 guidelines should each be considered when authoring a web page:
- Provide equivalent alternatives to auditory and visual content
- Don't rely on colour alone
- Use markup and style sheets and do so properly
- Clarify natural language use
- Create tables that transform gracefully
- Ensure that pages featuring new technologies transform gracefully
- Ensure user control of time-sensitive content changes
- Ensure direct accessibilty of embedded user interfaces
- Design for device-independence
- Use interim solutions
- Use W3C technologies and guidelines
- Provide context and orientation information
- Provide clear navigation mechanisms
- Ensure that documents are clear and simple
Depending on the level of compliancy that I achieve against the guidelines, I will be allowed to display one of the following W3C logos on each page: