Re: Finding agreement on common purpose

Can someone answer if these will pass the new SC

<label>First Name<input ...></label>

The AccName would supply the purpose

or

<label>VISA
<input aria-describedby="p1" ...></label>
<span id="p1" class="offscreen">credit card</span>

the AccDescription supplies the purpose

I think it should... and I think mapping AT should be able to map it. This
is what understood during a call between Lisa, John, me and a couple of
others early on as we were trying to find a way forward...

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613.235.4902

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd

GitHub <https://github.com/DavidMacDonald>

www.Can-Adapt.com <http://www.can-adapt.com/>



*  Adapting the web to all users*
*            Including those with disabilities*

If you are not the intended recipient, please review our privacy policy
<http://www.davidmacd.com/disclaimer.html>

On Tue, Jan 16, 2018 at 8:58 AM, Andrew Kirkpatrick <akirkpat@adobe.com>
wrote:

> If the intent of this SC is to enable an AT to concretely determine the
>     purpose of qualifying controls, then we need to define the set of
>     possible tokens. If we say that any token can be used providing it maps
>     to the HTML tokens, we're creating a situation where the best an AT can
>     do is use heuristics and guesswork to make the determination.
>
> That’s not how I see it Leonie.
>
> The tokens defined in the PDF/OOXML/EPUB/etc specifications to convey
> purposes of input controls are the tokens that can be used for that
> technology. The tokens in each of those technologies that are mapped to
> tokens in the HTML list to represent the same purpose are the ones that the
> author is required to use.
>
> AT will need to know what tokens are supported in a given technology, and
> the AT will look at the PDF/OOXML/EPUB/etc spec to implement support.
>
> Authors looking to the right thing will determine if there is a means to
> convey the purposes for inputs for their technology and implement all of
> the tokens fully. Some of these may go beyond what HTML 5.2 indicates.
> Authors looking to do as little as possible will compare the set of tokens
> for their technology with the HTML set and only implement the overlap.
>
> There may be some interpretation and debate about whether the purpose of
> the token in one technology is mapped to a token in HTML, but the set of
> HTML tokens is pretty tight, so I don’t think that will be significant.
>
> AWK
>
>