1.15 Ensure that scripts and applets that provide the only source of important functionality are directly accessible or compatib
Contents
WAI checkpoint 8.1
Full WAI text: "Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]"
Scripts and applets are types of programmatic objects. These are pieces of functionality written in languages other than HTML, to provide dynamic or interactive behaviour ranging from simple visual effects to mini applications.
Some examples are enhanced functionality like pop-up menus coded in DHTML, form input validation routines written in JavaScript and interactive applications such as tax calculators or games written in Java or Macromedia Flash.
Programmatic elements should either be inherently accessible or should include features that ensure they are usable with assistive technologies.
Assistive technologies enable users to provide inputs and perceive outputs where they can't do so using technologies like the mouse, keyboard or monitor screen. For example, blind users may use a screen reader, which is a program that interprets the text contents of the screen and outputs this either to a speech synthesiser or a Braille display. Users with low acuity vision may use a screen magnifier program to enlarge a selected portion of the screen. People with motor impairments may require a special keyboard or a pointing device controlled by a joystick or by head movements.
Rationale
Ideally programmatic elements should be directly accessible so the widest audience can use them without having to resort to assistive technologies. This is not always possible, as many browsers or operating systems do not include adequate accessibility features. In this case, accessibility features which are provided in programming technologies and supported by assistive technologies should be included in programmatic elements.
Direct accessibility is desirable in situations where the user wants to access a service or information delivered through HTML pages but can't use their assistive devices or technologies because it is not practical or feasible. For example, using a screen reader to interact with a kiosk in a public place. This would be impossible because screen readers are typically installed on the user's PC and configured it to suit their needs.
Directions and Techniques
Write directly accessible applets
See WAI recommended techniques for writing directly accessible applets
If you use Java to create applets, consult the Java Look and Feel Guidelines from Sun Microsystems
Java has inherent accessibility features. Ensure that you have provided for input device independence using them. Refer to Sun guidelines on accessibility features provided in Java for details on using them.
How you could check for this:
Test programmatic elements with assistive technologies
Testing with assistive technologies such as screen readers, screen magnifiers, special pointing devices will show whether they are directly accessible or compatible with assistive technologies. You should consider testing with real users and if you do this, be sure to follow a structured user test methodology.
Test programmatic elements with keyboard only navigation
Test programmatic elements with audio browsers
Guidelines for Web Accessibility - Priority 1- 1.1 Provide a text equivalent for every non-text element
- 1.2 Ensure that information does not rely on colour perception
- 1.3 Avoid causing the screen to flicker
- 1.4 Provide an auditory description of the visual information in multimedia presentations
- 1.5 For multimedia, ensure that timing of alternative descriptions is synchronised with the presentation
- 1.6 Use the clearest and simplest language appropriate
- 1.7 Identify language changes in text
- 1.8 Ensure that equivalents for dynamic content are updated when the dynamic content changes
- 1.9 For data tables, identify row and column headers
- 1.10 For complex data tables, use mark-up to associate data cells and header cells
- 1.11 Add titles to frames
- 1.12 Ensure that documents can be read without style sheets
- 1.13 Provide text links to emulate server-side image maps
- 1.14 Use client-side image maps rather than server-side image maps where possible
- 1.15 Ensure that scripts and applets that provide the only source of important functionality are directly accessible or compatib
- 1.16 Ensure that pages are usable without support for scripts, applets, or other programmatic objects
- 1.17 If you cannot make a page accessible, provide an equivalent accessible page
