Re: What is a failure of 1.3.5 Identify Input Purpose?

> What AT is required to support the technique for this SC? Serious
question.

What can be done without AT in terms of identifying the purpose of the
input and doing interesting things with that purpose envisioned by COGA
such as inserting icons, swapping out labels, etc. as per the Understanding
doc. etc....  ?

Cheers,
David MacDonald



*Can**Adapt* *Solutions Inc.*

Tel:  613-806-9005

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 Wed, Jan 23, 2019 at 4:57 PM Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> On 23/01/2019 21:51, John Foliot wrote:
> > Hi David,
> >
> > What AT is required to support the technique for this SC? Serious
> question.
>
> Some AT (or UA, or UA extension) that does something meaningful with
> whatever means of adding "purpose" the author chose?
>
> Probably depends on the exact reading of what "support" really
> means/refers to in
>
> "The content is implemented using technologies with support for
> identifying the expected meaning for form input data."
>
> Support in a theoretical "well, it's exposed programmatically by the UA"
> way, or support in a "and there's some real-world, actually used UA etc
> that does something with it"?
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>