Venturers - South Australia

7.1

Until user agents allow users to control flickering, avoid causing the screen to flicker.

• Not applicable.

7.2

Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off).

• Not applicable.

7.3

Until user agents allow users to freeze moving content, avoid movement in pages.

• The only movement which occurs is the opening and closing menus. These are user-triggered events which don’t happen on their own.

7.4

Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages.

• Not applicable.

7.5

Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects.

• Not applicable.

8.1

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

To quote the W3C:
If an applet creates motion, developers should provide a mechanism for freezing this motion.

• Applets are used for the puzzles.
  I know of no way to freeze the motion. In fact there is no need to freeze motion.
• After saying that. . . there is no reason that a device other than a mouse (such as a pointer)  should not be used to move the puzzle images. Any device that can interact with a Java applet may be used.

9.1

Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.

• Client-side image maps are used.

9.2

Ensure that any element that has its own interface can be operated in a device-independent manner.

• Not applicable.

9.3

For scripts, specify logical event handlers rather than device-dependent event handlers.

• JavaScript is used for the drop down menus.
  The menu is duplicated as text links on every page.
• For people who do not have a mouse, the whole site is accessible using the keyboard.

9.4

Create a logical tab order through links, form controls, and objects.

• The links have tabindex attributes when applicable.

9.5

Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls.

• The main links have accesskey attributes.

10.1

Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user.

• All links that open in another window have the title attribute which warns the user.

10.2

Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned.

• Labels are placed adjacent to the form.

10.3

Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.

• See 5.3 above.

10.4

Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.

• Default text is used.

10.5

Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links.

• The vertical line character is used for adjacent links. See bottom of page.

11.1

Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported.

• See checkpoint 3 above.

11.2

Avoid deprecated features of W3C technologies.

• No deprecated elements or attributes are used. All the styling is CSS, which allows users to override the styling with their own.

11.3

Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.)

• The content of images is displayed as alternative text or / and as a title.
• Translations into other languages are available from sites such as www.freetranslation.com and is mentioned on the accessibility page.

11.4

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.

• Not applicable.

12.1

Title each frame to facilitate frame identification and navigation.

• Each frame has a title.

12.2

Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone.

• Not applicable.

12.3

Divide large blocks of information into more manageable groups where natural and appropriate.

• Headings and subheadings are used.

12.4

Associate labels explicitly with their controls.

• Labels are placed adjacent.

13.1

Clearly identify the target of each link

• All links are obvious by the link text that is used. There are no “click here” or “click on the green square” type of links used.

13.2

Provide metadata to add semantic information to pages and sites.

• Meta data is provided within the header of each page.

13.3

Provide information about the general layout of a site (e.g., a site map or table of contents).

• A site map is provided.

13.4

Use navigation mechanisms in a consistent manner.

• Menus are the same on each page.

13.5

Provide navigation bars to highlight and give access to the navigation mechanism.

• We have. On each page.

13.6

Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group.

• This is accomplished by separating the content by the use of headings and subheadings.

13.7

If search functions are provided, enable different types of searches for different skill levels and preferences.

• Not applicable.

13.8

Place distinguishing information at the beginning of headings, paragraphs, lists, etc.

• Headings and subheadings are used.

13.9

Provide information about document collections (i.e., documents comprising multiple pages.).

• Not applicable.

13.10

Provide a means to skip over multi-line ASCII art.

• Not applicable.

14.1

Use the clearest and simplest language appropriate for a site's content.

• We have!

14.2

Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page.

• Not applicable.

14.3

Create a style of presentation that is consistent across pages.

•  We have!