Functional Web Accessibility Checklist for Single Web Resource

Other Accessibility Checklists

Instructions

This is a electronic piece of paper, submitting the form (edit report or print view buttons) does not save the information you have entered or send it to the instructor. You must make your own local copy on your local storage (i.e. hard disk, USB drive, etc..) and use the form on the page to send a copy to the instructor.

"Edit" Mode
Allows you to edit results and comments using form controls. You can switch between edit and print mode with any of the button pairs on the page.
"Print" Mode
Removes form controls and uses text to indicate results.
Saving and Editing
When you close the web browser you will loose all the information that you have entered, make sure you save your form.
Before saving use the "Print View" button on the page. This stores your current settings in hidden input controls on the web page
Use the browsers "Save As" command save a copy of the web page on your local hard disk or storage device for permanent storage. You can edit the page again, by opening the page in a web browser and selecting the edit button option.
Sending the Results to the Instructor
Enter your name, e-mail, course and the instructors name and e-mail address in the form below.
Press the "Send to Instructor" button

Student and Instructor Information

Jeff Ginger

ginger@uiuc.edu

LIS 490

Jon Gunderson

jongund@uiuc.edu

Web Resource Information

Beckwith Training

www.jag85.com/beckwith

Functional Web Accessibility Testing

Functional Accessibility Rating

Navigation

 Conformance Rating

N.1 Unique titles with corresponding h1 element on each resource.

 Yes     Comment for N.1: Main Beckwith title.

N.2 All major/minor topics have headings (h1-h6) and the headings provide useful orientation information to the content on the page. Headings should not be used to stylize text.

 Yes     Comment for N.2: Navigation and main topics identified.

N.3 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.

 Yes     Comment for N.3: All links should be self explanatory.

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

     N/A Comment for N.4: No image maps present.

N.5 Are navigation bars markup up using ul and given a title with an H2 or other header. Header maybe hidden using CSS techniques.

 Yes     Comment for N.5: Yes in all cases.

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

   No   Comment for N.6: CSS is intermingled with javascript in order to make IE6 work. It is still accessible.

N.7 Do all form controls of have labels.

     N/A Comment for N.7: No form controls to worry about.

N.8 Are groups of form controls have labels.

     N/A Comment for N.8: No form controls to worry about.

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

     N/A Comment for N.9: No changes in language.

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

     N/A Comment for N.10: No data tables.

N.11 Lists markup using ul, ol or dl lists.

 Yes     Comment for N.11: Numerous lists, and they all use this technique.

N.12 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".

     N/A Comment for N.12: No frames to worry about.

Text Equivalents

 Conformance Rating

E.1 All images have text descriptions

 Yes     Comment for E.1: All images that need them.

E.2 All OBJECTs/APPLETS have text descriptions

     N/A Comment for E.2: No applets or objects.

Styling

 Conformance Rating

Y.1 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.

 Yes     Comment for Y.1: All content reflows just fine. Feature text doesn't change size, but they have alt tags that read what they say. Header underline gets out of sync but only because it's part of the graphic. There's no easy way to do an underline like that in CSS.

Y.2 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.

 Yes     Comment for Y.2: Page layout reflows fine.

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

 Yes     Comment for Y.3: It's ugly, but it works.

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

 Yes     Comment for Y.4: The only images are the features on the home page.

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

 Yes     Comment for Y.5: Just the UIUC logo in the upper corner, nothing else.

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

 Yes     Comment for Y.6: New style markup.

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

 Yes     Comment for Y.7: Accounted for as needed.

Scripting and Automation

 Conformance Rating

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

   No   Comment for R.1: No access keys, but headers can be navigated through in good browsers.

R.2 Dymanic text content hidden or revealed using CSS techniques.

 Yes     Comment for R.2: Hidden links and headers with CSS.

R.3 No OnChange events on SELECT elements.

 Yes     Comment for R.3: No such conditions.

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

 Yes     Comment for R.4: No image swapping.

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

   No   Comment for R.5: Pull downs use a combination of CSS and javascript in order to make IE6 work.

R.6 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

     N/A Comment for R.6: No timed response resources.

R.7 Animations can be paused and restarted under user control

     N/A Comment for R.7: No annimations.

R.8 No content causes flickering between 2-55 Hz

     N/A Comment for R.8: No issues of flicker.

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

     N/A Comment for R.9: Just feature pictures, no big deal.

Multimedia

 Conformance Rating

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

     N/A Comment for M.1: No multimedia.

M.2 Text transcipts video+audio and other multimedia with visual and auditory renderings are synchoronized with visual rendering

     N/A Comment for M.2: No multimedia.

M.3 Provide links to play multi-media content in external multimedia players

     N/A Comment for M.3: No multimedia.

Standards

 Conformance Rating

S.1 DOCTYPE specified

 Yes     Comment for S.1: Yessir.

S.2 Default language sepcified

 Yes     Comment for S.2: Yes, english.

S.3 Character encoding specified

 Yes     Comment for S.3: Yes.

S.4 No validation errors

 Yes     Comment for S.4: All pages pass but the home page, which has issues only because of the javascript.

 

No comments

Valid XHTML 1.0 Transitional Copyright 2006 Illinois Center on Information Technology Accessibility