- From: David MacDonald <david100@sympatico.ca>
- Date: Mon, 4 Jul 2016 07:23:39 -0400
- To: "public-mobile-a11y-tf@w3.org" <public-mobile-a11y-tf@w3.org>, WCAG <w3c-wai-gl@w3.org>
- Message-ID: <BLU436-SMTP24365D95F309F9E7D6F94E2FE380@phx.gbl>
This thread *may* below on LVTF which I'm not signed up for. but its perhaps also a mobile issue. Jonathan says: >Responsive versions may have different functionality and some low vision users are forced into breakpoints by using zoom or low resolution they may not have access to content that would appear on other’s desktops even when they are using a desktop and that they can’t get the desktop functionality with their level of zoom or resolution – that remains an issue. Given Patrick's definition of the different types of responsive, we should get an idea of which types of responsive more commonly drop content on a small screen version. - Pure CSS breakpoints - JavaScript which mimics/uses CSS breakpoints -UA sniffing on the server side Would we want to require ALL the content from the desktop on the responsive site? It may be optimized for a different use case than the desktop view, people on the go trying to complete a task without clutter... and people with cognitive disabilities may appreciate less content... We may want to develop a simple toggle switch that adds the dropped content that was on the desktop view when responsive kicks in WITHOUT forcing it back to the desktop view which requires horizontal scroll on zoom in ... if we make it easy, then perhaps we can require it? Cheers, David MacDonald *Can**Adapt* *Solutions Inc.* Tel: 613.235.4902 LinkedIn <http://www.linkedin.com/in/davidmacdonald100> twitter.com/davidmacd GitHub <https://github.com/DavidMacDonald> www.Can-Adapt.com <http://www.can-adapt.com/> * Adapting the web to all users* * Including those with disabilities* If you are not the intended recipient, please review our privacy policy <http://www.davidmacd.com/disclaimer.html>
Received on Monday, 4 July 2016 11:24:11 UTC