proposal for accessibility report tool

i took an action item a couple weeks ago to write a proposal for the 
accessibility report tool.

We have discussed setting up a non-technical version as well as a technical 
version.  The technical version needs to cover at least all of the P1 
checkpoints from WCAG.  My proposal actually allows someone to go through 
all three levels.  Note that the technical version is a rough sketch 
because i focused on the non-technical version as well as the general 
flow.  I think the technical version will share text with ERT and will need 
to be fairly detailed.

to decrease the insanity, we ought to script the creation of the report 
from the ERT document (in WCAG we generate the checkpoint list from the 
guidelines document).  This is something that I can work on with Ian.  I 
just want y'all to be aware that this doesn't have to be a huge time hog to 
maintain once (if) it is set up.



Step 1
Welcome to the Web Accessibility Reporting Tool.  This is a five step 
process.  You may cancel at any time.  A report will not be sent until the 
final step after you have pressed the submit button.

Please enter the URL of the page you are reviewing (or use Copy&Paste from 
your browser). [yourURL]  [submit]

Step 2: Review existing reports for [yourURL]  [submit]

Step 3: Identify Problems With [yourURL]
   1. I want to let the site's maintainer know that I can't use the site 
[radiobutton1]
   2. I want to provide a technical review of the site by using the WCAG 
checklist [radiobutton2]
[submit]

Step 4:  Providing feedback
[author e-mail]
[your e-mail]
[your name]

if radiobutton 1
I find this site difficult to use (select all that apply):
   [checkbox] with a screen reader.
   [checkbox] with a screen magnifier.
   [checkbox] with a dynamic braille display.
   [checkbox] without a mouse.
   [checkbox] without a standard QWERTY keyboard.
   [checkbox] without sound.
   [checkbox] without sight.

I also find that I
   [checkbox] can not use the controls because they change too quickly.
   [checkbox] can not access all of the links available on the page.
   [checkbox] can not access all of the information available on the page.
   [checkbox] can not comprehend the information on the page.
   [checkbox] can not use the page because of too much movement.
   [checkbox] can not read the page because of poor color contrast.
   [checkbox] can not make sense of information in tables when the table is 
linearized.
   [checkbox] can not get to information in frames.
   [checkbox] do not know what is presented in a script, applet, or plug-in 
because I do not have the right software.

Browser [picklist]
Assistive Technology [picklist]
other [editbox]
[submit]

else if radiobutton2

Browser [picklist]
Assistive Technology [picklist]
other [editbox]

WCAG Priority 1 checkpoints:
Images
[checkbox] Some images are missing text equivalents.  [Checkpoint 1.1]
[checkbox] Some images are missing a long description. [Checkpoint 1.1]
[checkbox] etc. etc.
(refer to ERT document breakdown of checkpoints.  group by themes: images, 
tables, frames, etc. like in the current List of Checkpoints)
[submit]

WCAG Priority 2 checkpoints:
(refer to ERT document breakdown of checkpoints.  group by themes: images, 
tables, frames, etc. like in the current List of Checkpoints)
[submit]

WCAG Priority 3 checkpoints:
(refer to ERT document breakdown of checkpoints.  group by themes: images, 
tables, frames, etc. like in the current List of Checkpoints)
[submit]

end if radiobutton2

Step 5 (Final step): Confirm Your Report

[view report]
[submit]

<>
wendy a chisholm (wac)
world wide web consortium (w3c)
web accessibility initiative (wai)
madison, wisconsin (madcity, wi)
united states of america (usa)
tel: +1 608 663 6346
</>

Received on Monday, 29 November 1999 10:59:50 UTC