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 06:27:50 -0400
To: Aaron Leventhal <aleventhal@google.com>
Cc: Rich Schwerdtfeger <richschwer@gmail.com>, ARIA Working Group <public-aria@w3.org>
Message-ID: <a01d7e2c-ce3e-a7f6-81fd-a50fbe82e40f@igalia.com>
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?

Received on Wednesday, 2 August 2017 10:28:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:58:40 UTC