- From: James Craig via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Jan 2022 02:12:59 +0000
- To: public-css-archive@w3.org
> [the problem] exists any time text is scaled more than the proportionate increase in the viewport or container. Okay. That I understand, but it may be difficult to achieve consensus. One example why is that Safari for Mac has a text-only variant of this feature... (Open the View Menu and hold the Option key to see this.) By definition, changing the text size only will be disproportionate to other layout metrics. How would you propose reconciling your example layouts while still preserving a user's ability to adjust the font to a size that works best for them using a "text-only" increase? It sort of sounds like you're asking for the ability to cap a font size based on some proportional range, similar to how some iOS apps support Dynamic Type, but limit some views within the constraints of the layout. For example, the iOS Calendar app can shift between showing 1, 2, or 3 month grids horizontally, but beyond that, increasing the font size would cause overlap, so a top range is reached. A calendar grid isn't a calendar if the weeks wrap, or the numbers are unreadable! | 3 Months Across | 2 Months Across | 1 Month Across | | --- | --- | --- | |  |  |  | Previous suggestions for something like a `max-font-size` in em/rem would allow this, but if I recall correctly, the various W3C WGs rejected the proposals because `max-font-size` would be too easy for authors to abuse at the expense of user need. That said, if your need is too constrain some reasonable font size within some critical structural layout (including but not limited to tables), I support finding a good solution. In the screen shots above, a calendar grid isn't a calendar if the weeks wrap. I didn't think any of the layouts you posted were _critical_ for conveying the information, though I acknowledge an inability to have fine control over visual hierarchy is frustrating. Am I getting closer to the core need of your issue? Or are we still out-of-sync? > This issue is not an uncommon issue, and it has an active thread with [WCAG](https://github.com/w3c/wcag/issues/1671). I opened this issue as a proposal to solve this. I'm aware of that thread, but I don't see your proposed solution as solving exactly the same issue. -- GitHub Notification of comment by cookiecrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6869#issuecomment-1009536280 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 January 2022 02:13:01 UTC