Main navigation

Accessibility

The RACGP website aims to have Double-A compliance with the W3C's "Web Content Accessibility Guidelines 1.0" available at www.w3.org/TR/WAI-WEBCONTENT/. This confirms that we have taken appropriate steps to make our site accessible for certain user groups, such as users with disabilities.

These include:

• Providing a text equivalent for every non-text element (eg. via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations, applets and programmatic objects, ASCII art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
• To ensure that all information conveyed with colour is also available without colour, for example from context or markup.
• Clearly identify changes in the natural language of a document's text and any text equivalents (eg. captions).
• Organise 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.
• Ensure that equivalents for dynamic content are updated when the dynamic content changes.
• Until user agents allow users to control flickering, avoid causing the screen to flicker.
• Use the clearest and simplest language appropriate for a site's content.
• Provide redundant text links for each active region of a server-side image map.
• Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
• For data tables, identify row and column headers.
• For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.
• Title each frame to facilitate frame identification and navigation.
• Ensure that pages are useable 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.
• 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.
• For any time-based multimedia presentation (eg. a movie or animation), synchronise equivalent alternatives (eg. captions or auditory descriptions of the visual track) with the presentation.

Publication Date: 1 September 2005