From e4384f07d076e310358b1ad496fe0920deb368b5 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Tue, 1 Jun 2021 17:15:53 +0100 Subject: [PATCH 1/4] Remove initial window/browser size from F94 test it's irrelevant, as the SC applies at any size, so doesn't need to appear to be limited to any particular one. This addresses initial concern of https://github.com/w3c/wcag/issues/704 (but that issue has more discussion about the potential need for a normative change for 1.4.4, or addition of note(s) in the understanding, to set some lower bound) --- techniques/failures/F94.html | 1 - 1 file changed, 1 deletion(-) diff --git a/techniques/failures/F94.html b/techniques/failures/F94.html index edd20c9d1c..27ec17aba7 100644 --- a/techniques/failures/F94.html +++ b/techniques/failures/F94.html @@ -45,7 +45,6 @@

Procedure

In a desktop browser with a resizable window:

  1. Set zoom level to 100%.
  2. -
  3. Set window size to 1280 pixels wide.
  4. Visit the page to be tested.
  5. Use any of the following methods to resize text when available:
      From 1868240da6d991ad3a0a6e7b452c48961d46b155 Mon Sep 17 00:00:00 2001 From: "Patrick H. Lauke" Date: Mon, 22 Aug 2022 21:04:17 +0100 Subject: [PATCH 2/4] Add note about needing to re-run procedure for each variation --- techniques/failures/F94.html | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/techniques/failures/F94.html b/techniques/failures/F94.html index 81b9d1d1e1..d80f0d96ab 100644 --- a/techniques/failures/F94.html +++ b/techniques/failures/F94.html @@ -45,16 +45,19 @@

      Procedure

      In a desktop browser with a resizable window:

      1. Set zoom level to 100%.
      2. -
      3. Visit the page to be tested.
      4. -
      5. Use any of the following methods to resize text when available: +
      6. Visit the page to be tested.
      7. +
      8. 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.
      9. -
      10. Check that the text resizes by one of the methods above, and can be resized to at least 200% of the default.
      11. +
      12. Check that the text resizes by one of the methods above, and can be resized to at least 200% of the default.
      +
      +

      If the page has variations that are automatically presented for various screen sizes (e.g. media query breakpoints), you should run the test procedure for each variation.

      +

      Expected Results

      From 30a3d6b5fa8e56a711c7055ddb857ce70c912627 Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 6 Dec 2023 14:44:08 -0800 Subject: [PATCH 3/4] Update techniques/failures/F94.html --- techniques/failures/F94.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F94.html b/techniques/failures/F94.html index d80f0d96ab..93ef9019b5 100644 --- a/techniques/failures/F94.html +++ b/techniques/failures/F94.html @@ -48,7 +48,7 @@

      Procedure

    • Visit the page to be tested.
    • Use any of the following methods to resize text when available:
        -
      • the zoom feature of the browser
      • +
      • the zoom feature of the browser,
      • the text-sizing feature of the browser,
      • on-page controls for resizing text.
      From 1b4634a47949c6eb6b9b071d7355c3cfce95024b Mon Sep 17 00:00:00 2001 From: Mike Gower Date: Wed, 6 Dec 2023 14:44:59 -0800 Subject: [PATCH 4/4] Update techniques/failures/F94.html --- techniques/failures/F94.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/techniques/failures/F94.html b/techniques/failures/F94.html index 93ef9019b5..0e8f9b9edd 100644 --- a/techniques/failures/F94.html +++ b/techniques/failures/F94.html @@ -56,7 +56,7 @@

      Procedure

    • Check that the text resizes by one of the methods above, and can be resized to at least 200% of the default.
-

If the page has variations that are automatically presented for various screen sizes (e.g. media query breakpoints), you should run the test procedure for each variation.

+

If the page has variations that are automatically presented for various screen sizes (for instance, media query breakpoints), you should run the test procedure for each variation.