W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2005

GL 1.3 issue summary against June 30 draft

From: <Becky_Gibson@notesdev.ibm.com>
Date: Thu, 30 Jun 2005 08:28:56 -0400
To: "WCAG " <w3c-wai-gl@w3.org>
Message-ID: <OFF0236297.718F22C4-ON8525702E.0048184A-85257030.0044CEDC@notesdev.ibm.com>

I reviewed the open Issues for 1.3 based on June 30 draft are placed each 
into one of three categories:
1. Issues that are closed
2. Issues that seem to be closed, but may need clarification
3. Issues that are not addressed in current draft


1. Issues that are closed (1)
Issue 1371 GL 1.3, Example 1 - required fields should be marked in advance 
[http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1371]. This is a 
duplicate of 1350 and should be closed for that reason - it is not a 
result of changes in the latest draft.

Issue  1453 Don't understand General Technique for GL 1.3 L1 SC3 - using 
color to convey information 
[http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1453] was addressed 
by the proposal for guideline 1.3 level 1 and level 2 success criteria 2 
adopted at the June 23, 2005 meeting 
[http://www.w3.org/2005/06/23-wai-wcag-minutes.html].

2. Issues that seem to be closed, but may need clarification
Issue 1005 Meaning of "derived programmatically" and "structure" [
http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1005] may be addressed 
 by the proposal for guideline 1.3 level l success criterion 1 adopted at 
the May 5, 2005 meeting [
http://www.w3.org/2005/05/05-wai-wcag-minutes.html]. Unsure because of the 
following reasons: The author has questions about what "structural 
relationships" are.  The word "relationships" has been removed from the 
current SC language which may solve the issue.  Also, has a concern about 
what "structures" are and how this SC can be tested.  Suggest contacting 
the author and asking if current wording and definition of 
"programmatically determined" answers the questions.

Issue 1086  Programmatically defining structures and relationships within 
the content is not always possible.[
http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1086 ] may be 
addressed  by the proposal for guideline 1.3 level l success criterion 1 
adopted at the May 5, 2005 meeting 
{http://www.w3.org/2005/05/05-wai-wcag-minutes.html]. Unsure because of 
the following reasons: Issue was that structural relationships can not 
always be determined.  Since "relationships" has been removed fromt he 
current SC language need to check with author and see if this solves the 
issue. 

Issue 1087      Difference between 2 success criteria for color use is 
confusing. [http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=1087] may 
be addressed  by the proposal for guideline 1.3 level 1 and level 2 
success criteria 2 adopted at the June 23, 2005 meeting [
http://www.w3.org/2005/06/23-wai-wcag-minutes.html]. Unsure because of the 
following reasons: The rewording of the SC concerning color should address 
this issue but there is also a request for a clarification of links and 
color. 


3. Issues that are not addressed in current draft:
Issue  827 Need SC for separation of structure from presentation
         Reason: there is still no explicit SC about separating 
presentation from structure

Issue 938       Clarify language in Guideline 1.3, especially examples
        Reason: no change to examples in this draft
Issue 795       Level 1 success criteria should not prohibit short simple 
text 
        Reason: We have still not addressed the issue of plain text which 
does not have structure

Issue 796       Describe how 1.3 benefits people  
        Reason: no modification to the benefits section in this draft

Issue 1036      Why isn't "avoid blinking or flashing" a criterion for 
content-structure-separation? 

Issue 1088      Add an example to Guideline 1.3, SC2. 
        Reason: no change to examples in this draft

Issue 1309      Clarify definition of programmatically determined.
        Reason: no change to definition of programmatically determined

Issue 1339      GL 1.3 wording hard to understand 
        Reason: although this is essentially a duplicate of 1309 - it 
specifically complains about the wording of the GL 1.3 Level 1 SC 1 - I 
would leave open since  issue 1309 addresses the definition of 
programmatically determined in addtion to the SC text.

Issue 1350      GL 1.3, Example 1 conflicts with usability
        Reason: no change to examples in this draft

 


Becky Gibson
Web Accessibility Architect
                                                       
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
Email: gibsonb@us.ibm.com
Received on Thursday, 30 June 2005 12:29:02 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:37 UTC