Re: Finding agreement on common purpose

Léonie, I think some important decisions are going to be made on the call
today. You may want to consider joining us at 11am EST

I am largely in agreement with you regarding the concerns about mapping. It
appears Gregg Vanderheiden shares these concerns also.

Lisa assures us its trivial using JSON and that the AT itself will have
mapping documents which include micro data, schema.org, coga-attributes and
html5 tokens.

I have confusion about whether the ACCNAME, ACCDESCRIPTION could be used as
those tokens (at least in the English language), in which case,  <label>
element with a a common purpose would be sufficient. This would lower the
burden on authors sgnificantly. Early discussions indicated that to be the
case, but I've gotten no clear answers yet and its not in the list of
sufficient techniques proposed.

Unfortunately, there is no AT right now to demonstrate this mapping in
action. I feel like the mapping part of it is this black box that doesn't
exist and that we're supposed to just trust will happen.

 I would like to hear more from Lisa and others about how that is actually
going to happen in an effective way.



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 7:43 AM, Alastair Campbell <acampbell@nomensa.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
>
> Yes, but not *in* the success criteria, otherwise 4.1.2 would have to
> define which ARIA attributes to use, and 1.3.1 which HTML elements to use.
>
> At the SC level it should define the requirement, at the technique level
> (and separate specs) it should define the mapping.
>
> The difference (and compromise) compared to ARIA is that there needs to be
> a list of purposes/meanings, as the external specs are not dedicated to
> providing this and HTML is much wider than accessibility.
>
> -Alastair
>
>