Web Database Features and Accessibility

The following list describes the desirable and undesirable features contained in web-based databases when accessed with a screen-reader. The list of desirable features indicates features that should be readily available, while the undesirable features should either be eliminated or present some form of accommodation so that the information is accessible.

Desirable Features

easy navigation – this allows for the user to access information from one interface to the next with relative ease; there appears to be some form of consistency with the structure of all database interfaces; etc.

comprehensive site content - the content within the database contains the necessary search features and functions, plus uses terminology that is easy to understand.

content layout – the content of each database interface has a logical layout/structure when read by the screen reader.

ALT tags – should be provided for all available images, buttons, tables, search field boxes, etc. so that the user will have access to all presented information. It is important to note that all ALT tags should contain the appropriate information for the feature it is describing (e.g. the user should be able to understand the difference between an image and a button).

keyboard navigation option available – the user should automatically be able to navigate all interfaces by being able to use specific control buttons on the keyboard (Tab, Enter, Cursor Keys, etc.). When navigating by keyboard, the cursor should not skip over any pertinent function or feature (links, search fields, etc.).

skip navigation link – this should be made available so that the user can skip over sections of information that the screen-reader relays to him/her.

text only version – if the original database interface(s) heavily relies on graphics, tables, etc., a text only version of the interface(s) should be made available (via an accessible hyperlink)

HTML full-text articles – when full-text articles are made available directly from the database, the option of an HTML text article should be made available so that it can be accessed using a screen-reader.

Undesirable Features

scripting/Java Script/applets – some forms of scripting, such as Java Script, can interfere with the adaptability between the database and the screen- reader being used. Web interfaces that heavily rely on scripting to relay (visual) information should then provide a text only version of the same interface.

pop-up windows/menus – rely on active scripting in order to function properly. Information in pop-up windows/menus sometimes cannot be accessed by a screen-reader depending on the coding involved. Again, a text only version containing the same information should be made available.

redundant text links – these are confusing for the user when the screen-reader relays that there is more than one place within the web page to access the same information.

tables and/or frames – are used to help a sighted user access organized information in a comprehensive fashion. However, the information presented in a table or frame format is typically not relayed by a screen- reader in a comprehensive manner since it tends to read information presented on a page from top to bottom, left to right. If tables or frames are going to be used, then the appropriate ALT tags, labels, and HTML codes should be applied.

PDF full-text articles – if available, these typically CANNOT be accessed by a screen-reader depending if the PDF was a scanned document and/or relies on images. Some PDF articles can be accessed if the computer being used as access to Adobe 5.0. An HTML full-text article option should be made available as an alternative to the PDF format.

images – cannot relay meaningful information via a screen-reader unless the appropriate ALT tags have been attached that explain what is involved. Interfaces that heavily rely on image-based information are not helpful for a non-sighted user. Images that support the design of the web interface, but do not serve a particular purpose should be labelled accordingly.

R. Caldwell
UW Library Intern
April 19, 2004

Information Resources Management Committee
.
June 25, 2007