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

WCAG 2.1 Understanding 2.3.1 - missing/vague dimension definitions #585

Closed
patrickhlauke opened this issue Jan 16, 2019 · 5 comments · Fixed by #2127
Closed

WCAG 2.1 Understanding 2.3.1 - missing/vague dimension definitions #585

patrickhlauke opened this issue Jan 16, 2019 · 5 comments · Fixed by #2127

Comments

@patrickhlauke
Copy link
Member

In https://www.w3.org/WAI/WCAG21/Understanding/three-flashes-or-below-threshold.html it mentions

The 1024 x 768 screen is used as the reference screen resolution for the evaluation. The 341 x 256 pixel block represents a 10 degree viewport at a typical viewing distance.

This omits / handwaves one fairly important aspect: saying that a monitor is "1024 x 768" is mostly meaningless without any physical dimensions of the monitor itself. I can set a giant cinema display to run at "1024 x 768", or a super-small LCD screen. Unless a monitor size itself is defined, or the "typical viewing distance" is explained (would this "typical distance" be the one that results in the pixels matching up with the definition for the "reference pixel"?), this is very vague.

I seem to remember discussion ages ago that this SC/Understanding's wordings came from a time when 1024x768 was the norm/top-end, and "most" monitors were generally of a certain size (14" or so?) ... but now, this feels strangely anachronistic without any anchoring/rationale behind it.

@alastc
Copy link
Contributor

alastc commented Jan 18, 2019

Hi Patrick,

So is the question about the original rational, or primarily about converting it to a more modern size?

The first might take some digging, but taking the rational of the time I assume we could convert that to a more modern definition.

E.g. the reference pixel is about 0.0213 degrees at the intended viewing distance, so the "10 degree viewport at a typical viewing distance" is (10 / 0.0213 = 469) 469px. Hmm, might need to round that off/up.

The technique G176 goes into a lot more detail and should be considered at the same time, care to do a PR?

@awkawk
Copy link
Member

awkawk commented Jan 28, 2019

The resolution defined was because of the typical monitor resolution at the time. How about we change:

The 1024 x 768 screen is used as the reference screen resolution for the evaluation. The 341 x 256 pixel block represents a 10 degree viewport at a typical viewing distance.

to

If a 1024 x 768 screen on a desktop monitor is used as the reference screen resolution for an evaluation then a 341 x 256 pixel block represents a 10 degree viewport at a typical viewing distance.

Would this help?

@alastc
Copy link
Contributor

alastc commented Jan 28, 2019

If it's updated to match CSS pixels, it appears we need to update the value as well, 341x256 is not 10 degrees according to the spec. The commenter in issue #553 came to the same conclusion.

@patrickhlauke
Copy link
Member Author

Just adding here, as an aside: the 1024x768 reference is used by tools like PEAT, and (at least last time I checked) what the tool does is resize your browser to that particular size, to match the reference. This is ok, except in the age of responsive/adaptive web design, where a layout may well change at different breakpoints ... and you'd really want a more abstracted way of testing this at different breakpoints, rather than only relying on testing the 1024x768 breakpoint...

@alastc
Copy link
Contributor

alastc commented Nov 12, 2021

PR added: #2127

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

Successfully merging a pull request may close this issue.

3 participants