- From: <bugzilla@jessica.w3.org>
- Date: Thu, 16 Oct 2014 15:51:48 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27086 Bug ID: 27086 Summary: HTML to Platform Accessibility APIs should include iOS and Android mappings Product: HTML WG Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal Priority: P2 Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) Assignee: faulkner.steve@gmail.com Reporter: dmazzoni@google.com QA Contact: sideshowbarker+html-a11y-api@gmail.com CC: mike@w3.org, public-html-admin@w3.org, public-html-bugzilla@w3.org, public-html-wg-issue-tracking@w3.org A larger share of web usage is on mobile, and in addition to use of mobile web browsers, many mobile apps use web views to implement part of their interface. We should include iOS and Android mappings for all HTML elements too. On iOS, Apple's WebKit implementation is the only one allowed to display web content - alternative web browsers based on a different engine are not currently allowed. Still, I think it'd be useful to spec for several reasons: * To help catch bugs in Apple's implementation * To clarify the expected mappings and behavior for HTML authors, especially app authors who need native content and web content to interoperate * In case Apple relaxes the rules in the future and allows alternative web implementations -- You are receiving this mail because: You are on the CC list for the bug.
Received on Thursday, 16 October 2014 15:51:50 UTC