Re: 7-day CfC: restrictions on password role - closes 15 June

Sure, you will be able to make things editable such as the contents of a dive that were not editable and create your own accessible caret with a new accessibility API for the web. Google Docs does not use contenteditable today to create editable docs and they draw their own caret. ... It was not editable content to start.



Sent from my iPhone

> On Jun 11, 2016, at 1:05 PM, Léonie Watson <tink@tink.uk> wrote:
> 
> From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] 
> Sent: 10 June 2016 21:44
> “To be clear, this will certainly create problems in the future should we introduce an API that allows for caret movement and editing by the author. This was one of the ARIA 2 use cases. Although it is not a problem today this text lacks vision as to where we are going and it will need to be changed - probably in ARIA 2.”
>  
> Can you explain this a little more Rich? Thanks.
>  
> Léonie.
>  
> Rich
> 
> Sent from my iPhone
> 
> On Jun 9, 2016, at 9:04 PM, Michael Cooper <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:
> 
> Accept Joanie's text limiting password role to editable elements, with Michael's addition about host language parallel restriction.
> 
> 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#item03
> 
> If this CfC is accepted, the following changes will be merged:
> 
> https://github.com/w3c/aria/compare/action-2080
> 
> 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 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