Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stacked SC: SC 1.4.4: Resize text AND 1.4.3: Contrast and zoom Native UA elements? #1523

Closed
jake-abma opened this issue Nov 13, 2020 · 4 comments

Comments

@jake-abma
Copy link
Contributor

When I change the size of a default Select element to 200% I get the following result in Firefox:

Screen Shot 2020-11-13 at 11 42 37 AM

The text is clipped in the options popup / panel
The contrast of the black on the blue is not 4.5:1

Do we fail both 1.4.4 and 1.4.3?
There is no exception for native UA elements.

@JAWS-test
Copy link

I would consider it a failure (at 1.4.4 or 1.4.3). But the problem does not occur with in my testing environment (Windows 10). The select element is scaled correctly when zooming in the browser and when resizing text in Firefox

@jake-abma
Copy link
Contributor Author

jake-abma commented Nov 13, 2020

I used: https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_select

On a Macbook...

But if I copy the select code in: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/select

I get same bad results...

Copy / paste code in developer.mozilla.org page and set text resize only to 200%

Volvo Saab Opel Audi ****

Screen Shot 2020-11-13 at 12 16 57 PM

@patrickhlauke
Copy link
Member

In terms of 1.4.4, a tricky one, because as you say the SC normatively doesn't exempt color choices made by the UA. There is a little note in the key term definition for color contrast

WCAG conformance should be evaluated for color pairs specified in the content that an author would expect to appear adjacent in typical presentation. Authors need not consider unusual presentations, such as color changes made by the user agent, except where caused by authors' code.

but that doesn't seem to fully exempt this particular scenario ... though it can be argued that without additional styling, it should be up to the user agents to make sure they use sufficiently contrasty foreground/background.

Likewise for 1.4.3 (and probably also 1.4.10) the user agent should really strive to avoid loss of content like that.

Fundamentally, these feel like UAAG failures (if UAs actually cared for UAAG), but of course at the end of the day it's end users that miss out on content, regardless who gets the blame.

@jake-abma
Copy link
Contributor Author

yep, another exempt here... while the content creator 'can' fix it for the user need, smells like Silver... thx @patrickhlauke

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants