Re: Custom Element Semantics
Hi, Steve. A second (small) run. * It represents http://www.w3.org/TR/html/dom.html#represents its children. The term represents is defined by Elements in the DOM represent things; that is, they have intrinsic *meaning*, also known as semantics.. So that means that custom elements have meaning of its children, that may sound unclear. For example, a custom element contains text field and button elements so one element represents both a button and a text field. It's questionable how such custom element have to be mapped to accessible tree. Wouldn't it be good to say something like custom element is a container for its children. * All stuff are under 11.1.1 Custom Tag Example. I would describe the idea first and then supplied it by example. For example, As instantiated a custom tag conveys a similar amount of semantics as a HTML div http://www.w3.org/TR/html/grouping-content.html#the-div-element or span http://www.w3.org/TR/html/text-level-semantics.html#the-span-element element doesn't have any need to describe the taco-button example and should be used as generic description. The wording could be like By default a custom tag http://stevefaulkner.github.io/webcomponents/spec/custom/#dfn-custom-tag has no special meaning at all. It serves is a container for its children. As instantiated a custom tag conveys a similar amount of semantics as a HTML div http://www.w3.org/TR/html/grouping-content.html#the-div-element or span http://www.w3.org/TR/html/text-level-semantics.html#the-span-element element. The addition of visual styling and scripted events to the custom element could provide hints as to the semantics and expected interaction behaviours of the custom element for *some* users, but for the semantics to be formally expressed, developers must convey the semantics using ARIA roles http://w3c.github.io/aria/aria/aria.html#usage_intro, states and properties http://w3c.github.io/aria/aria/aria.html#introstates. * The addition of visual styling and scripted events to the custom element could provide hints as to the semantics and expected interaction behaviours of the custom element for *some* users, but for the semantics to be formally expressed, developers must convey the semantics using ARIA roles http://w3c.github.io/aria/aria/aria.html#usage_intro, states and properties http://w3c.github.io/aria/aria/aria.html#introstates It sounds as too strong statement. Scripted events may add semantics and may be mapped to accessible tree, so it's really about some semantics rather than semantics for some users. Also I would replace must for ARIA techniques on can. It's rather a right way to add semantics, but shouldn't be a requirement. Thanks. Alex. On Mon, Dec 15, 2014 at 3:24 AM, Steve Faulkner faulkner.st...@gmail.com wrote: Thanks Alex! I have made some updates to the spec text in response to your feedback, I have also added other content. http://stevefaulkner.github.io/webcomponents/spec/custom/#semantics please review, thanks! -- Regards SteveF HTML 5.1 http://www.w3.org/html/wg/drafts/html/master/ On 9 December 2014 at 17:29, Alexander Surkov surkov.alexan...@gmail.com wrote: Hi. Some feedback per Steve's request on WAI group. * but for the semantics to be formally expressed, developers must convey the role, states and properties of the element to browser APIs. It's not clear what role, states and properties is. It'd be good to develop this sentence by mentioning ARIA techniques. Also it might be not clear what browser APIs are. Perhaps I wouldn't even mention a11y APIs since this info is rather for browser developers and may sound confusing for web authors. * I don't think that any focusable element should get its name from its subtree. For example, tree control name is not a concatenation of subtrees of its item. I think role should define whether the element should grab its name from the subtree or not. taco-button tabindex=0Eat Me/taco-button * The addition of a tabindex http://www.w3.org/TR/html/editing.html#attr-tabindex attribute to the *taco-button* element I think taco-button should be left for examples, but all rules should be worded in generic terms. For example, the sentence above would be The addition of tabindex attribute to the custom element and then give a markup example for taco-button. * The addition of keyboard event handlers to the *taco-button* element provides the means for keyboard users to operate the control, but does not convey the presence of the functionality. I think I miss the idea of this sentence because the topic is about semantics of custom elements and thus it's not clear with me where functionality is supposed to be here. * The addition of an ARIA role=button http://rawgit.com/w3c/aria/master/aria/aria.html#button conveys the *taco-button* element's role semantics It'd be good to generalize it and give this sentence as an example. It'd be good to mention other ARIA button related attributes. Thanks.
Re: PSA: publishing new WD of Custom Elements on December 16
On 12/10/14 8:10 PM, Arthur Barstow wrote: Dimitri prepared a new Working Draft of Custom Elements for publication on December 16: http://w3c.github.io/webcomponents/publish/custom/WD-custom-elements-20141218/ FYI, this WD was published today http://www.w3.org/TR/2014/WD-custom-elements-20141216/.
IndieUI Teleconference Agenda; 17 December at 22:00Z for 60 minutes
Cross-posting as is now usual ... What: IndieUI Task Force Teleconference When: Wednesday 17 December 2:00 PMSan Francisco -- U.S. Pacific Time (PST: UTC -8) 4:00 PMAustin -- U.S. Central Time(CST: UTC -6) 5:00 PMBoston -- U.S. Eastern Time(EST: UTC -5) 10:00 PMLondon -- British Time (BST: UTC +0) 11:00 PMParis -- Central European Time (CET: UTC +1) 6:00 AMBeijing -- China Standard Time (Thursday, 13 November CST: UTC +8) 7:00 AMTokyo -- Japan Standard Time(Thursday, 13 November JST: UTC +9) Where: W3C Teleconference--See Below * Time of day conversions Please verify the correct time of this meeting in your time zone using the Fixed Time Clock at: http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconferenceiso=20141217T1700p1=43ah=1 ** Preliminary Agenda for IndieUI Task Force Teleconference 17 December 2014 Meeting: IndieUI Task Force Teleconference Chair: Janina_Sajka agenda+ preview agenda with items from two minutes agenda+ End of Year Telecon Scheduling -- Reminder agenda+ Checkin with Web Apps' Editing TF [See below] agenda+ Editor's Report agenda+ `Events Spec Changes Vis a Vis Editing TF agenda+ User Context -- TPAC Followup agenda+ Reconsidering Our Timelines agenda+ Requirements Use Cases Progress agenda+ Testing Conversation; Polyfills agenda+ User Context Issues Actions https://www.w3.org/WAI/IndieUI/track/products/3 agenda+ Events Issues Actions https://www.w3.org/WAI/IndieUI/track/products/2 agenda+ Other Business agenda+ Be Done Resource: TPAC Minutes Monday: http://www.w3.org/2014/10/27-indie-ui-minutes.html Tuesday:http://www.w3.org/2014/10/28-indie-ui-minutes.html Resource: Teleconference Minutes http://www.w3.org/2014/11/19-indie-ui-minutes.html Resource: Web Apps Editing TF Editing Explainer: http://w3c.github.io/editing-explainer/ User Intentions: http://w3c.github.io/editing-explainer/commands-explainer.html Resource: For Reference Home Page: http://www.w3.org/WAI/IndieUI/ Email Archive: http://lists.w3.org/Archives/Public/public-indie-ui/ Resource: Teleconference Logistics Dial the Zakim bridge using either SIP or the PSTN. PSTN: +1.617.761.6200 (This is a U.S. number). SIP: za...@voip.w3.org You should be prompted for a pass code, This is 46343# (INDIE#) Alternatively, bypass the Zakim prompts and SIP directly into our teleconference. SIP: 0046...@voip.w3.org Instructions for connecting using SIP: http://www.w3.org/2006/tools/wiki/Zakim-SIP Place for users to contribute additional VoIP tips. http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips IRC: server: irc.w3.org, channel: #indie-ui. During the conference you can manage your participation with Zakim commands as follows: 61# to mute yourself 60# to unMute yourself 41# to raise your hand (enter speaking queue) 40# to lower your hand (exit speaking queue) The system acknowledges these commands with a rapid, three-tone confirmation. Mobile phone users especially should use the mute function if they don't have a mute function in their phone. But the hand-raising function is a good idea for anyone not using IRC. * IRC access An IRC channel will be available. The server is irc.w3.org, The port number is 6665 (Note this is not the normal default) and The channel is #indie-ui. * Some helpful Scribing and Participation Tips http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet For more on the IRC setup and the robots we use for agenda and speaker queuing and for posting the log to the web, see: - For RRSAgent, that captures and posts the log with special attention to action items: http://www.w3.org/2002/03/RRSAgent - For Zakim, the IRC interface to the bridge manager, that will maintain speaker and agenda queues: http://www.w3.org/2001/12/zakim-irc-bot - For a Web gateway to IRC you can use if your network administrators forbid IRC, see: http://www.w3.org/2001/01/cgi-irc - For more on W3C use of IRC see: http://www.w3.org/Project/IRC/ -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Email: jan...@rednote.net The Linux Foundation Chair, Open Accessibility: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Protocols Formats http://www.w3.org/wai/pf IndieUI http://www.w3.org/WAI/IndieUI/
Re: IndieUI Teleconference Agenda; 17 December at 22:00Z for 60 minutes
Editor's Report topics: Events spec: - on hold until ETF determines Event structure User Context: - Several new features from IndieUI being incorporated into CSS4. - Discussion with CSS WG re: adding MF security model. Shared, separate spec? Would affect both JS and CSS accessors. On Dec 16, 2014, at 12:32 PM, Janina Sajka jan...@rednote.net wrote: Cross-posting as is now usual ... What: IndieUI Task Force Teleconference When: Wednesday 17 December 2:00 PMSan Francisco -- U.S. Pacific Time (PST: UTC -8) 4:00 PMAustin -- U.S. Central Time(CST: UTC -6) 5:00 PMBoston -- U.S. Eastern Time(EST: UTC -5) 10:00 PMLondon -- British Time (BST: UTC +0) 11:00 PMParis -- Central European Time (CET: UTC +1) 6:00 AMBeijing -- China Standard Time (Thursday, 13 November CST: UTC +8) 7:00 AMTokyo -- Japan Standard Time(Thursday, 13 November JST: UTC +9) Where:W3C Teleconference--See Below * Time of day conversions Please verify the correct time of this meeting in your time zone using the Fixed Time Clock at: http://timeanddate.com/worldclock/fixedtime.html?msg=IndieUI+Teleconferenceiso=20141217T1700p1=43ah=1 ** Preliminary Agenda for IndieUI Task Force Teleconference 17 December 2014 Meeting: IndieUI Task Force Teleconference Chair:Janina_Sajka agenda+ preview agenda with items from two minutes agenda+ End of Year Telecon Scheduling -- Reminder agenda+ Checkin with Web Apps' Editing TF [See below] agenda+ Editor's Report agenda+ `Events Spec Changes Vis a Vis Editing TF agenda+ User Context -- TPAC Followup agenda+ Reconsidering Our Timelines agenda+ Requirements Use Cases Progress agenda+ Testing Conversation; Polyfills agenda+ User Context Issues Actions https://www.w3.org/WAI/IndieUI/track/products/3 agenda+ Events Issues Actions https://www.w3.org/WAI/IndieUI/track/products/2 agenda+Other Business agenda+ Be Done Resource: TPAC Minutes Monday: http://www.w3.org/2014/10/27-indie-ui-minutes.html Tuesday: http://www.w3.org/2014/10/28-indie-ui-minutes.html Resource: Teleconference Minutes http://www.w3.org/2014/11/19-indie-ui-minutes.html Resource: Web Apps Editing TF Editing Explainer:http://w3c.github.io/editing-explainer/ User Intentions: http://w3c.github.io/editing-explainer/commands-explainer.html Resource: For Reference Home Page:http://www.w3.org/WAI/IndieUI/ Email Archive:http://lists.w3.org/Archives/Public/public-indie-ui/ Resource: Teleconference Logistics Dial the Zakim bridge using either SIP or the PSTN. PSTN: +1.617.761.6200 (This is a U.S. number). SIP: za...@voip.w3.org You should be prompted for a pass code, This is 46343# (INDIE#) Alternatively, bypass the Zakim prompts and SIP directly into our teleconference. SIP: 0046...@voip.w3.org Instructions for connecting using SIP: http://www.w3.org/2006/tools/wiki/Zakim-SIP Place for users to contribute additional VoIP tips. http://www.w3.org/2006/tools/wiki/Zakim-SIP-tips IRC: server: irc.w3.org, channel: #indie-ui. During the conference you can manage your participation with Zakim commands as follows: 61# to mute yourself 60# to unMute yourself 41# to raise your hand (enter speaking queue) 40# to lower your hand (exit speaking queue) The system acknowledges these commands with a rapid, three-tone confirmation. Mobile phone users especially should use the mute function if they don't have a mute function in their phone. But the hand-raising function is a good idea for anyone not using IRC. * IRC access An IRC channel will be available. The server is irc.w3.org, The port number is 6665 (Note this is not the normal default) and The channel is #indie-ui. * Some helpful Scribing and Participation Tips http://www.w3.org/WAI/PF/wiki/Teleconference_cheat_sheet For more on the IRC setup and the robots we use for agenda and speaker queuing and for posting the log to the web, see: - For RRSAgent, that captures and posts the log with special attention to action items: http://www.w3.org/2002/03/RRSAgent - For Zakim, the IRC interface to the bridge manager, that will maintain speaker and agenda queues: http://www.w3.org/2001/12/zakim-irc-bot - For a Web gateway to IRC you can use if your network administrators forbid IRC, see: http://www.w3.org/2001/01/cgi-irc - For more on W3C use of IRC see: http://www.w3.org/Project/IRC/ -- Janina Sajka, Phone: +1.443.300.2200 sip:jan...@asterisk.rednote.net Email: jan...@rednote.net The Linux Foundation Chair, Open Accessibility:http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair,Protocols Formats