- From: White, Jason J <jjwhite@ets.org>
- Date: Fri, 15 Jul 2016 17:22:16 +0000
- To: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
> -----Original Message----- > From: Patrick H. Lauke [mailto:redux@splintered.co.uk] > Sent: Friday, July 15, 2016 12:53 PM > > Related, there is a stub of a proposed new SC and a technique for it in the > Mobile Accessibility TF document > > "[Proposed New MOBILE Success Criteria] 4.1.3 Non-interference of AT: > Content does not interfere with default functionality of platform level assistive > technology > > Mobile Technique proposed for WCAG 4.1.3 > M007: Supporting the characteristic properties of the platform (e.g. > zoom, larger font, captions)" > > I'm not quite sure it belongs in mobile itself (the technique probably, but not the > overarching SC, so I filed a bug against that. [Jason] What would be a good example of Web content that fails to satisfy this proposed SC? Wouldn't it be a platform-level bug if Web content can interfere with the operation of accessibility features? ________________________________ This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited. Thank you for your compliance. ________________________________
Received on Friday, 15 July 2016 17:22:46 UTC