> > James, Dominic, how should we go about defining the mappings on iOS and > Android? Is there someone in your organizations who we could work with to > define the mappings. > This is something I've been working on with the Android team. The current Android accessibility API isn't rich enough to support everything in web accessibility, so we're working on enhancing it in the next version - and in the meantime we'll provide forwards compatibility by defining mappings that use the flexible "Bundle" (a data structure that lets you add additional attributes of any time). The most common web elements and controls can be mapped now, though, so I'm happy to help provide some guidance on those while we're figuring out the rest. iOS seems like a bit of a different situation since Apple doesn't allow third-party web rendering engines - it might be interesting to know how some HTML elements are mapped, but it's less practical because nobody can create an alternative implementation.
Received on Tuesday, 31 March 2015 15:20:48 UTC