Re: aria-readonly and plain elements

Joanie, I'll take a look at your recommended spec changes.

Aaron

On Wed, Aug 2, 2017 at 9:07 AM Aaron Leventhal <aleventhal@google.com>
wrote:

> I don't see readonly as a conflict with host language editing, and here's
> why: a readonly state tweaks the meaning of a control to make it for
> display and navigation only, but the value cannot be changed. A readonly
> control is a subtype of that control. For example, authors use <input
> readonly> is a special type of input. It doesn't negate the <input>, which
> is why authors use that instead of a <span> -- they still get the control,
> and the user can navigate it, but the value cannot be changed. In my
> opinion, <contenteditable aria-readonly="true"> is simply analagous to
> <input readonly>. It doesn't conflict, but it tweaks the use.
>
> Regarding timing, I'm just bringing items up as I see them during
> implementation. The group can save them for later, but as a browser
> implementor I'd like to know the intention/direction in any case.
>
> Aaron
>
>
> On Wed, Aug 2, 2017 at 8:02 AM Joanmarie Diggs <jdiggs@igalia.com> wrote:
>
>> 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:
>>   -
>>
>> https://rawgit.com/w3c/aria/readonly-ia2/core-aam/core-aam.html#ariaReadonlyTrue
>>   -
>>
>> https://rawgit.com/w3c/aria/readonly-ia2/core-aam/core-aam.html#ariaReadonlyFalse
>>
>> Thanks!
>> --joanie
>>
>> 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
>> >
>> >
>>
>>