Accessibility Statement
- home
- » Accessibility Statement
The Berlitz Brighton website has been designed with accessibility in mind, coded to strict standards to ensure that it operates across multiple platforms and browsers, to enable all users to access content, regardless of any personal disability.
This policy applies only to web pages on the Berlitz Brighton website that make use of standard templates (ie pages that have the same structure, navigation and design as this one).
Access keys
Most browsers support jumping to specific links by typing keys defined on the website.
On Windows, press ALT + an access key then press enter
On Macintosh, press CTRL + an access key then press enter
Pages on this site use the following access keys for common tasks:
- Access key S : Skip to content
- Access key 0 : Accessibilty Statement
- Access key 1 : Home page
- Access key 2 : News
- Access key A : About Us
- Access key C : Contact Us
Standards compliance
Berlitz Brighton has tried to ensure, as far as possible, that:
- All pages on this site comply with all priority 1 and 2 guidelines of the W3C Web Content Accessibility Guidelines
- All pages on this site should validate as XHTML 1.0 Transitional
- All pages on this site use structured semantic markup. h1 tags are used for main titles, h2 tags for subtitles (and so on)
Images
All content images used in this site should include descriptive alt tags. Purely decorative graphics include null tags. Complex images may include longdesc tags or inline descriptions to explain the significance of each image to non-visual readers.
Visual design
This site primarily uses cascading style sheets for visual layout and relative font sizes, compatible with the user-specified 'text size' option in visual browsers. If you need to change the 'text size' in your web browser, instructions are available.
In Internet Explorer go to View / Text Size.
In Netscape go to View / Text Zoom.
In Opera go to View / Zoom.
If your browser or browsing device does not support style sheets at all, the content of each page should still be readable.
Accessibility references
W3 accessibility guidelines, which explains the reasons behind each guideline.
www.w3.org/TR/WCAG10W3 accessibility techniques, which explains how to implement each guideline.
www.w3.org/TR/WCAG10-TECHSW3 accessibility checklist, a developer's guide to accessibility.
www.w3.org/TR/WCAG10/full-checklist.html
Comments
If you have any questions or comments, please use our contact form.