Report Form issues

Open issues

• liability, filtering out wrong/bad report (is educating reporter as much as we can enough?)
• need junior programming resource to implement what's on the todo list below

Todo

• implement cgi behind report step forms: query report database for dup, extract webmaster email, building dynamic pages, dynamic email, do sendmail, etc.
• complete small tutorial/help file
  -- get list of stable # in GL
• append bobby short report, maybe modify it
• get reliable text-only service, maybe host it at w3.org
• add integrity: make sure the version reported is the same as the one bobbied and lynxed. Also add browser info.

Comments

For the replies to the messages, I can imagine the following cases:

• no reply: message was ignored
• ignored + treated as spam, w3.org enters some spam filter :-(
• disagreement over the report, reply/discussion on list
• report acknowledged, action is taken to make the site more accessible, a note is sent to w3c-wai-report@w3.org, discussion/ack can follow.

I like the idea of having the same forum used for storing outgoing (from W3C to site) and ingoing (from site to W3C) messages because it's simple and also it gives the outgoing reports the same publicity as their reactions (the replies) from webmaster, whatever this publicness is.