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

Re: Allowing font size changes

From: Chaals McCathie Nevile <chaals@yandex-team.ru>
Date: Mon, 18 Jan 2016 20:51:22 +0100
To: w3c-wai-ig@w3.org
Message-ID: <op.ybf9fwqcs7agh9@widsith.local>
On Fri, 15 Jan 2016 15:46:19 +0100, Patrick H. Lauke  
<redux@splintered.co.uk> wrote:

> But as ever, it comes down to whose responsibility it is? Should it be  
> the content authors, or the device/OS/browser manufacturers?

The OS and browser are each broken if they don't provide a way to increase  
font size, and zoom - yes they are different. And both have important uses.

I'm not sure there is any absolute requirement that authors add a  
redundant shortcut to do the same, but in practice it can be a useful  
thing for many users, especially given that in practice many OS and  
browser soutions are hard to find or use.

IMHO.

chaals

> P
>
> On 15/01/2016 14:40, ALAN SMITH wrote:
>> Heather,
>>
>> I agree.
>>
>> Imaging having to set the volume on our devices in a settings somewhere
>> and constantly return to that setting after we find out it is not enough
>> or too much and not having the immediate feedback afforded by volume
>> buttons or onscreen controls.
>>
>> Same should be provided for fonts.
>>
>> After all, the text on the web page or app is the main mode of
>> communication or human computer interaction.
>>
>> It is why we use these devices anyway: to be able to read the text being
>> used.
>>
>> The world population that needs this is so big.
>>
>> Regards,
>>
>> Alan
>>
>> Sent from Mail <http://go.microsoft.com/fwlink/?LinkId=550986> for
>> Windows 10
>>
>>
>> *From: *Durham, Heather <mailto:heather.durham@pearson.com>
>> *Sent: *Friday, January 15, 2016 9:25 AM
>> *To: *howard_leicester@btconnect.com  
>> <mailto:howard_leicester@btconnect.com>
>> *Cc: *Patrick H. Lauke <mailto:redux@splintered.co.uk>;
>> w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org>
>> *Subject: *Re: Allowing font size changes
>>
>> What will be the plan for the app? Will it be widely used on mobile
>> devices? In mobile devices you can increase the font size, but it's not
>> as convenient as in a web page. On mobile devices you need to go to the
>> settings app and you can't see how the font size looks live as you
>> adjust it. For people who have difficulty navigating, it could be a real
>> convenience to tap a button to increase the font size right there in the
>> app their using.
>>
>> This could also be a nice feature for other uses, such as those with
>> autism. I attended an autism conference in the summer and this was
>> something that was widely discussed. The convenience of reducing the
>> number of steps to accomplish something.
>>
>> Thanks,
>>
>> Heather
>>
>> On Thu, Jan 14, 2016 at 3:22 PM, Howard Leicester
>> <howard_leicester@btconnect.com <mailto:howard_leicester@btconnect.com>>
>> wrote:
>>
>>     Hi P et al,
>>
>>     Do things really have to be so detailed and difficult?
>>
>>     May be there's some more fundamentally wrong in our approach?
>>
>>     No criticism, just a view!
>>
>>     VV best,
>>     Howard (Leicester, UK).
>>
>>
>>
>>     -----Original Message-----
>>     From: Patrick H. Lauke [mailto:redux@splintered.co.uk
>>     <mailto:redux@splintered.co.uk>]
>>     Sent: 14 January 2016 01:23
>>     To: w3c-wai-ig@w3.org <mailto:w3c-wai-ig@w3.org>
>>     Subject: Re: Allowing font size changes
>>
>>     On 14/01/2016 00:52, Oscar Cao wrote:
>>     > I want to get what everyone's views are on the importance of  
>> having
>>     > custom font size buttons for a website. You know those 3 icon  
>> buttons:
>>     > smaller, medium, and larger.
>>
>>     Very low from my point of view. It's functionality built into the
>>     browser already, so provided a site's CSS is made correctly, these
>>     in-page controls would be redundant.
>>
>>     There is an argument that users simply don't know that they can  
>> resize
>>     text/content using the browser controls - but this is more of a user
>>     education issue that should not have to be the responsibility of  
>> content
>>     authors. (same for in-page/custom controls to switch to high  
>> contrast
>>     mode or similar)
>>
>>     P
>>     --
>>     Patrick H. Lauke
>>
>>     www.splintered.co.uk <http://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
>>
>>
>>
>>
>> --
>>
>> Heather Durham
>>
>> Accessibility SQA, HEd
>>
>> Pearson North America
>>
>> 2154 East Commons Ave.
>>
>> Suite 4000
>>
>> Centennial, CO
>>
>> 80122
>>
>> USA
>>
>> *Pearson *
>>
>> Always Learning
>> Learn more at www.pearson.com <http://www.pearson.com/>
>>
>
>


-- 
Charles McCathie Nevile - web standards - CTO Office, Yandex
  chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Monday, 18 January 2016 19:51:58 UTC

This archive was generated by hypermail 2.3.1 : Friday, 29 January 2016 16:39:04 UTC