On 12/04/2016 3:26 AM, Joanmarie Diggs wrote:
If there's sufficient belief that errormessage is inherently different
FWIW, I don't believe this personally--I've not seen a single argument
that I wasn't able to defeat--but it seems like this decision has
already been made in ARIA. Certainly, NVDA will just be merging it into
description internally. What I will say is if ARIA views it as being
fundamentally different (as misguided as I think this is), it seems
problematic if the accessibility APIs merge it.
That said, one nasty problem with an additional API or relation is that
we have to call/crawl that additional thing for *every* accessible just
to find out whether it has an error message. That's kinda ugly from a
performance perspective; we hurt performance everywhere just to support
aria-errormessage. Still, I guess this is the best we can have given the
majority opinion that it is so fundamentally different.
I'm happy with the names you proposed.
Jamie
--
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: [email protected]
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
