W3C home > Mailing lists > Public > wai-xtech@w3.org > February 2009

details on report of PFWG HTML5 actions & issues status

From: Gregory J. Rosmaita <oedipus@hicom.net>
Date: Thu, 12 Feb 2009 18:29:14 +0000
To: public-html@w3.org, wai-xtech@w3.org, wai-liaison@w3.org
Cc: janina@rednote.net
Message-Id: <20090212182436.M81307@hicom.net>


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:

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

1b) related bugs

1b1) Bug 6462 "Self-reference and cyclic references in headers=''"

     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"

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

1b3) Bug 6438 "Error in step 9.4 of the internal algorithm for scanning 
     and assigning header cells"

     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:

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 

    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: 

   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 

3. @alt

   Steve's reply to Dan on the public HTML list
   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

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:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:51:39 UTC