Hi again, I want to raise this issue in parallel to the IA2_ROLE_NOTE thread. I don't want to complicate that discussion since this one might take fair bit longer to resolve.
One of the IA2 object attribute pairs that FF exposes is the aria roles string. So for example: <div role="navigation"> Will have the object attribute xml-roles=navigation. (I apologize for the "xml-" prefix, but that prefix is there for purely historical reasons as I understand it and is tangential to this discussion.) Now, one of the things we do for html landmarks like <nav> is expose it like we would the aria role=navigation, via an xml-roles object attribute. This allows AT that already work with our xml-roles (based on aria) to "just work" with <nav>. A couple of questions: 1. Should we strive to add roles to the IA2 spec such that we don't need to expose the role as an object attribute? 2. Should we promote the object attributes method as a first class solution and standardize how they are implemented? 3. Are landmark roles distinct enough to warrant a distinct way of exposing them? Hoping to hear thoughts from everyone, including AT devs. Cheers, David _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
