RE: Next step

I volunteered for issues for Guideline 4.2. Below are my brief recommendations. Note: to view the issue, append the issue number to the URL <http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=> (I didn't want to put 15 nearly identical URLs into this post).

There are a number of issues in the "pending" state: 244, 889, 934, 970, 993, 1133, 1537. I recommend we close them all, as resolved by the baseline. I'm not sure the reviewers who raised the issues will agree the baseline is the solution they were looking for but they can raise new issues about that if needed.

Below are my recommendations for open issues, using the key suggested by Gregg and repeated at the bottom of the message. For items coded "3" - reject and close - I provided a brief rationale. The others didn't seem to require that, but I can explain during teleconference if needed.

822:  1
971:  2
972:  3 - many of us don't like alternate versions, but for some technologies it is the only way
1050: 3 - baseline and technology independence are future-proofing approaches; guide docs support
1418: 1
1536: 1
1713: 2
1714: 3 - scalability constantly discussed but determined a UA issue

1 - addressed by our current edits
2 - OBE (overcome by events) (e.g. the bug no longer applies with our new wording)
3 - Suggest rejecting comment and closing (based on our discussions to date)
4 - Suggest making the following change and closing it
5 - keep item open.

Michael

--- Signature ---

Michael Cooper
Accessibility Product Manager, Watchfire
1 Hines Rd Suite 200, Kanata, ON  K2K 3C7  Canada
Tel: +1 (613) 599-3888 x4019
Fax: +1 (613) 599-4661
Email: michaelc@watchfire.com
Web: http://www.watchfire.com/

Received on Tuesday, 29 November 2005 18:11:02 UTC