RE: WAPA proposal related to ARIA and the DOM?

I do have one question about this for when you have time, which is somewhat confusing.

In the description, it states “WAPA allows the ARIA attributes to be added in response to an Accessibiltiy API call, rather than for all users.”

If ARIA state attributes are only updated when an AT explicitly requests it, how then is it possible to bind CSS styling to related ARIA attributes for all users?

E.G http://whatsock.com/training/#hd11

Thanks,
Bryan

From: Cynthia Shelly [mailto:cyns@microsoft.com]
Sent: Thursday, May 14, 2015 4:46 PM
To: Bryan Garaventa; PF
Subject: RE: WAPA proposal related to ARIA and the DOM?

Yes, it's moving forward. We're working on this as a proposal to webapps to replace parts of indieui.  Once the charters are nailed, and some day job responsibilities are behind me, we'll be developing it further.

Sent from my Windows Phone
________________________________
From: Bryan Garaventa<mailto:bryan.garaventa@ssbbartgroup.com>
Sent: ý5/ý14/ý2015 1:49 PM
To: PF<mailto:public-pfwg@w3.org>
Subject: WAPA proposal related to ARIA and the DOM?
Hi,
I just wished to ask if the WAPA proposal is still moving forward?
https://github.com/cyns/wapa

By the way, within the intro document, the role=”listbox” code example should have children of role=”option” and not role=”listitem”.

:)

Received on Friday, 15 May 2015 16:31:12 UTC