search

w3c / wcag

Web Content Accessibility Guidelines
https://w3c.github.io/wcag/guidelines/22/
Other
1.14k stars 256 forks source link

F80 code example doesn't fail #3558

Open kengdoj opened 1 year ago

kengdoj commented 1 year ago

https://www.w3.org/WAI/WCAG22/Techniques/failures/F80

At 400% zoom with Chrome and Edge, everything including the input field text increased.

JAWS-test commented 1 year ago

This is only true if the browser zoom is changed directly. However, if a different font size is selected in the browser, the inputs are not displayed enlarged

JAWS-test commented 1 year ago

However, it would be even better if it were used input {font-size: 1vw;} instead, because then the input would not scale even with browser zoom

patrickhlauke commented 1 year ago

This is only true if the browser zoom is changed directly.

and since 1.4.4 doesn't require a specific approach, but only that there be a way to enlarge text, this technique passes. agree that it should either be changed or removed /cc @alastc

bruce-usab commented 1 year ago

Any other ideas for failure techniques illustrating how author might break browser zoom?

Thanks @JAWS-test for 1vw as simple substitution! I tried 12px (instead of 12pt) but browser zoom worked fine.

Jym77 commented 7 months ago

Same problem with the example in F69, they work perfectly fine with browser zoom and only break with font size change (vw font size doesn't do the trick here since it makes the text overflow on small zoom and fit on big zoom; vh height on the containers does).

With all modern desktop browsers allowing zoom and thus passing G142, does 1.4.4 boils down to "be careful with viewport relative units" 🤔