Accessibility

This website is designed by Miramedia in order to be accessible to all users and to comply with the Disability Discrimination Act (DDA).

The DDA was passed in 1995 (updated 1999. 2001 & 2005) to end the discrimination facing many disabled people, including when using the Internet. The Web Content Accessibility Guidelines (WCAG) were set out in 1999 to give checkpoints for accessible web design that complies with the DDA.

This website follows the Priority 1 guidelines relating to accessibility as set out by the WC3. Please see below for a summary of how the site meets these terms.

All pages on this website have also been validated for XHTML and CSS, with accordance to the web standards set out by the W3C.

Further information regarding the DDA can be found at the Disability Rights Commission.
 

> Accessibility and www.rslive.co.uk

Priority 1 Guidelines: A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.
 

> Priority 1 Guidelines

Provide content that, when presented to the user, conveys essentially the same function or purpose as auditory or visual content

  • Provide redundant text links for each active region of a server-side image map.
    • N/A - no image maps are used in the RS website.
  • Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation.
    • N/A - no visual tracks are used in the RS Live website. The only multimedia presentation is a Flash animated header to the site for design purposes only.
  • For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation.
    • N/A - as above.

Don't rely on color alone

  • Ensure that all information conveyed with colour is also available without colour, for example from context or markup.
    • All information can be read when the website is viewed in black and white.

Clarify natural language usage

  • Clearly identify changes in the natural language of a document's text and any text equivalents (e.g. captions).
    • The language of the website is clearly stated as English in the html tags.

Create tables that transform gracefully

  • For data tables, identify row and column headers.
    • N/A - The RS Live website does not contain any tables for design or content.
  • For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.
    • N/A - The RS Live website does not contain any tables for design or content.

Ensure that pages featuring new technologies transform gracefully

  • Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document.
    • All of the information on the RS Live website is still viewable without the style sheets.
  • Ensure that equivalents for dynamic content are updated when the dynamic content changes.
    • N/A.
  • Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.
    • The scripts used in the RS Live website only affect the design and not content, so when scripts are not supported all content is still viewable.

Ensure user control of time-sensitive content changes

  • Until user agents allow users to control flickering, avoid causing the screen to flicker.
    • The RS Live website does not cause screen flickering.

Ensure direct accessibility of embedded user interfaces

  • Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.
    • N/A.

Design for device-independence

  • Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
    • N/A - no image maps are used in the RS Live website.

Use W3C technologies and guidelines

  • If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.
    • The RS Live has a complete text-only version of the site.

Provide context and orientation information

  • Title each frame to facilitate frame identification and navigation.
    • N/A - no frames are used in the RS Live website.

Ensure that documents are clear and simple

  • Use the clearest and simplest language appropriate for a site's content.
    • RS Live has strived to make the language as clear and simple as possible for all users.

At present, RS Live does not follow all of the Priority Two or Three guidelines. However, we strive to make the website accessible to all. If you are not able to view any crucial content of this site please contact us.

d