E-mail List Archives
Thread: Clarification on Testing Procedure for 1.4.4 Resize Text
Number of posts in this thread: 3 (In chronological order)
From: Ragupathy Ramasamy
Date: Sat, Feb 10 2024 11:19AM
Subject: Clarification on Testing Procedure for 1.4.4 Resize Text
No previous message | Next message →
Dear WebAIM Community,
I am reaching out regarding a clarification on the testing procedure for
text resizing, specifically in relation to success Criterion 1.4.4.
Upon reviewing the provided testing procedure for Failure F94 (
https://www.w3.org/WAI/WCAG21/Techniques/failures/F94) the following
procedure is mentioned.
Procedure:
In a desktop browser with a resizable window:
1. Set zoom level to 100%.
2. Set window size to 1280 pixels wide.
3. Visit the page to be tested.
4. Use any of the following methods to resize text when available:
- the zoom feature of the browser
- the text-sizing feature of the browser,
- on-page controls for resizing text.
5. Check that the text resizes by one of the methods above, and can be
resized to at least 200% of the default.
Now, point number two states that the window size should be 1280 pixels
wide, and the testing technique discusses resizing text using various
methods, including the browser zoom and text-sizing features, as well as
on-page options for resizing text. To ensure accurate testing and
compliance, I am seeking clarification on the following points:
1. Is it acceptable to simply resize the page to 200% zoom using the
browser feature to achieve SC 1.4.4: Resize Text? or
2. Should there be a prior step to adjust the window size to 1280 pixels
wide before zooming the page to 200%, as suggested in the testing procedure?
3. Alternatively, is it advisable to utilize a bookmarklet to conduct the
test resize of text for verification of 1.4.4?
Bookmarklet code:
javascript: (function () {
const htmlElement = document.querySelector('html');
const currentFontSize = htmlElement.style.getPropertyValue('font-size');
const isZoomed = currentFontSize === '200%';
const newFontSize = isZoomed ? null : '200%';
htmlElement.style.setProperty('font-size', newFontSize);
})();
I would greatly appreciate your insights and guidance on the most
appropriate testing methodology.
Thank you for your time and assistance. I look forward to your response.
Best regards,
Ragu (He/Him)
From: Patrick H. Lauke
Date: Sat, Feb 10 2024 4:34PM
Subject: Re: Clarification on Testing Procedure for 1.4.4 Resize Text
← Previous message | Next message →
On 10/02/2024 18:19, Ragupathy Ramasamy wrote:
> Upon reviewing the provided testing procedure for Failure F94 (
> https://www.w3.org/WAI/WCAG21/Techniques/failures/F94) the following
> procedure is mentioned.
Note that techniques are only suggestions, not normative (and often not
quite correct, or antiquated).
> Procedure:
> In a desktop browser with a resizable window:
> 1. Set zoom level to 100%.
> 2. Set window size to 1280 pixels wide.
I've contested this particular point https://github.com/w3c/wcag/issues/704
Because normatively, success criteria apply at any possible size/breakpoint.
So, ideally, you'd need to test at a variety of possible
browser/viewport sizes.
P
--
Patrick H. Lauke
* https://www.splintered.co.uk/
* https://github.com/patrickhlauke
* https://flickr.com/photos/redux/
* https://mastodon.social/@patrick_h_lauke
From: Ragupathy Ramasamy
Date: Wed, Feb 14 2024 11:19PM
Subject: Re: Clarification on Testing Procedure for 1.4.4 Resize Text (Patrick H. Lauke)
← Previous message | No next message
Hi Patrick,
Thank you so much for your reply and sharing the github issue link with me
for the reference.
Is it fine or acceptable to use the bookmarklet to test resize text in
chrome browser?
Thank you,
Ragu
On Mon, 12 Feb, 2024, 12:30 am , < = EMAIL ADDRESS REMOVED = >
wrote:
> Send WebAIM-Forum mailing list submissions to
> = EMAIL ADDRESS REMOVED =
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://list.webaim.org/cgi-bin/mailman/listinfo/webaim-forum
> or, via email, send a message with subject or body 'help' to
> = EMAIL ADDRESS REMOVED =
>
> You can reach the person managing the list at
> = EMAIL ADDRESS REMOVED =
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
> Today's Topics:
>
> 1. Re: Clarification on Testing Procedure for 1.4.4 Resize Text
> (Patrick H. Lauke)
> 2. Re: JAWS keyboard command for Page Labels in PDFs (Ben Moxey)
> 3. Foxit PDF Editor keyboard command for going to a page
> (Windows) (Karen McCall)
>
>
>
> ---------- Forwarded message ----------
> From: "Patrick H. Lauke" < = EMAIL ADDRESS REMOVED = >
> To: = EMAIL ADDRESS REMOVED =
> Cc:
> Bcc:
> Date: Sat, 10 Feb 2024 23:34:49 +0000
> Subject: Re: [WebAIM] Clarification on Testing Procedure for 1.4.4 Resize
> Text
>
>
> On 10/02/2024 18:19, Ragupathy Ramasamy wrote:
>
> > Upon reviewing the provided testing procedure for Failure F94 (
> > https://www.w3.org/WAI/WCAG21/Techniques/failures/F94) the following
> > procedure is mentioned.
>
> Note that techniques are only suggestions, not normative (and often not
> quite correct, or antiquated).
>
> > Procedure:
> > In a desktop browser with a resizable window:
> > 1. Set zoom level to 100%.
> > 2. Set window size to 1280 pixels wide.
>
> I've contested this particular point
> https://github.com/w3c/wcag/issues/704
>
> Because normatively, success criteria apply at any possible
> size/breakpoint.
>
> So, ideally, you'd need to test at a variety of possible
> browser/viewport sizes.
>
> P
> --
> Patrick H. Lauke
>
> * https://www.splintered.co.uk/
> * https://github.com/patrickhlauke
> * https://flickr.com/photos/redux/
> * https://mastodon.social/@patrick_h_lauke
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Ben Moxey < = EMAIL ADDRESS REMOVED = >
> To: Duff Johnson < = EMAIL ADDRESS REMOVED = >, WebAIM Discussion List <
> = EMAIL ADDRESS REMOVED = >
> Cc: ATHEN < = EMAIL ADDRESS REMOVED = >
> Bcc:
> Date: Sun, 11 Feb 2024 02:33:22 +0000
> Subject: Re: [WebAIM] JAWS keyboard command for Page Labels in PDFs
> Hi Karen
>
> The JAWS command, Insert + Page Down, and the NVDA command, Insert + End,
> are simply dedicated commands to announce what's in the status bar. It must
> be related to a change in the Adobe user interface.
>
> I'm be interested to know if the status bar still displays these details
> visually.
>
> Cheers
>
> Ben
>
>
> âBen Moxey
> Access and Technology Advisor
> P 1800 436 364
>
> |
>
> T
> +61 2 4063 3019
>
>
> Suite 2, 265 Wharf Road, Newcastle NSW 2300
> |
>
>
>
>
> â
> We acknowledge Aboriginal and Torres Strait Islander Peoples as the First
> Peoples and the Traditional Owners and Custodians of the lands and
> ââwaters on which we live and work. We pay our respects to their Elders,
> Knowledge Holders and Leaders, past, present and emerging and extend
> ââthat respect to all Aboriginal and Torres Strait Islander Peoples.
> â
> This e-mail is for the use of the intended recipient(s) only. If you have
> received this e-mail in error, please notify the sender immediately and then
> delete it. If you are not the intended recipient, you must not use,
> disclose or distribute this e-mail without the author's permission. We have
> taken
> precautions to minimise the risk of transmitting software viruses, but we
> advise you to carry out your own virus checks on any attachment to this
> e-mail. We cannot accept liability for any loss or damage caused by
> software viruses.
>
> Guide Dogs Privacy Policy
>
>