- From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
- Date: Wed, 18 Jun 2014 19:13:36 -0700
- To: "'Janina Sajka'" <janina@rednote.net>
- Cc: <public-html-admin@w3.org>, "'W3C WAI Protocols & Formats'" <public-pfwg@w3.org>
No worries, Actually Mark already helped me with this, since I was under quite a few deadlines at the time. -----Original Message----- From: Mark Sadecki [mailto:mark@w3.org] Sent: Friday, June 13, 2014 1:20 PM For your reference: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26090 Implicit ARIA semantics for the <ol> and <ul> elements should include radiogroup https://www.w3.org/Bugs/Public/show_bug.cgi?id=26089 Implicit ARIA semantics for the <li> element should include radio https://www.w3.org/Bugs/Public/show_bug.cgi?id=26088 Implicit ARIA semantics for the <a> element should include radio and option Thanks again. Mark -----Original Message----- From: 'Janina Sajka' [mailto:janina@rednote.net] Sent: Wednesday, June 18, 2014 7:02 PM To: Bryan Garaventa Cc: public-html-admin@w3.org; 'W3C WAI Protocols & Formats' Subject: Re: CfC: return HTML 5.0 to Last Call Bryan: Please consider filing bugs for the items you identify below. Janina Bryan Garaventa writes: > I would like to make a note about section "3.2.7.4 Implicit ARIA Semantics" > > The following is stated for the A tag: > > "If specified, role must be one of the following: link, button, > checkbox, menuitem, menuitemcheckbox,menuitemradio, tab, or treeitem" > > The following are missing however, radio and option. > > Similarly, the following is stated for the LI element: > > "If specified, role must be one of the following: listitem, menuitem, > menuitemcheckbox, menuitemradio, option, tab, treeitem or presentation" > > Radio is missing. > > Regarding the OL and UL elements: > > "If specified, role must be one of the following: directory, list, > listbox, menu, menubar, tablist, toolbar, tree or presentation" > > Radiogroup is missing. > > All the best, > Bryan > > -----Original Message----- > From: Janina Sajka [mailto:janina@rednote.net] > Sent: Friday, June 13, 2014 7:13 AM > To: public-html-admin@w3.org > Cc: W3C WAI Protocols & Formats > Subject: 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-nati > ve-sem > antics > > 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&chfiel > > df > > rom=2012-12-17&chfieldto=2014-06-17&chfieldvalue=RESOLVED&component= > > HT ML5%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/ > > -- 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 Thursday, 19 June 2014 02:14:38 UTC