This is the official accessibility statement for Gallant 2000. If you have any questions or comments, please call us. Our email is gallant2000ltd@btconnect.com. Other contact details are available on our contact page.

Access keys

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.

All pages on this site define the following access keys:

Access key 5 is used on child pages such as text descriptions of images to return to the parent page.

Access key 2 is used on pages with a full menu to skip to the main content.

Standards compliance

All pages on this site comply with the Gallant standard, levels 1, 2, and 3. This is based on the WCAG framework but takes an even more rigorous approach, as we believe that compliance is simply the starting point…

One of the requirements of the Gallant standard is an Accessibility Strategy. We monitor our performance against our strategy and welcome feedback.

All pages on this site are Bobby AAA approved, complying with all the Bobby guidelines. This is always a judgement call; many accessibility features can be measured, but many can not. We have reviewed all the guidelines and believe that all these pages are in compliance .

All pages on this site is WCAG AAA approved, complying wih all priority 1, 2, and 3 guidelines of the W3C Web Content Accessibility Guidelines. Again, this is a judgement call; many guidelines are intentionally vague and can not be tested automatically. We have reviewed all the guidelines and believe that all these pages are in compliance.

All pages on this site validate as XHTML 1.1 Strict. This is not a judgement call; a program can determine with 100% accuracy whether a page is valid XHTML. For example, check this page for XHTML validity.

All pages on this site use validated CSS. Again, this is not a judgement call and can be machine checked. Our stylesheets have been validated using the W3C’s CSS validation service.

All pages on this site use structured semantic markup. H1 tags are used for main site title, H2 tags for page titles, H3 tags for subtitles within the main content. For example, on this page, JAWS users can skip to the next section within the accessibility statement by pressing ALT+INSERT+3.

Navigation aids

All pages have rel=previous, next, up, and home links to aid navigation in text-only browsers. Netscape 6 and Mozilla users can also take advantage of this feature by selecting the View menu, Show/Hide, Site Navigation Bar, Show Only As Needed (or Show Always).

All pages have a logical tabindex through links, taking you first to the skip to content link, then through any links in content, and finally through menu items.

Links

Many links have title attributes which describe the link in greater detail, unless the text of the link already fully describes the target (such as the headline of an article).

Links are written to make sense out of context.

Images

All content images used in this site include descriptive ALT attributes. Purely decorative graphics include null ALT attributes. No graphics are used for layout purposes; if they were, they would also include null ALT attributes.

Complex images include LONGDESC attributes or inline descriptions to explain the significance of each image to non-visual readers.

Visual design

This site uses cascading style sheets for visual layout.

Alternate stylesheets are available, for example, high contrast, and white on black. There is a stylesheet for print that removes the menu and non-informational graphics. You can also use no styling, or choose your own.

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.

Credits

Thanks to Mark Pilgrim of Dive into Accessibility for making his accessibility statement publicly available. Our statement is based on his original text.

If you would like more information about web accessibility, please contact us — or an excellent way of starting your own learning would be to google for “accessibility joe clarke” or “accessibility mark pilgrim”.