W3C home > Mailing lists > Public > public-aria@w3.org > August 2017

Re: aria-readonly and plain elements

From: Joanmarie Diggs <jdiggs@igalia.com>
Date: Wed, 2 Aug 2017 08:01:49 -0400
To: Aaron Leventhal <aleventhal@google.com>
Cc: ARIA Working Group <public-aria@w3.org>
Message-ID: <dce24522-e86f-dcb0-a2a2-4624edab4916@igalia.com>
Hey again, Aaron.

I have created a pull request to address (what I believe to be) the most
concerning of the issues you identified. Please take a look -- keeping
in mind that, given the deadlines, the goal is (alas) "good enough"
rather than "perfect". The latter will have to wait for 1.2, I'm afraid.

* PR: https://github.com/w3c/aria/pull/619
* Pretty spec view:


On 08/02/2017 06:27 AM, Joanmarie Diggs wrote:
> Hey Aaron.
> Regarding this particular issue:
> On 07/27/2017 12:15 PM, Aaron Leventhal wrote:
>> CORE-AAM readonly="false"
>> States "Expose IA2_STATE_EDITABLE"
>> This does not make sense for a lot of the roles that support
>> aria-readonly, such as a checkbox.
>> In general it does not make sense to expose IA2_STATE_EDITABLE unless
>> you also expose the IAccessibleEditableText interface, which you would
>> not do on something like a gridcell unless it had contenteditable.
> Yeah.... In the case of ATK, at least there's a statement regarding only
> exposing the "editable" state if it's a textbox. Arguably that should be
> changed to something like "textbox or searchbox" since our taxonomy is
> not something we expect others to pay attention to.
> As for the other issues, a while back I had opened a github issue to fix
> ATK and plan to do so later this morning:
> https://github.com/w3c/aria/issues/568. Are the changes described there
> what you feel are needed for IA2?
> --joanie
Received on Wednesday, 2 August 2017 12:02:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 August 2017 12:02:27 UTC