Hi Dominic,
Thank you. Is it reasonable to plan for Android support in the ARIA 1.1
time frame which will be, I am guessing, some time in 2016 to be a
recommendation?
Best,
Rich
Rich Schwerdtfeger
From: Dominic Mazzoni <dmazzoni@google.com>
To: Richard Schwerdtfeger/Austin/IBM@IBMUS
Cc: Joseph Scheuhammer <clown@alum.mit.edu>, James Craig
<jcraig@apple.com>, Michael Cooper <cooper@w3.org>, "W3C WAI
Protocols & Formats" <public-pfwg@w3.org>, Shane McCarron
<shane@aptest.com>, W3C WAI-PFWG <w3c-wai-pf@w3.org>
Date: 03/31/2015 10:21 AM
Subject: Re: ACTION-1279: Talk to mobile manufacturers about how to
include their apis
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.
