Skip to content

402 how to test browser zoom jtrapp - #450

Open
jtweb23 wants to merge 15 commits into
mainfrom
402-how-to-test_browser-zoom_jtrapp
Open

402 how to test browser zoom jtrapp#450
jtweb23 wants to merge 15 commits into
mainfrom
402-how-to-test_browser-zoom_jtrapp

Conversation

@jtweb23

@jtweb23 jtweb23 commented May 1, 2026

Copy link
Copy Markdown
Collaborator

Rough draft of "How to Test" text content for Browser Zoom and Magnification. Please share feedback on the content outline and details. Once on track for the content, I can add in relevant screen shot examples and/or video.

jtweb23 added 5 commits April 30, 2026 19:10
Create "How to Test" page for Browser Zoom and desktop Magnification for Mac and Windows.
@jtweb23
jtweb23 requested review from joe-watkins and marshcooke May 1, 2026 01:01
✓ Ensure text content remains legible when scaled to 200 percent browser zoom
Note: This requirement is only for Web page text such as headings, body text, link text, button text labels, form field labels, and text inside form inputs, etc. (and excludes captions and images of text).

Pass Fail

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Pass/Fail section, are we aiming for this to have a similar table structure as other Pass/Fail examples on other How to Test sections? Or is there a easier way to display this information to clearly communicate what is considered passing or failing?

@marshcooke marshcooke left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few heading level updates left in two comments and another comment noting that the Pass/Fail display isn't done in the similar table style as other How to Test pages - but that doesn't mean it can't be different, more that we can more clearly inform users what is considered passing or failing.

Otherwise, great work @jtweb23!

Heading hierarchy updates.
@jtweb23

jtweb23 commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator Author

Thanks @marshcooke for the helpful feedback. I making the heading level updates today, and then will move into integrating screen shot examples. Thanks!

@silverli
silverli removed the request for review from joe-watkins June 4, 2026 14:57
jtweb23 added 2 commits June 8, 2026 14:05
Windows and Mac desktop keyboard shortcut table formatting.
jz-tmus
jz-tmus previously approved these changes Jun 8, 2026

@jz-tmus jz-tmus left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks great, thanks for updating Jule!

@marshcooke marshcooke left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure the "3. What to test for" list item is within the same list as the "1. General Requirements" and "2. How to test" and it should be good to go!

Remove extra space on a line.
Move "What to test for" inside <ol> ordered list.

3. ## What to test for

- Ensure text content remains legible when scaled to 200 percent browser zoom

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This list is not loading as a list in the DOM. It will likely come down to how you're formatting it in the markdown file - as currently it is all in blue text where list that are formatted correctly show the dash as yellow and the text as white (see above under "Reflow at 400 percent browser zoom".

This fix and another spacing issue on line 65 should resolve remaining concerns and be ready to merge on the next commit/review!! Great work, Jules!

@marshcooke marshcooke left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix formatting of list starting on Line 64, remove extra spacing on Line 65, and then we should be good to go! 🥳

jtweb23 added 3 commits June 18, 2026 17:30
Example table with CSS formatting
Pass/Fail table format 1 of 2.
Pass/Fail table format 2 of 2.
marshcooke
marshcooke previously approved these changes Jun 26, 2026

@marshcooke marshcooke left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me, I like the placeholders plan!

@joe-watkins

Copy link
Copy Markdown
Collaborator

@jtweb23 We will need to include direction on setting the viewport to 1280px for 400% testing on desktop to reach the equivalent of a 320px viewport - which the SC requires [and only that size does the SC require]. https://www.w3.org/WAI/WCAG22/Understanding/reflow.html#techniques

We can borrow from the test steps found in WCAG for how to test:

  • Display the web page in a user agent capable of 400% zoom and set the viewport dimensions (in CSS pixels) to 1280 wide and 1024 high.
  • Zoom in by 400%.
  • For content read horizontally, check that all content and functionality is available without horizontal scrolling.
  • For content read vertically, check that all content and functionality is available without vertical scrolling.

Reflow for mobile 320px 400% zoom equivalent.
@jtweb23

jtweb23 commented Jul 7, 2026

Copy link
Copy Markdown
Collaborator Author

Thank you @joe-watkins, I have added the suggested test steps for 320px width/1280px width at 400% zoom.

Remove What to Test For "screen shot placeholder" text.

@marshcooke marshcooke left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fantastic, just needs screenshots added! Awesome table work, Jules!

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants