Specific Barriers to Web Access

• use mouse with difficulty
• operating system or other software provides special keyboard commands to substitute for mouse movements
• cursor control by special adaptive input device
• speech recognition software

The greatest problem associated with this disability and its adaptive technology is difficulty in guiding the cursor with precision. If links or hot images are too small (some guidelines recommend .5" by .5" as the minimum size), the user will miss the target.

Questions to consider:

• How large are the link "targets" on your pages at various screen resolutions?
• Users with mobility impairments cannot afford wasted motion, and the general public doesn't like it either. Does the design of your page force the user to jump around a lot from place to place on the screen in order to read it or navigate it?
• Some forms are not accessible without a mouse. If you provide forms to gather data from users, do you provide alternative methods such as phone and/or fax numbers, printable forms and a mailing address?

screen reader with speech synthesis (see Blind)

may prefer to use graphics as a source of information when possible because of difficulties with written English

In the international world of the web, many non-disabled users do not possess native skills with English.

Questions to consider:

• If icons are used for navigation, is their meaning clear? Are they used consistently?
• Are colors used consistently in your web pages? Do they assist in or detract from navigating your web site?

may prefer to use graphics as a source of information when possible because of difficulties with written English

• If icons are used for navigation, is their meaning clear? Are they used consistently?
• Are colors used consistently in your web pages? Do they assist in or detract from navigating your web site?

relies on text and graphics for information

Many non-hearing impaired users own computers that still do not have speakers of a high enough quality to project understandable speech or enjoyable music.

Questions to consider:

• Do your pages provide transcriptions and descriptions of all audio clips and real-time feeds?
• If you have video+audio clips or feeds on your page, are transcripts, descriptions, or captions available? (QuickTime provides a means of coordinating audio and video in order to provide synchronized captioning.)

• glasses
• large monitor
• browser configured to display large type
• screen enlarging software

Because the technology for magnifying information displayed on a computer screen is widely available, it can actually be counterproductive to design a web page with large fonts in order to accommodate this population.

Questions to consider:

• Is your web page still readable with the browser configured to display very large font sizes?
• Is your web page still readable with the screen palette set to 256 colors?
• As the user increases the degree of magnification, the amount of viewable space grows smaller, and it becomes easy to "get lost" on the page because the borders are outside the viewing space. Are navigational menus, buttons or links in a standard and consistent position on each of your pages?

• browser configured for higher contrast
• operating system configured for higher contrast

Questions to consider:

• Does your web page still convey the information you want when it is viewed with black text on a white background?
• Are the images on your page low- or high-contrast? It might help to provide a text-based description, particularly for navigational images that are low in contrast.
• Many people have difficulty interpreting text and images that do not contrast enough with their background. Do you think most people would find your page "readable" with its current color scheme?
• Is your web page still readable with the screen palette set to 256 colors?

some perceive color differences based on saturation and brightness more than on hue

saturation

intensity of a color; the lighter it is the less saturated it is

brightness

percentage of black in a color; more black makes a color less bright

hue

the color category; for example, the hue red contains many different "shades" of red

The general population shows variation in its response to color. Many non-disabled people find it unpleasant to view certain colors side by side with other colors.

Questions to consider:

• Do you use blue/yellow and red/green combinations on your web pages?
• When it is important for two colors to be distinguished on your web pages, do you provide supplementary text?
• If you use colors for navigation, do they vary in terms of brightness and saturation as well as hue?
• How does your page look when displayed in gray scale?

As the Web matures, new helper applications, search and indexing tools, and intelligent agents will be created to assist the general population in managing data found on the Web. Applications written to the HTML 3.2 specification will produce unpredictable and erroneous results when used to manage web pages that do not conform to the specification.

• Do you use HTML tags according to the HTML 3.2 specification, or have you misused some tags in order to achieve certain effects that were otherwise unavailable to you?

Although Braille display devices are available, they are too expensive for most people to own. Not all blind people know Braille, but those who want to use it usually download text files and then convert them to printed Braille.

• If an image is important to the understanding or appreciation of your web site, do you have an adequate text description of it available?
• Many non-blind as well as blind users may want to print or download your pages. How easy is it to download or print out your site as a whole?
• Not everyone enjoys installing and learning to use additional software, and many such products are inaccessible to blind people. If you provide downloadable files in non-HTML formats (like .pdf files), do you provide the same information in a text or HTML format? If the file is compressed, is it self-extracting?
• Blind people, people using text-only browsers and people who have turned off automatic downloading of images see no useful information when a web page contains no text. Does the home page of your web site contain text that could guide such a user to a non-graphical alternative?
• Do you provide text descriptions for video clips and video feeds?

Screen Reader with speech synthesizer technology is more widely used than Braille, and it usually has many features:

• reads sequentially from top to bottom, left to right (easily confused by columns)

As speech synthesis technology matures, browsers designed specifically to read HTML will make greater use of HTML tags to format output and provide options for the user. Tags that are used not according to the HTML 3.2 specification will create problems for such browsers.

• Does your site have tables that do not "read" from top to bottom, left to right? This includes the use of tables to achieve the effect of columnar text layout. If so, is the information alternatively provided in some other non-columnar format?

Screen reader:

• begins reading as soon as it loads the page

• Do you have excessive standard text or navigational tools that appear at the top of every page? It is difficult for a speech synthesizer to be manipulated to "ignore" such items.

Screen reader:

• navigation is by link, word, line or character, but not by sentence or paragraph

• If a user hops from link to link on your web page, will she or he hear "click here" repeated over and over again or is the link text brief but meaningful?

Screen reader:

• reads content of ALT attributes with images but cannot interpret images themselves

• Do you use brief but meaningful ALT text with all images? Does your ALT text describe the function of certain visual images rather than just a description of the image? (Example: "change of topic" rather than "blue line")
• If an image is important to the understanding or appreciation of your web site, do you have an adequate text description of it available?
• Blind people, people using text-only browsers and those who have turned off automatic downloading of images see no information when a web page contains no text. Does the home page of your web site contain text that could guide such a user to a non-graphical alternative?
• Do you provide text descriptions for video clips and video feeds?

Screen reader:

• cannot interpret background graphical wallpaper (no ALT attribute)

• Do you use background images that contain important content? If so, do you provide an alternate (text-based) method for viewing that content?

Screen reader:

• cannot reliably read blinking text (sometimes skips it and sometimes fixates on it)

• Many non-blind people object to blinking text on aesthetic grounds, and it can affect speech synthesizer software negatively as well. Do you really need to use it?

Screen reader:

• can search for text strings or attributes (jumping from link to link is accomplished by searching for underlined text)
• uses punctuation (periods, commas, etc.) to structure speech output

• In addition to its negative consequences for speech synthesis software, incorrect use of punctuation and spelling irritates many members of the general public. Do you use punctuation correctly and consistently throughout your site? Have you checked your spelling?