From 4bdc10e63b8ce00e85cea9b2b34df509a8215975 Mon Sep 17 00:00:00 2001 From: anticultist <33195947+anticultist@users.noreply.github.com> Date: Tue, 22 Oct 2024 08:31:23 +0200 Subject: [PATCH] update link for WebAims Screen Reader User Survey --- doc/accessibility-supported.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/accessibility-supported.md b/doc/accessibility-supported.md index 4e334f6c5e..6585bd0a9a 100644 --- a/doc/accessibility-supported.md +++ b/doc/accessibility-supported.md @@ -6,7 +6,7 @@ In order to adhere to the manifesto and at the same time be useful to developers Accessibility supported means that in order for a technique to pass, it must work in some predefined set of browsers and assistive technologies. For axe-core this means that for a screen reader, browser, or environment to be added to the list of supported combinations, the following two criteria must be met: -1. Be used by more than 1% of users (currently extrapolated from the [WebAims Screen Reader User Survey](https://webaim.org/projects/screenreadersurvey8/#browsercombos)) +1. Be used by more than 1% of users (currently extrapolated from the [WebAims Screen Reader User Survey](https://webaim.org/projects/screenreadersurvey10/#browsercombos)) 1. Introduce new coverage for a screen reader, browser, or environment not currently accessibility supported We currently test the following AT combinations for support