Issues that need discussion or proposals - week of 12 April

Ben and I have been cleaning up the issues list.  This email includes 
issues that have proposals to discuss and issues that do not have proposals 
for which we are searching for a volunteer to write a proposal.

Issues that need work
(i.e., we need volunteers to research and write proposals)
We have not attempted to summarize the issue in this email.  Please follow 
links to issues for more information about each issue.

Issue 506 - Definition of structure
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=506>
Action: write a definition of structure that clarifies difference between 
using structured layout vs using structural elements (in definition of 
"structure").

Issue 556 - Guideline is difficult to understand
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=556>
Action: Write a proposal to clarify the level 1 #1 criterion.

Issue 669 - What is meant by "emphasis"
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=669>
Action: Write a proposal to address or clarify use of "emphasis" and visual 
presentation.

Issue 405 - General issue about knowing how to interpret how apply to html 
w/out reading the techniques.
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=405>
Action: Write a proposal that clarifies the Level 1 #1 success criterion.

Issue 704 - In-line warnings and options to deactivate are good, but a User 
Agent could also handle this in most cases
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=704>
Action: This issue could be addressed with some additional text in the 
benefits describing how user agents may handle this in the future.

Issue 707 - Example is vague
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=707>
Action: Write a proposal that clarifies the example or propose a different 
example that will help clarify the intent of the guideline.


Issues that need discussion

Issue 487 - are tables for layout a violation of 1.3?
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=487>
Currently under discussion on the list.  Good example to discuss for June 
draft.

Issue 374 - How do AT users learn what makes structure distinct and how 
these distinctions can be specified?
<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=374>
Yvette proposes this is a user agent issue.  Does anyone disagree?

-- 
wendy a chisholm
world wide web consortium
web accessibility initiative
http://www.w3.org/WAI/
/--

Received on Monday, 19 April 2004 16:38:47 UTC