W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2017

Re: Subgroups proposal for support personalization and important request from coga

From: Wayne Dick <wayneedick@gmail.com>
Date: Tue, 18 Jul 2017 13:37:29 -0700
Message-ID: <CAJeQ8SDt3eJW-wwCQ0P1U+ax0XMpMQpDcVLfdvdZ-HYdoc5cYg@mail.gmail.com>
To: Alastair Campbell <acampbell@nomensa.com>
Cc: "W3c-Wai-Gl-Request@W3. Org" <w3c-wai-gl@w3.org>
To All,
Yes, we have a gap in HTML and ARIA. How much can we fix in one week.

Is there one item we can isolate that needs semantic that can be added, is
technology independent (in the 2.1 sense). I am thinking that disambiguate
div elements is the place.

The problem with ARIA is that people only think of it as contributing to
the accessibility API, not just providing semantic support. That is what
personalization requires.

Am I way off?

Wayne

On Tue, Jul 18, 2017 at 1:15 PM, Alastair Campbell <acampbell@nomensa.com>
wrote:

> Hi Wayne,
>
>
>
> I think the problem is that (for the context / conventional elements at
> least) they don’t have native semantics (so not 1.3.1), and elements like
> links already have a role and a name, value doesn’t match, so they are not
> covered by role/name/value either.
>
>
>
> Cheers,
>
>
>
> -Alastair
>
>
>
>
>
> *From:* Wayne Dickmailto:wayneedick@gmail.com]
>
>
>
>
>
> > What we are proposes really appears to be cases of 1.3.1 that were not
> covered in previous iterations of the techniques.
>
>
>
Received on Tuesday, 18 July 2017 20:38:38 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:15 UTC