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

RE: Allowing font size changes

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Fri, 15 Jan 2016 15:15:52 +0000
To: Alistair Garrison <alistair.j.garrison@gmail.com>
CC: "Durham, Heather" <heather.durham@pearson.com>, Michiel Bijl <michiel@agosto.nl>, "Patrick H. Lauke" <redux@splintered.co.uk>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Message-ID: <BY2PR03MB272F63D346830267138A7059BCD0@BY2PR03MB272.namprd03.prod.outlook.com>
  If only the text is increased in size this horizontal scroll issue can generally be avoided.

Agreed, I'd rather use large text than zoom.  This is something I believe will be addressed by the low vision task force in the WCAG working group.

I also believe on page controls can be useful.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com
703.637.8957 (o)
Follow us: Facebook<http://www.facebook.com/#!/ssbbartgroup> | Twitter<http://twitter.com/#!/SSBBARTGroup> | LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog> | Newsletter<http://eepurl.com/O5DP>

From: Alistair Garrison [mailto:alistair.j.garrison@gmail.com]
Sent: Friday, January 15, 2016 10:10 AM
To: Jonathan Avila
Cc: Durham, Heather; Michiel Bijl; Patrick H. Lauke; w3c-wai-ig@w3.org
Subject: Re: Allowing font size changes

Hi,

I agree that page zoom is not the same as independently scaling page text.

I also agree that page zoom under G142 can be used to meet SC 1.4.4.  But, I'd just add that it is also good to be aware that the horizontal scroll that is often a zoom by-product can cause significant accessibility issues by itself.

If only the text is increased in size this horizontal scroll issue can generally be avoided.

Alistair

On 15 Jan 2016, at 14:41, Jonathan Avila wrote:


>  I skimmed 1.4, but that doesn't seem to say whether text should be scaled independently from he layout. In other words, is page zoom equal to text scaling?

Page zoom (if not blocked or disrupted by the author) can be used to me SC 1.4.4 resize of text.  People may disagree on this - but this is current the case through sufficient techniques that were created by the WCAG working group.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com<mailto:jon.avila@ssbbartgroup.com>
703.637.8957 (o)
Follow us: Facebook<http://www.facebook.com/#!/ssbbartgroup> | Twitter<http://twitter.com/#!/SSBBARTGroup> | LinkedIn<http://www.linkedin.com/company/355266?trk=tyah> | Blog<http://www.ssbbartgroup.com/blog> | Newsletter<http://eepurl.com/O5DP>

From: Durham, Heather [mailto:heather.durham@pearson.com]
Sent: Friday, January 15, 2016 9:30 AM
To: Michiel Bijl
Cc: Patrick H. Lauke; w3c-wai-ig@w3.org<mailto:w3c-wai-ig@w3.org>
Subject: Re: Allowing font size changes

Page zoom is different from font size change.

On Thu, Jan 14, 2016 at 5:23 AM, Michiel Bijl <michiel@agosto.nl<mailto:michiel@agosto.nl>> wrote:

> If you think it's the web content author's job to patch up hidden/insufficient functionality of browsers on tablets/smartphones, then sure, adding a custom in-page tool for text resizing is the way to go. Personally, I tend to think it's the responsibility of UA developers to provide functionality like that to their users (e.g. https://www.w3.org/TR/UAAG20/#g-1-4)

I agree that this should be a UA thing. I'm merely asking if such a functionality is available in tablets, smartphones, etc. For example, iOS offers a Text Size option under Display settings in settings.app, but that doesn't translate to web content. I'm not familiar with any option on any mobile platform that offers such a functionality (text size for web content).

I skimmed 1.4, but that doesn't seem to say whether text should be scaled independently from he layout. In other words, is page zoom equal to text scaling?

-Michiel






--
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/>
Received on Friday, 15 January 2016 15:16:37 UTC

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