The Odyssey Group website is committed to ensuring accessibility of its Web site for people with disabilities. All the pages on our Web site will conform to W3C/WAI's Web Content Accessibility Guidelines 1.0, Conformance Level Double A. A summary of these guidelines is prived below.

1. 1. Statement of commitment

1.1. The ODYSSEY GROUP is committed to making its output as accessible as possible to all audiences (including those with visual, hearing, cognitive or motor impairments) to fulfil its public service mandate and to meet its statutory obligations defined by the Disability Discrimination Act.
1.2. Unless it can be shown to be technically or practically impossible, all content MUST be made accessible.

2. Scope

2.1 These standards relate to the Odyssey Group Website and other sites operated by The Odyssey Group

3. Editorial content

3.1 You MUST provide an accessible alternative to any potentially inaccessible content, including all plug-in content, UNLESS this can be proven to be technically or practically impossible.
3.1.1. An accessible alternative is defined as one that meets the information, educational and entertainment objectives of the original content.
3.1.2. If your content relies on Flash, other plug-ins or JavaScript to deliver accessibility features, you MUST still provide an HTML alternative that does not rely on Flash, other plug-ins or JavaScript. See Production and Delivery of Plug-in Content Standards.
3.2. All accessible alternative content MUST be updated in-line with and at the same time as the original content.
3.3. You SHOULD divide large blocks of information into manageable chunks e.g. use short paragraphs.
3.4. Lines SHOULD NOT be longer than 70 characters (for the browser default font setting) including the spaces in between words, except where the language of the website is:
 Arabic, German, Serbian, Russian, Persian, Urdu, Pashto, Hindi, Bengali, Sinhala, Chinese (simplified and traditional), Welsh, Polish, Ukrainian, Greek, Macedonian, Bulgarian, or Dutch.
 Or the line is a URL or code fragment.
3.5. You MUST provide an appropriate text equivalent for each non-text element of the core content. See the Textual Equivalents Standards.
3.6. You SHOULD specify the expansion of each abbreviation or acronym in a document where it first occurs.
3.7. All pages MUST use heading elements. See Semantic Mark-up Standard.
3.8. You SHOULD use HTML text rather than images wherever possible.

4. Language/Style

4.1 You SHOULD use plain language and avoid jargon.
4.2. Where the language in the document changes (e.g. from English to Welsh), you MUST indicate this with a tag containing a Lang attribute.
4.3. All text of more than two lines MUST be left aligned (if published language is naturally ranged left e.g. English), except for tabular data and where the formatting is integral to the meaning of the text, e.g. poetry.

5. Editorial Images

5.1. Editorial content MUST make sense without reference to images or diagrams, UNLESS the subject matter can only be displayed via images (e.g. a 'spot the difference' game).
5.2. Instructional images SHOULD make sense without text e.g. a user must be able to follow a set of diagrammatical instructions without the help of a text explanation.
5.3. You MAY support instructions with diagrams.
5.4. Where appropriate, you SHOULD use pictures and symbols in addition to text.
5.5. You SHOULD support your "calls to action" with icons.
5.6. You MUST NOT use ASCII art.

6. Movement

6.1. You MUST NOT cause an item on the screen to flicker – see Flicker Guidelines.
6.2. You MUST NOT use blinking, flickering or flashing objects.
6.3. You MUST provide a mechanism to freeze any movement on the page UNLESS there is no alternative to the movement.

7. Audio and Video Content (A/V)

7.1. You SHOULD provide subtitles/captions (that can be turned off and on) for all AV content. This includes AV content featured in interactive features or Flash games.

8. Frames

8.1. You MUST describe the purpose of frames and how they relate to each other if this is not obvious using the frame titles alone.

9. Forms

9.1. You MUST provide a "submit" button on all forms.

10. Documents

10.1. All PDFs MUST comply with Adobe's accessibility guidelines.

11. Links

11.1. Where possible all pages SHOULD provide users with the option to bypass groups of related links e.g. "Skip to Content", "Skip to Local Navigation" and "Skip to Global Navigation". This option SHOULD be the first thing found by screen readers i.e. first thing inside the body tag.
11.1.1. "Skip to Content"
11.1.2. "Skip to Global Navigation"
11.1.3. "Skip to Page Navigation"
11.2. You MUST provide redundant text links for each active region of an image map.
11.3. All links to video content SHOULD be accompanied by an image that encapsulates what the programme is or is about.

12. Accessibility Options

12.1. Page layout MUST accommodate the enlarging of text.
12.2. You MUST use style sheets to control layout and presentation.

13. Structure/Function/Layout

13.1. All text based content SHOULD be published on a plain solid background.
13.2. You MUST NOT create periodically auto-refreshing pages in their default state, i.e. you can allow an opt-in auto-refresh.
13.3. You MUST NOT break browser back button functionality.
13.4. New windows MUST NOT be opened from a page UNLESS they are pop-up.
13.5. You MUST clearly label links (in the text of the page) which launch pop-ups so that the audience know they are launching a pop-up.
13.6. Pop-ups MUST NOT appear without being intentionally opened by the user.
13.7. You MUST provide consistent navigation – see Page Layout Standards.
13.8. You MUST clearly define the different sections of the page and ensure consistent location of screen objects. See Page Layout Standards.