Text autosizer favors "paragraphs" based on a heuristic but doesn't affect the rest, so we believe page zoom should perform more consistently.  This setting is not very popular but we've received a few complaints about it.

+klobag who mentioned this morning the current accessibility slider isn't very effective (often doesn't make text large enough to read for poor eyesight users even at 150%/200%).

 Issue 694579  has been merged into this issue.

 Issue 569083  has been merged into this issue.

Must we scale only text? or also other DOM elements (e.g., images).
I am considering applying this change only to font or to localframe's page zoom factor.

We should scale every DOM element (images, etc).  Any method that scales only fonts will cause layout bugs, and avoiding these layout bugs is one of the reasons to switch.  The page zoom will naturally scale everything (in fact it would be very difficult to make it scale only fonts).

Hi, I'd like to understand this a bit more. 

I couldn't find the font scale factor in chrome accessibility section. Is this different from font size in Appearance section?

It sounds like you're looking at desktop Chrome, but this feature is Android-specific.

Starting from NYC, Android has Display Size settings in Accessibility, which changes density instead. I think that'll do the same thing?

Yes, that's more or less the same thing.  (I have no objection to an outcome where we would delete this slider as redundant instead of improving it.)

I will discuss this issue with oshima@ in offline

+zork@ who is in charge of android accessibility.

I think it's best to use the system preference as the canonical way to enable this feature.  Having a consistent experience across the system is preferable to a Chrome specific setting, in my opinion.

+1, I agree with zork@.
pdr@, could you give us your opinion?

+1, I like using the system accessibility slider.

Just to make sure I understand though.. we'll still want to make the accessibility slider use page zoom instead of text autosizing, right? The most important usecase to me is google.com search results which do not currently change with the system accessibility slider.

I'm very excited about this change because it seems Chrome will finally respect android system font size setting, but 1 quick question: this Android setting, is it Settings > Display > Font size or is it under the Accessibility section? Or are those 2 the same thing?

My apologies for double posting, the only issue I can think of is, Chromes text scaling offers very fine grained control in increments of 5%, where as the Android system wide font size settings seems to be in much larger chunks (approx 20%?). Could the Android text size slider be changed to give this fine granular control of text size like Chrome currently does?

Removing owner who has left the team.

@Donimic, is this something your team could take a look at? I think this is an important issue because top sites like google.com do not respect the accessibility slider.

 Issue 766213  has been merged into this issue.

dmazzoni@, #31 intended to ask you, but went to a wrong Dominic.

I was talking to pdr@ in https://chromium-review.googlesource.com/c/chromium/src/+/994495 , we might need do something in LayoutNG.

IMO, zooming and scaling layout punishes web developers that actually support text scaling.

Accessibility text scaling shouldn't be any different to desktop the version. If web developers want to force font sizes, Chrome shouldn't mess around with that. We shouldn't be trying to fix bad code.

Here's what's happening when I try using proper, accessible text scaling:

Compare what Chrome for Desktop shows when emulating a Pixel 2 XL, vs an actual Pixel 2 XL:

(See attached)

On iOS devices, I just have to use `font: -apple-system-body;` and the browser will respect the system-wide accessibility font scaling. It won't mess around with my layout.

Deleted: emulated.png 977 KB

	emulated.png 977 KB View Download

Deleted: real-device.png 1.1 MB

	real-device.png 1.1 MB View Download

If you want to use the website I use for testing, you can use my Material Design framework. (where I referenced the screenshots)

https://clshortfuse.github.io/materialdesignweb/textfield.html

Nothing scales when I play with the Chrome accessibility settings in Android. Chrome Desktop, and iOS devices work fine. Even old versions of IE work fine.

Bulk edit**

This bug has the label Postmortem-Followup but has not been updated in 3+ weeks. We are working on a new workflow to improve postmortem followthrough. Postmortems and postmortem bugs are very important in making sure we don't repeat prior mistakes and for making Chrome better for all.

We will be taking a closer look at these bugs in the coming weeks. Please take some time to work on this, reassign, or close if the issue has been fixed. Thank you.

Any updates?

For reference, Firefox on Android has an option to scale text with AndroidOS font settings.

Safari on iOS has no problems using text scaling.

Every modern browsers, be on it desktop or mobile applies the standard way of scaling font, EXCEPT for Chrome for Android. If you Chrome is going to break precedent and go about implementing its own custom text scaling option, it should be optional. There's no reason to reinvent the wheel here.

I have duped many of the scaling not working bugs into master bug 779409. I then made this feature related bug blocking the font scaling not working bug. 

Bug 779409 consolidates all the user complaints about the feature not working 
Bug 645717 (this one) explores the solution to making text scaling work 

 Issue 877833  has been merged into this issue.

Is there any update on this bug? It’s an accessibility bug blocking several other bugs, some of which are also accessibility bugs, and there is no workaround. Even “use a different browser like Opera” isn’t a valid workaround because there’s no way to replace WebView for other apps that use it.

Apologies if I'm mistaken but I think Chrome for Android getting 'zoom for DSF' was one of the things holding this up? If so, zoom for dsf on android finally seems ready to ship so that's positive 

> For reference, Firefox on Android has an option to scale text with AndroidOS font settings.

... which, when toggled on, uses font inflation (the Firefox implementation of text autosizing) as well when dealing with non-mobile/Desktop pages, though.

Yes, which is how every other browser (including Safari Mobile) besides Chrome for Android handles font scaling. It's also how Chrome for Desktop works when debugging for mobile.

Firefox's automated font inflation (aka font-boosting) is something different. That's done on pages designed for desktop (no viewport meta) that are being read on a mobile device.

Opting for scaling (actually zooming) content is something different. Just because a user wants larger fonts it doesn't mean they want everything else larger (like buttons).

Chrome team, Is there any update on this issue please?

Chrome team ,could you please update the bug?

dmazzoni@/pdr@: Could you please respond to comment#43, c#47, c#48.