Re: [w3ctag/design-reviews] Other Spec Review: <meta name="text-scale" content="scale" /> (Issue #1172)

matatk left a comment (w3ctag/design-reviews#1172)

Thank you @davidsgrogan and @JoshTumath for your replies, clarifications, and updates to the explainer, and spec. There's one thing on which I think I was not clear, and would like to check with you...

The current draft has the `legacy` and `scale` modes. The explainer mentions a possible `progressive` mode that could be added in future. But would it really be needed?

I think you've both answered the question "Could the UA try to decide if a legacy page could be scaled (without breakage, or burdensome scrolling)?" - I wasn't meaning to ask that question, but your answer is interesting, and encouraging.

The question I meant to ask is: "Given a page that opts into linear scaling via `scale`, wouldn't you expect that its layout would be more robust, and thus be able to cope with the non-linear scaling (described as `progressive` in the explainer) at any time, as determined by the UA, and user's preferences?"

An accessibility concern I have here is that I think the user ought to have control over what type of scaling they need (UAs could even offer control over the scaling factors, if they liked - I think I would find this useful). So even if other scaling modes are added in future, what I'm asking for is to allow the UA to always be able to make the final decision as to how to scale the fonts. (That aligns with the SHOULD in the spec that you highlighted.)

(Due to the breakage issues such as those you found, I wasn't meaning to include `legacy` pages in this, but if experimentation reveals UAs _could_ actually reliably determine that no two-axis scrolling would be needed for a given layout, it would seem to be fine to allow UAs to make the decision on `legacy` pages, too.)

Particularly regarding `scale` vs future additional modes: I hope that clears things up - how does it sound to you?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1172#issuecomment-3765794376
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1172/3765794376@github.com>