From af737c05d2c16ade4e55abde4aa3d878f0ff3e62 Mon Sep 17 00:00:00 2001 From: Thibaud Colas Date: Mon, 15 Jan 2024 07:10:18 +0000 Subject: [PATCH] Address feedback about specifics of when more testing is needed --- .../contributing/writing-code/accessibility.txt | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/docs/internals/contributing/writing-code/accessibility.txt b/docs/internals/contributing/writing-code/accessibility.txt index 8a0667b607..942c89d370 100644 --- a/docs/internals/contributing/writing-code/accessibility.txt +++ b/docs/internals/contributing/writing-code/accessibility.txt @@ -63,7 +63,7 @@ Always test user interface changes with: * The `Accessibility Insights`_ browser extension's automated checks feature, or an equivalent tool with the `Axe`_ checker. -Where the UI changes, also test with: +Where the UI changes could affect those modalities, also test with: * Touch-only navigation * 400% browser zoom @@ -74,8 +74,8 @@ Where the UI changes, also test with: Assistive technologies ---------------------- -Where more extensive testing is appropriate, here are popular free assistive -technologies we recommend testing with: +Where the UI changes could affect assistive technologies, here are popular +free options we recommend testing with: * `NVDA`_ on Windows with Firefox ESR * `VoiceOver`_ on macOS with Safari @@ -86,7 +86,8 @@ technologies we recommend testing with: * VoiceOver on iOS, or TalkBack on Android * `Contrast themes`_ on Windows -Where expert help is available, also consider testing with: +If you have the expertise or you can work with someone who does, also test +with: * `JAWS`_ on Windows * `Dragon`_ on Windows