- From: Patrick H. Lauke <redux@splintered.co.uk>
- Date: Wed, 29 Jun 2016 15:08:55 +0100
- To: WCAG <w3c-wai-gl@w3.org>, "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>
On 29/06/2016 14:51, David MacDonald wrote: > *Note 8: Sometimes specifically optimized views are delivered to the > user agent based on screen size, device type, etc. A WCAG conforming > view linked from such an optimized view could only be considered a > conforming alternative if it has the same functionality as this > optimized view. For example, a large screen view with a complicated > menu, more content, or additional interface elements would not be a > conforming alternative to a view optimized for small screen because the > two have different functionality. There's a danger here of directly contradicting Note 2 (though the note seems to be aimed at the "other way", going from a complex to a simplified version) "The alternate version does not need to be matched page for page with the original (e.g., the conforming alternate version may consist of multiple pages)." https://www.w3.org/TR/WCAG20/#conforming-alternate-versiondef So even if there are "more content", "additional interface elements" etc in the alternate version, it counts as alternate version under the current definition/note 2. P -- Patrick H. Lauke www.splintered.co.uk | https://github.com/patrickhlauke http://flickr.com/photos/redux/ | http://redux.deviantart.com twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Wednesday, 29 June 2016 14:09:28 UTC