WebCT Section Accessibility Evaluation


Please use this form to provide your accessibility evaluation report. You can send the result as an e-mail to Hadi Rangin (e-mail: hadi@uiuc.edu) or Terry Thompson (e-mail: tft@u.washington.edu) so it can be posted at the collaboration website.
You can also click on the "Print view" button and use the "Save as" option of your browser to save the result locally on your computer. Please note that the evaluation results are not saved if you are not in "Print view" mode.
Use "Edit" button to modify the information in this form.

Blackboard Evaluation Information

Rating Defintions

All requirements met for the entire collection of resources for the functional accessibility requirement.
Almost Complete
95% of the requirements are met for the entire collection ot resources for the functional accessibility requirement.
Partial Implementation
Less than 95% of the requirements are met for the entire collection of resources for the functional accessibility requirement, but greater that 40%.
Not Implemented
Less than 40% of the requirements are met for the entire collection of resources for the functional accessibility requirement.
Not Applicable
The web resource does not need to comply with the functional accessibility requirement because the requirements do not apply to the content in the resource.


N.1 Unique Titles

(Best practices for Unique Titles)

Each resource in a website needs to have a unique title.

N.2 Major/Minor Topics

(Best practices for Major/Minor Topics)

All major/minor topics with in a web resource have a heading (h1-h6) before the section and the headings provide useful orientation information to the content on the page. Headings should not be used to stylize text.

N.3 Links

(Best practices for Links)

All links indicate the target of the link. The same link text is used to point to different URIs and references to the same URI with different link text.

N.4 Image Maps

Image maps (client and server side) have redundent text links

N.5 Navigation Bars

(Best practices for Navigation Bars)

Are navigation bars marked up using ul and given a throuh ul.title attribute.

N.6 Dyanmic Menus

(Best practices for Dyanmic Menus)

Dynamic menus are created using CSS, rather than scripting techniques.

N.7 Form Controls

(Best practices for Form Controls)

Do all form controls of have labels.

N.8 Groups of Controls

(Best practices for Groups of Controls)

Do groups of form controls have labels (fieldset/legend) or headings (h2-h6).

N.9 Language

(Best practices for Language)

Are changes in language indicated in markup using .lang attributes.

N.10 Data Tables

(Best practices for Data Tables)

Data tables use caption elements, th elements, td.id attributes and td.header attributes to title and indicate cell relationships.

N.11 Lists

(Best practices for Lists)

Lists are markuped using ul, ol or dl lists.

N.12 Frames

(Best practices for Frames)

Frames have useful titles for navigation (frame.title). Frames used for client/server interaction or do not contain vieable content are marked as title="hidden".

Text Equivalents

E.1 Images

(Best practices for Images)

All images have text descriptions

E.2 Objects/Applets

All OBJECTs/APPLETS have text descriptions and have alternative accessible content


Y.1 Font Size

Liquid page designs: Does content reflow when browser text zooming features change font size. As content reflows the user should not need to use the horizontal scroll feature to view content.

Y.2 Automatic Reflow

Liquid page designs: Does content reflow when a graphical window width changes. As content reflows the user should not need to use the horizontal scroll feature to view content.

Y.3 User Stylesheet

When the user applies their own style sheet is the page still usable (i.e. high contrast sytlesheet).

Y.4 Background Images

Background images used for styling content, rather than inline images.

Y.5 Stylized Text

Images are not used to stylize text, except in logos and other branding icons.

Y.6 In-line Styling Elements

All content styled through stylesheets, no in-line styling elements of content (B, I, FONT, CENTER, BLINK, MARQUEE, ...).

Y.7 Dynamic pseudo-classes

(Best practices for Dynamic pseudo-classes)

Dynamic pseudo-classes like :hover, should have corresponding :focus dynamic pseudo-class selectors.

Scripting and Automation

R.1 Keyboard

Support the keyboard. Make sure all actions can be operated through only the keyboard.

R.2 Dynamic Content

Dymanic text content hidden or revealed using CSS techniques.

R.3 OnChange Event

No OnChange events on SELECT elements.

R.4 Link Hover Styling

Mouse roll over effects should be done through CSS techniques and not through javascript swapping image references.

R.5 Dynamic Menus

(Best practices for Dynamic Menus)

Pull down or pop out menus should be created using CSS techniques and not through javascript positioning.

R.6 Timed Responses

Resources with timed responses need to provide a means to alert the user that a timed response is requiredand a means to extend the response time

R.7 Animations

Animations can be paused and restarted under user control

R.8 Flicker

No content causes flickering between 2-55 Hz

R.9 Programmable Content

Provide an accessible alternative for embedded Java Applets, Fash and other APPLETS and OBJECTS


M.1 Text Transcripts

Text transcipts of audio, video+audio and other multimedia that include sound are available

M.2 Synchromization

M.3 Links to Players


S.1 HTML/xhtml Version

DOCTYPE needs to be specified for validation of the HTML/xhtml code. Valid code is important for interoperability.

S.2 Language

Default language is needed for speech renderings to speak the correct language and for HTML/xhtml version validation

S.3 Character Encoding

Character encoding is important for checking HTML validation

S.4 http://validator.w3.org/

(Best practices for http://validator.w3.org/)

Invalid documents reduce interoperability and documents may not render correctly by some user agents.