diff --git a/src/assets/json/checklist/tests-web-en.json b/src/assets/json/checklist/tests-web-en.json index 558d8fb09..49b957a2d 100644 --- a/src/assets/json/checklist/tests-web-en.json +++ b/src/assets/json/checklist/tests-web-en.json @@ -199,7 +199,7 @@ "title": "Provide accessible flashes", "type": ["Manual test"], "tests": ["Inspect the animation and video contents of the page that flashes"], - "verifier": ["Make sure that any content does not show rapid flashes (more than 3 flashes per second) or the flashes are below the general flash and red flash thresholds."], + "verifier": ["Make sure that any content does not show rapid flashes (more than 3 flashes per second) or the flashes are below the general flash and red flash thresholds."], "resultat": ["No rapid flash or beyond the general flash and red flash thresholds."], "exception": "", "raccourcis": "", @@ -813,7 +813,7 @@ "title": "Make sure the autocomplete attribute is present to avoid entry errors", "type": ["Manual test"], "tests": ["Manual test", "Browse the forms", "Fill in the forms with specific information about the user"], - "verifier": ["For any field that collects specific information about the user ( exhaustive list ), the autocomplete attribute of the field must be present and have an appropriate value "], + "verifier": ["For any field that collects specific information about the user ( exhaustive list ), the autocomplete attribute of the field must be present and have an appropriate value "], "resultat": ["The autocomplete attribute is:", "present", "and the value of this attribute is relevant"], "exception": [], "raccourcis": "", diff --git a/src/assets/json/checklist/tests-web-fr.json b/src/assets/json/checklist/tests-web-fr.json index 39f3fbb12..6ccdba280 100644 --- a/src/assets/json/checklist/tests-web-fr.json +++ b/src/assets/json/checklist/tests-web-fr.json @@ -199,7 +199,7 @@ "title": "Rendre accessible les clignotements", "type": ["Test manuel"], "tests": ["Examiner les contenus de type animations et vidéos de la page qui clignotent"], - "verifier": ["Vérifier qu'il n'y a pas de contenu présentant des clignotements rapides (plus de 3 flash à la seconde) ou les flashs sont inférieurs au seuil général ou seuil de rouge."], + "verifier": ["Vérifier qu'il n'y a pas de contenu présentant des clignotements rapides (plus de 3 flash à la seconde) ou les flashs sont inférieurs au seuil général ou seuil de rouge."], "resultat": ["Absence de clignotement ou de flash rapide ou dépassant le seuil général ou de rouge"], "exception": "", "raccourcis": "", @@ -813,7 +813,7 @@ "title": "S'assurer que l'attribut autocomplete est mis en place afin d'éviter les erreurs de saisie", "type": ["Test manuel"], "tests": ["Test manuel", "Parcourir les formulaires", "Renseigner les formulaires avec des informations spécifiques sur l'utilisateur"], - "verifier": ["Pour tout champ qui permet de collecter des informations spécifiques sur l'utilisateur (liste exhaustive), l'attribut autocomplete du champ doit être présent et avoir une valeur adéquate"], + "verifier": ["Pour tout champ qui permet de collecter des informations spécifiques sur l'utilisateur (liste exhaustive), l'attribut autocomplete du champ doit être présent et avoir une valeur adéquate"], "resultat": ["L'attribut autocomplete est présent", "et la valeur de cet attribut est pertinente"], "exception": [], "raccourcis": "", diff --git a/src/en/accessibility.njk b/src/en/accessibility.njk index d5bf3f8d1..31a3eba04 100644 --- a/src/en/accessibility.njk +++ b/src/en/accessibility.njk @@ -30,7 +30,7 @@ css:

Standard applied

- WCAG version 2.1, level AA. + WCAG version 2.2, level AA.

diff --git a/src/en/articles/aria-status-messages.md b/src/en/articles/aria-status-messages.md index 033c86741..c23f66e93 100644 --- a/src/en/articles/aria-status-messages.md +++ b/src/en/articles/aria-status-messages.md @@ -9,7 +9,7 @@ tags: --- ## Status message and accessibility -The WCAG 2.1 criterion 4.1.3 Status Messages requires that important informations for the user, which do not induce a change of context (no opening of a new window, no focus on the content, no modification of the content or the viewport), are seen via properties and roles (ARIA) by anyone using AT without taking focus on the message. +The WCAG 2.1 criterion 4.1.3 Status Messages requires that important informations for the user, which do not induce a change of context (no opening of a new window, no focus on the content, no modification of the content or the viewport), are seen via properties and roles (ARIA) by anyone using AT without taking focus on the message. ## Some examples of status messages diff --git a/src/en/articles/font-size-and-colors.md b/src/en/articles/font-size-and-colors.md index ea26ae472..806c3a577 100644 --- a/src/en/articles/font-size-and-colors.md +++ b/src/en/articles/font-size-and-colors.md @@ -16,19 +16,19 @@ In this article, we will try to answer the following questions concerning the ac ## What do the guidelines say ? The [WCAG](https://www.w3.org/WAI/standards-guidelines/wcag/) do not impose a minimum size or colors for texts. However two criteria must be taken into consideration: -- 1.4.4 Resize text -- 1.4.3 Contrast (Minimum) +- 1.4.4 Resize text +- 1.4.3 Contrast (Minimum) ### Text size enlargement -If the guidelines do not impose a minimum size for characters, [criterion 1.4.4](https://www.w3.org/TR/WCAG21/#resize-text) indicates that the user must be able to increase text size up to 200% without loss of content or functionality. To comply with this criterion, it is essential to test. The procedure to increase text size is available on the following page: [Text size enlargement](https://a11y-guidelines.orange.com/en/web/toolbox/methods-and-test-tools/text-zoom/). +If the guidelines do not impose a minimum size for characters, [criterion 1.4.4](https://www.w3.org/TR/WCAG22/#resize-text) indicates that the user must be able to increase text size up to 200% without loss of content or functionality. To comply with this criterion, it is essential to test. The procedure to increase text size is available on the following page: [Text size enlargement](https://a11y-guidelines.orange.com/en/web/toolbox/methods-and-test-tools/text-zoom/). Sometimes the sizing of certain blocks of text, in particular using sizes in pixels, can lead to loss of information (truncated texts), it is therefore advisable to use relative units (%, em, rem ...). ### Color contrast The guidelines do not require the use or even prohibit the use of certain colors for texts. However, a light gray text on a white background, for example, could be difficult. It is therefore essential to check that the text color and the background color provide a sufficient level of contrast (see levels below). This can be done easily with help [of tools](https://a11y-guidelines.orange.com/en/web/toolbox/methods-and-test-tools/color-contrast-level/). -[Criterion 1.4.3 of the standard](https://www.w3.org/TR/WCAG21/#contrast-minimum) details the required contrast levels. +[Criterion 1.4.3 of the standard](https://www.w3.org/TR/WCAG22/#contrast-minimum) details the required contrast levels. For standard texts (not bold): - size less than 24px: contrast of 4.5:1 minimum diff --git a/src/en/articles/form/part2/index.md b/src/en/articles/form/part2/index.md index c331c6444..6b52f5bea 100644 --- a/src/en/articles/form/part2/index.md +++ b/src/en/articles/form/part2/index.md @@ -264,7 +264,7 @@ In the example above: ### Using the autocomplete attribute -The autocomplete attribute makes it easier to fill in fields that contain personal information. All fields whose type is listed in 7. InputPurposes for User Interface Components must contain the autocomplete attribute. +The autocomplete attribute makes it easier to fill in fields that contain personal information. All fields whose type is listed in 7. InputPurposes for User Interface Components must contain the autocomplete attribute. In our example the fields below should have an autocomplete attribute: