details on report of PFWG HTML5 actions & issues status

aloha!

in accordance with DanC's request that i send details to the WG's 
emailing list with details about the report i made on PFWG's processing
of HTML5 issues, i am sending this summary -- although i am confident
that it accurately reflects the state of the situation and the stance 
of WAI/PF, this is not a formal report, but an informational report
compiled at the request of the chairs


1. @headers for table:
   http://esw.w3.org/topic/HTML/IssueTableHeaders

1a) consensus is that the new headers wording is good

1b) related bugs

1b1) Bug 6462 "Self-reference and cyclic references in headers=''"
     (http://www.w3.org/Bugs/Public/show_bug.cgi?id=6462)

     summary: the self-reference bug shouldn't be closed until the 
     specification is updated to outlaw self-referencing headers

1b2) Bug 5822 "The headers attribute should be able to reference a td"
     (http://www.w3.org/Bugs/Public/show_bug.cgi?id=5822)

     summary: this bug has been overtaken by events and has been 
     closed

1b3) Bug 6438 "Error in step 9.4 of the internal algorithm for scanning 
     and assigning header cells"
     (http://www.w3.org/Bugs/Public/show_bug.cgi?id=6438)

     the internal algorithm has not undergone a formal review, but is 
     under active investigation/review by thw PFWG

1c) in addition, chaals is the process of testing @headers, consult:
    http://lists.w3.org/Archives/Public/public-html/2009Feb/0270.html

1d) a note on CyclicHeaderChains: the cyclic reference bug still needs 
    to be addressed as the suggested rewording needs to be written 
    into the HTML5 specification - consult 
    http://esw.w3.org/topic/HTML/CyclicHeaderChains

    the HTML5 WG investigated chained headers, and concluded it would 
    result in perpetual feedback, as each header is resolved with no 
    end; the CyclicHeader chain just points out that isn't the case, 
    but recommends that cyclic references are outlawed, as they're 
    obviously nonsense; the bug Simon has filed is accurate, and 
    should just be incorporated into the spec


2. @summary: 

   PF WG already made an official announcement on this issue and 
   requested the attribute be re-instated, consult: 
   http://lists.w3.org/Archives/Public/public-html/2008Aug/0213.html

   PF WG's position from the outset has been that there is a need to
   restore @summary for TABLE in the draft specification BEFORE the 
   next public working draft is issued -- janina sajka, chair of PFWG
   will probably say so formally in the near future in a post to 
   public-html


3. @alt

   Steve's reply to Dan on the public HTML list
   http://lists.w3.org/Archives/Public/public-html/2009Feb/0266.html
   clearly indicates that the item should remain open as discussions 
   are ongoing. PFWG feedback on @alt will take up to another month 
   or so; PF has been holding ongoing weekly conversations involving 
   chairs of all WAI groups on our feedback to the HTML WG


gregory.
-----------------------------------------------------------------
Accessibility, Internationalization, and Interoperability are not
"features", "overlays" or "add-ons".  Rather, they are core 
components of any architecture -- programmatic or otherwise.
-----------------------------------------------------------------
     Gregory J. Rosmaita, gregory@linux-foundation.org
Vice-Chair, WebMaster & Listmaster, Open Accessibility Workgroup
http://a11y.org/                                http://a11y/specs
-----------------------------------------------------------------

Received on Thursday, 12 February 2009 18:30:18 UTC