W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2016

RE: How 1.4.4 Resize text applies when mobile templates kick in

From: Matthew Putland <matthew.putland@mediaaccess.org.au>
Date: Thu, 3 Nov 2016 02:36:28 +0000
To: "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <175A0C3A8A81CC4AA58A058F62066E530402EEED@SERVER01.mediaaccess.local>
Hi All,

Thanks for all your responses. When testing websites against 1.4.4 Resize text, I will allow any structure or presentation of the content, as long as the content itself is still present when zoomed in. I also completely agree that if a web component is only available on the desktop-template, but cannot work on the mobile-template, then it shouldn't be on the desktop-template at all. However, in discussion with organizations and their web developers, stating this has often been a hard pill for them to swallow. 

Something like an embedded twitter feed could be removed on mobile to prevent touch-screen users from getting stuck in a massive list of tweets. Sure, the twitter feed could fit in the mobile viewport, but it may not work too well on mobile, so they remove it. I never liked those horrible huge embedded twitter feeds anyway!

I'm satisfied, Thanks again for your input and thoughts.


Matthew Putland
Senior Analyst, Digital Accessibility | Media Access Australia 
61 Kitchener Avenue, Victoria Park WA 6100
Tel: 08 9311 8230 (direct) 02 9212 6242 (main) Mobile: 0431 924 288 Web: www.mediaaccess.org.au

My working hours are from 11am-7:30pm AEST (8am-4:30pm AWST).

Media Access Australia - inclusion through technology and Access iQ® - creating a web without limits. Follow us on Twitter @mediaaccessaus @AccessiQ 

-----Original Message-----
From: Patrick H. Lauke [mailto:redux@splintered.co.uk] 
Sent: Thursday, 3 November 2016 4:18 AM
To: w3c-wai-ig@w3.org
Subject: Re: How 1.4.4 Resize text applies when mobile templates kick in

On 02/11/2016 17:12, Phill Jenkins wrote:
> "Often the mobile/tablet version of websites do not contain the same 
> content as the desktop version."
> Can you give some example?
> I've seen complex grids turn into card views as a result of narrowing 
> the browser width (not zoom) on a desktop, all the information, but 
> formatted very differently.
> My interpretation of "without loss of content or functionality" does 
> _not_ include exact same format, or exact same relative place of 
> information.  We should encourage reflow of format and responsive 
> design in my opinion.
> and a question for the group:  if we interpret that 1.4.4 must keep 
> all the information in the same relative place, then keeping all that 
> information in complex grid formats (e.g. data tables) will require 
> left-right scrolling.

I don't think anybody's interpreting 1.4.4 in that way, no.

> Usually responsive design keeps all the information and all the 
> functionality.  However, there are examples of only have one search 
> instead of two, or only one set of footer links, or you have to really 
> scroll down to find all the sections, of there is no longer the sub 
> menus requiring a person to select a menu item to determine its sub 
> menu
> - is that a loss of functionality - no in my opinion because it still 
> requires one and only one user interaction,  We need more specific 
> examples to better discuss this than general statements.

That's not a loss of content/functionality, no. It may require more/different steps to get to, but it's still there/workable.

Related, I think a lot of the ground of this was covered in great detail on this other thread earlier in the year https://lists.w3.org/Archives/Public/w3c-wai-gl/2016AprJun/0889.html

(warning: long read, with branching parallel discussions...but the end result is pretty much what we've said already in short here - the small-screen/small-viewport version, which is also triggered on large screens when user zooms in browser or makes their browser window smaller than their large desktop monitor, must have the same content/functionality)

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 Thursday, 3 November 2016 02:37:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:01 UTC