Re: Use of ARIA to satisfy 'Identify common purpose' SC

Hi David,

I’m fairly sure it is an update to the previous version. I read the spec previously, the structure is similar and the types of content are the same (e.g. field, link, button), it’s just a change of attribute name.

I’m not involved, but working backwards I’d guess the ARIA WG came to a decision about the name, generalising beyond the COGA use-case.

I can’t see a definition, but perhaps it means ARIA UI?  Hmm, that would be an acronym inside an acronym, perhaps just accessible UI?

-Alastair



From: David MacDonald <

Hi Lisa (or anyone else who knows)

How do the new personalization semantics of coga-* vs uia-* relate to one another.

Is UIA-field just an update to COGA-field or is there something new happening here?


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613.235.4902

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

twitter.com/davidmacd<http://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>