Re: CfC: return HTML 5.0 to Last Call

Dear Chairs, WG:

Please understand that this is NOT an objection to returning HTML 5.0 to
LC. While the PFWG has not considered a position on this question, all
indications are that we would support this CfC.

However, we do believe there is one section of the candidate LC document
whose RFC2119 status may need to be changed. Therefore, we are
requesting that the following section be marked "At Risk" for the LC:

http://htmlwg.org/heartbeat/WD-html5-20140617/dom.html#sec-strong-native-semantics

PF notes that the normative requirements on user agents in this section
are not tested and believes that they cannot be appropriately
implemented from the specification alone. The development of the "HTML
Accessibility API Mappings" specification will eventually provide the
relevant implementation guidance, but this document is far from ready at
this time.

Discussion of this issue in PF can be found beginning at:

http://lists.w3.org/Archives/Public/public-pfwg/2014Jun/0067.html

I expect the PFWG will file a bug against the HTML 5.0 specification in this
regard during the coming week.

Janina


Sam Ruby writes:
> In accordance with Plan 2014[1]:
> 
>      We think it is likely that the Working Group will make substantive
>      changes to the document as a result of Candidate Recommendation
>      Review. Therefore, in accordance with the W3C Process, we will
>      return to a short Last Call before requesting to advance to
>      Proposed Recommendation.
> 
> the HTML Chairs are issuing a Call for Consensus to return HTML 5.0 to Last
> Call.  The document can be found here:
> 
>      http://htmlwg.org/heartbeat/WD-html5-20140617/
> 
> Silence will be taken to mean there is no objection, but positive responses
> are encouraged. If there are no objections by Friday June 13th, this
> resolution will carry.
> 
> The proposed Last Call Working Draft states:
> 
>      The scope of Last Call feedback on this specification is limited to
>      changes that have taken place during the Candidate Recommendation
>      phase[2]. The Last Call period is expected to finish on 15 July
>      2014. Once Last Call comments are addressed, the Working Group
>      expects to advance this draft to Proposed Recommendation.
> 
> Note that some features marked as at risk in the current Candidate
> Recommendation were removed[3].  The following features remain in the draft
> at this time but may be removed due to lack of implementation:
> 
>      the DataCue interface;
>      <input type=time>;
>      drag and drop;
>      the new ruby model.
> 
> - Sam Ruby,
> on behalf of the HTML WG co-chairs
> 
> [1] http://dev.w3.org/html5/decision-policy/html5-2014-plan.html#plan
> [2] https://www.w3.org/Bugs/Public/buglist.cgi?chfield=bug_status&chfieldfrom=2012-12-17&chfieldto=2014-06-17&chfieldvalue=RESOLVED&component=HTML5%20spec&list_id=38742&product=HTML%20WG&query_format=advanced
> [3] https://www.w3.org/Bugs/Public/show_bug.cgi?id=24812

-- 

Janina Sajka,	Phone:	+1.443.300.2200
			sip:janina@asterisk.rednote.net
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/

Received on Friday, 13 June 2014 14:13:41 UTC