That's a very interesting idea.
Note that for errormessage, we can first test for the invalid state, so
this wouldn't help that. (The bigger problem there is walking the tree
to get the message from the target.)
What do you think about using an object attribute (or attributes) to do
this, rather than a separate bit mask? That way, it's much easier to add
new ones. Also, I'm guessing most AT (certainly screen readers) already
have to fetch attributes anyway, so this avoids an extra call.
Thanks!
Jamie
On 7/09/2016 8:42 AM, Dominic Mazzoni via Accessibility-ia2 wrote:
One of the objections Jamie brought up to making aria-errormessage an
additional interface is that it increases the number of interfaces AT
needs to call on every single accessible. I've also thought about this
same issue, as the number of nodes in an average web page continues to
grow along with the number of interfaces in IA2.
What would folks think of adding some sort of bitmask to allow AT to
quickly test for the presence of lots of properties at the same time?
Something like:
HRESULT propertyBitmask([out, retval] IA2PropertyBitmask *bitmask)
enum IA2PropertyBitmask {
IA2_HAS_NAME = 0x01,
IA2_HAS_DESCRIPTION = 0x02,
IA2_HAS_ERRORMESSAGE = 0x04,
...
}
One could imagine variants of this, for example AT could fill in the
bitmask with properties it's interested in, and the browser would only
have to compute those.
- Dominic
_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: ja...@nvaccess.org
_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
