Inclusive Design Research Centre

Adaptive Technology Resource Centre
University of Toronto

No compromises

• No "special" accommodation
• Transparent inclusion

Viewing a Document

• sizing up a document at first glance
• the overall sense
• inventory of content
• what is emphasized
• anything of personal interest
• organization/structure
• where are we
• zero in on item of interest

Challenges

• obtaining an overview and determining the structure of the document,
• orienting and moving to desired sections of the document or interface, and
• obtaining translations of graphically presented information (i.e., animation, video, graphics).

Quicktips

• Images & animations. Use the alt attribute to describe the function of all visuals.
• Image maps. Use client-side MAP and text for hotspots.
• Multimedia. Provide captioning and transcripts of audio, descriptions of video, and accessible versions in case inaccessible formats are used.
• Hypertext links. Use text that makes sense when read out of context. For instance, do not use "click here."
• Page organization. Use headings, lists, and consistent structure. Use CSS for layout and style where possible.
• Graphs & charts. Summarize or use the longdesc attribute.
• Scripts, applets, & plug-ins. Provide alternative content in case active features are inaccessible or unsupported.
• Frames. Label with the title or name attribute.
• Tables. Make line by line reading sensible. Summarize. Avoid using tables for column layout.
• Check your work. Validate the HTML. Use evaluation tools and text-only browsers to verify accessibility.

File Formats

• Examples: http://snow.utoronto.ca/web-savvy/resources/index.html
• CSS
• XML, XSL

The Browser

• WAI User Agent Accessibility Guidelines
• www.w3.org/WAI
• Internet Explorer and Netscape
• Text Browsers
• Audio Browsers

The Authoring Tool

• Accessible user interface
• Creates accessible content

Keyboard Access

• Keyboard equivalents for all mouse actions
• Logical tab order between buttons and lists
• Keyboard shortcuts for commonly used objects.
• Document keyboard controls
• Do not interfere with system based equal access features
• Allow adjustable response time

Object Information

• Provide visual focus indicator, exposed to assistive technologies
• Provide information about user interface objects to assistive technologies (e.g., object is a text box with label "enter password," or a check box which is checked).

Icons

• Text label for Icons (text next to icons, tool tips, bubble help)
• Consistent use of icons

Sounds

• Provide a visual cue for all audio alerts.
• Present audio information in text format (e.g. captioning)
• Allow the user to disable sound and adjust the volume.

Display

• Provide text through an API (application programming interface) supporting interaction with assistive technology or use system text drawing tools.
• Do not use color coding as the only means of conveying information or indicating an action.
• Provide a wide variety of color and font settings. Inherit and respect system-wide color settings.
• Allow users to turn off patterned backgrounds.

Tools

• Bobby
• A-Prompt
• HTML verification