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

2.4.11 and 2.5.8 - Recommended viewport size for testing? #1829

Closed
LiLoDavis opened this issue May 26, 2021 · 6 comments
Closed

2.4.11 and 2.5.8 - Recommended viewport size for testing? #1829

LiLoDavis opened this issue May 26, 2021 · 6 comments

Comments

@LiLoDavis
Copy link

LiLoDavis commented May 26, 2021

Conformance with 2.4.11 Focus Appearance (Minimum) and 2.5.8 Target Size (Minimum) can depend on an element's height and width. Given that elements' dimensions can vary with changes in the viewport size and/or zoom setting, can you recommend a viewport size and zoom setting for testing these SC?

@jake-abma
Copy link
Contributor

Hey @LiLoDavis not viewport sizes need to be tested, but all variations of a "full page" (they may be triggered by viewport changes though...)

See also: https://www.w3.org/TR/WCAG21/#cc2

NOTE
A full page includes each variation of the page that is automatically presented by the page for various screen sizes (e.g. variations in a responsive Web page). Each of these variations needs to conform (or needs to have a conforming alternate version) in order for the entire page to conform.

@alastc
Copy link
Contributor

alastc commented May 27, 2021

can you recommend a viewport size and zoom setting for testing these SC?

For focus appearance, if you have sticky / layered content, I would test at each page variation (e.g. media query kicking in). It would apply to the 'obscured' bullet, and if you had shapes (rather than outlines or backgrounds) it might apply to the sizing for things which change shape at different viewport sizes.

For target size, as it's measured in CSS pixels it would only really be if the size or spacing of links deliberately changed that you'd need to test.

So overall, there isn't really a recommended size to test at, as Jake mentioned you need to test different page variations. What I'd recommend is examining when the elements on the page are changing, and therefore might need testing.

@LiLoDavis
Copy link
Author

Thank you, @jake-abma and @alastc.
I was evaluating a page for target size when I realized that some text fields changed width automatically (to fit the space available) as I adjusted the width of the page. If I understand the SC correctly, as target sizes decrease below 24px, the target offset needs to increase in order to conform.

@alastc
Copy link
Contributor

alastc commented May 27, 2021

If a text-input gets smaller than 24px wide, you wouldn't fit more than a letter or two in it?!

@alastc alastc added this to To do in WCAG 2.2 via automation Oct 22, 2021
@alastc
Copy link
Contributor

alastc commented Nov 30, 2021

Approved response:


The intent of the SC is that conformance is met across page variations. The new focus-appearance and target-size SCs do not create specific scenarios where a particular viewport size is required.

If the pages are being tested down to 320px wide (for reflow), that would be a useful minimum size for testing the smallest page-variant. Targets / focus indicators should pass across other page-variants as well (e.g. break points).

@alastc alastc moved this from To do to To Survey in WCAG 2.2 Dec 3, 2021
@alastc
Copy link
Contributor

alastc commented Feb 3, 2022

The response above was approved: https://www.w3.org/2022/02/01-ag-minutes#item07

@alastc alastc closed this as completed Feb 3, 2022
WCAG 2.2 automation moved this from To Survey to Done Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
WCAG 2.2
  
Done
Development

No branches or pull requests

3 participants