- From: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
- Date: Mon, 20 Jun 2016 19:58:36 +0000
- To: James Craig <jcraig@apple.com>
- CC: Michael Cooper <cooper@w3.org>, ARIA Working Group <public-aria@w3.org>
- Message-ID: <BLUPR0301MB163404BD3F6057B8F2D87BF4982A0@BLUPR0301MB1634.namprd03.prod.outlook.>
I understand the problem, and this would mean something like the following as markup for spinbutton: <div role="spinbutton" aria-valuemin="0" aria-valuemax="100" aria-valuenow="50" aria-valuetext="50 members" > <button aria-label="Decrement">-</button> <input type="text" value="50" aria-label="Attendees"> <button aria-label="Increment">-</button> </div> As an FYI though, the spec does not support this markup as it is currently written. Bryan Garaventa Accessibility Fellow SSB BART Group, Inc. bryan.garaventa@ssbbartgroup.com 415.624.2709 (o) www.SSBBartGroup.com From: James Craig [mailto:jcraig@apple.com] Sent: Saturday, June 18, 2016 10:01 AM To: ARIA Admin <public-aria-admin@w3.org> Cc: Michael Cooper <cooper@w3.org> Subject: Re: 7-day CfC: notes on option, treeitem, and spinbutton about children presentational - closes 15 June Sorry I'm a couple days late responding to this. Concerns with making "spinbutton" children presentational: I don't think spinbutton's children should be presentational until there is a solution for the ARIA's coverage gap wrt operability. As an example, there is no good way to make custom sliders accessible on touch screen devices because there is no way to trigger the increment/decrement events other than through de facto keypress events (this workaround is not sustainable or recommended for touch screen interfaces). If the WG makes spinbutton's children presentational, the same problem will apply. Author's are currently able to make spinbuttons accessible by using descendant stepper buttons that are individually operable. (Note: The native stepper buttons on macOS and in WebKit are implemented this way.) On Jun 9, 2016, at 6:04 PM, Michael Cooper <cooper@w3.org<mailto:cooper@w3.org>> wrote: This is a Call for Consensus (CfC) to the Accessible Rich Internet Applications (ARIA) Working Group regarding the following resolution of the ARIA Working group: Add editorial note to option, treeitem, and spinbutton roles that their "children are presentational" status is provisional Background This was approved by the participants of the 9 June 2016 teleconference, and further context is available in the minutes: https://www.w3.org/2016/06/09-aria-minutes.html#item02 Note this resolution does not close discussion on the issue of whether these roles ultimately should have the children presentational restriction, or whether further engineering is needed, and if so in what time frame. This edit supports wider review of the topic. Action This CfC is now open for objection, comment, as well as statements of support via email. Silence will be interpreted as support, though messages of support are certainly welcome. If you object to this proposal, or have comments concerning it, please respond by replying on list to this message no later than 23:59 (midnight) Boston Time, Wednesday, 15 June 2016. For objections only, please copy the main aria@w3.org<mailto:aria@w3.org> list to allow technical discussion of the objection to happen there. Process This CfC is conducted per the ARIA WG decision policy: https://www.w3.org/WAI/ARIA/decision-policy I am issuing this CfC as acting chair, but Rich will record the formal ratification if passed. Michael
Received on Monday, 20 June 2016 19:59:08 UTC