WebCT Page Accessibility Evaluation

Instructions

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). 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.

WebCT Evaluation Information

Konstantinos Yfantis, Hadi Bargi Rangin

hadi@uiuc.edu

Vista 4

Discussions

 

Hadi

hadi@uiuc.edu

Functional Web Accessibility Testing

Functional Accessibility Rating

Navigation

Conformance Rating

N.1 Does the web page have a unique TITLE element and at least one H1 that is a subset of the TITLE content?

Yes     Comment for N.1: No comments

N.2 Do menus and navigation bars have H2 elements before their links to provide orientation, and do those menu bars, exapandable menu bars, and other expansion controls change their labels based on whether they are expanded or not? NOTE: Headings can be hidden using CSS techniques based on the "position: absolute" property; do not use "display: none" or "visibility: hidden" since these techniques hide information from screen readers.

Yes     Comment for N.2: No comments

N.3 Do all major/minor topics have headings (H2-H6) and the headings provide useful orientation information to the content on the web page?
NOTE: Headings should not be used to stylize text.

  No   Comment for N.3: No sub-headings for "Selected Actions" or the group of these links: "Create Message, View Drafts, Expand All, Collapse All, Display: Threaded, Unthreaded, All Unread"

N.4 Do all links indicate the target of the links?
NOTE: The same link text should not be used to point to different URIs and references to the same URI should use the same link text.

  No   Comment for N.4: The alt/title attribute for the Preview button (the button after Post) do not match the on-screen label (Preview). Instead it says "Link: opens in new window). Screen reader can not display both on-screen label and title/at atributes at the same time. To resolve this issue, the alt/ttitle attributes should include the on-screen value as well. E.g. it should say: Preview (opens in new window).

N.5 Do all form controls of have descriptive labels?

  No   Comment for N.5: No comments

N.6 Do groups of related form controls have labels, this includes using fieldset/legend or headings (h2-h6) to indicate the relationship between the form controls?

    N/A Comment for N.6: No comments

N.7 Do changes in language of content use the LANG attribute to markup the new language?

  No   Comment for N.7: If any content needs to be entered in a language other than the default language (English), there is no mechanism to do it.

N.8 Do data tables use CAPTION elements, TH elements, TH.ID attributes and TD.HEADERS attributes to title and indicate cell relationships?

  No   Comment for N.8: The table used to display the summary of correspondences needs to support ID/HEADERS associations.

N.9 Do lists of items use UL, OL or DL list markup.?

    N/A Comment for N.9: No comments

N.10 Do frames have useful TITLE attributes?
NOTE: Frames used for client/server interaction or do not contain viable content should be marked as title="hidden".

  No   Comment for N.10: Excessive use of frames/nested frames makes the navigation and orientation very difficult regardless if they have proper namings.

N.11 Does content make sense when the page is linearized (i.e. table markup and/or stylesheets are disabled)?

Yes     Comment for N.11: However, with very difficulties.

Text Equivalents

Conformance Rating

E.1 Do all decorative images set ALT=''?
NOTE: Decorative images do not carry any content but are used purely for graphical styling (i.e. spacers, divider lines, ..), ideally these should all be moved to CSS techniques.

Yes     Comment for E.1: No comments

E.2 Do all content carrying and icon images have descriptive ALT text?

Yes     Comment for E.2: No comments

E.3 Does the ALT text for all images used for links or form control buttons match the onscreen text?
NOTE: If an image is used in conjunction with text links that ALT='' text should be null, otherwise the link text is spoken twice in screen readers.

  No   Comment for E.3: See my comments in n.4 above.

E.4 Do all OBJECTs/APPLETS have text descriptions and alerntaive accessible version of the content and functions provided by the applet or object.

  No   Comment for E.4: No comments

E.5 Are text transcipts of audio, video+audio and other multimedia available?

    N/A Comment for E.5: No comments

E.6 Are Text transcipts video+audio and other multimedia with visual and auditory renderings synchoronized with visual rendering?

    N/A Comment for E.6: No comments

E.7 Are links available to play multi-media content in external multi-media players?

    N/A Comment for E.7: No comments

Styling

Conformance Rating

Y.1 Does content reflow when browser text zooming features change font size?
NOTE: As content reflows the user should not need to use the horizontal scrolling features to view content and text content should not overlap with other text content.

    N/A Comment for Y.1: I cannot verify it but since CSS is not used fully to stylize this module, it is very possible that it won't flow well.

Y.2 Does content reflow when the graphical window width changes.
NOTE: As content reflows the user should not need to use the horizontal scroll features to view content.

    N/A Comment for Y.2: I cannot verify it but since CSS is not used fully to stylize this module, it is very possible that it won't flow well.

Y.3 Is content still usable when high contrast stylesheets are applied to the web page?
NOTE: The Opera browser has built-in high contrast user stylesheets and the Mozilla/Firefox Accessibility Extension also provides a high contrast stylesheet feature.

    N/A Comment for Y.3: I cannot verify it but since CSS is not used fully to stylize this module, it is very possible that it won't flow well.

Y.4 Are Background images used for decorative styling, instead of inline images?

    N/A Comment for Y.4: No comments

Y.5 Is any image used to stylize text, except in logos and other branding icons?

    N/A Comment for Y.5: No comments

Y.6 Is all content styled through CSS stylesheets, no in-line styling elements are used (i.e. B, I, FONT, CENTER, BLINK, MARQUEE, ...)?

  No   Comment for Y.6: No comments

Y.7 Do dynamic CSS pseudo-classes like :hover have corresponding :focus dynamic pseudo-class selectors.
NOTE: Keyboard movement of fous should cause changes in stypling, similar to :hover effects.

    N/A Comment for Y.7: No comments

Scripting and Automation

Conformance Rating

R.1 Can all functions of the web page be performed with only the keyboard?

  No   Comment for R.1: The Java-based function: Enable HTML Creater, is not usable for keyboard users. You cannot open a selected subject without mouse either.

R.2 Is any OnChange event used for SELECT elements?

  No   Comment for R.2: No comments

R.3 Are session time outs adjustable by the user?

  No   Comment for R.3: User has no mean to customize session time-out.

R.4 Can animations be paused and restarted by the user?

  No   Comment for R.4: No comments

R.5 Is any content that flickers between 2-55 Hz disabled by default, users must be warned of the flickeering before the content is started?

    N/A Comment for R.5: No comments

R.6 Is an accessible alternative for embedded Java Applets, Flash and other APPLETS and OBJECTS available?

  No   Comment for R.6: See my comments on R.1.

Standards

Conformance Rating

S.1 Is DOCTYPE specified?

Yes     Comment for S.1: No comments

S.2 Is default language specified?

  No   Comment for S.2: No comments

S.3 Is character encoding specified?

  No   Comment for S.3: No comments

 

The fact that users cannot open the desired e-mail makes theis module unusable for keyboard users including the screen reader users. Another important problem with this module is the Java-based Enable HTML Creater. If a keyboard users intentionally or unintentionally clicks on it, then there is no way to get out of it. Non-matching on-screen values of some buttons with their corresponding alt/title attributes are other problems that need to be addressed and resolved.