Re: [w3ctag/design-reviews] Other Spec Review: [css-text] `text-fit` property (Issue #1208)

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

Hi @tkent-google, thanks for your review request, and sorry for the long response time. We acknowledge the aesthetic use case for this feature. We have some questions... 
  
1. This feature introduces quite a bit of nondeterminism into layouts. How will this affect DX, and authors' ability to test layouts?

2. [Text that gets too big can be just as problematic as text that gets too small.](https://github.com/w3c/wcag3/issues/261#issuecomment-2598860620). Just one common user scenario: a person may be zoomed into the web page _and_ zoomed into the screen (via full-screen magnification). This is already a complex and tiring set-up, with parallax scrolling, and the cognitive (and physical) load that comes with it. If text is being scaled significantly, it could make it much harder to read.

   - Note: The current WCAG 3 draft changes the text-resizing requirement from "[text can be resized without assistive technology up to 200 percent](https://www.w3.org/TR/WCAG22/#resize-text)" to "[Text can be increased in size to at least 200% of the platform’s default body-text size.](https://www.w3.org/TR/wcag-3.0/#text-size-adjustable)", which offers a new angle for how to make this CSS feature compliant. But WCAG 3 is some way off.

   - There's [some discussion in CSSWG around what to do about this](https://github.com/w3c/csswg-drafts/issues/12886) but it doesn't look like a resolution has been reached. Does that thread represent the latest thinking on this issue? It has been quiet for several months.

3. Research/discussion is ongoing within APA on this: we have some concerns about the difficulties this could cause for readability, particularly for people with cognitive disabilities. It could also affect people who need high zoom levels.

   - This may be quite profound for some users, and we would suggest that UAs allow the feature to be toggled off by the user, in order to improve legibility. However that in turn raises a fingerprinting question.

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

Message ID: <w3ctag/design-reviews/issues/1208/5346062656@github.com>