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

Hi Rich,

Why would you want to apply the role of password to a static, non-editable
element? If it's one thing we know, it's that if authors can mess it up,
they will.

If we don't specify this, how would a browser parse this: <img src=""
role="password"> ? What is a screen reader supposed to do with that?

Thanks.

JF

On Fri, Jun 10, 2016 at 3:44 PM, Rich Schwerdtfeger <richschwer@gmail.com>
wrote:

> 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.
>
> 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>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
>
>


-- 
John Foliot
Principal Accessibility Consultant
Deque Systems Inc.
john.foliot@deque.com

Advancing the mission of digital accessibility and inclusion