Language improvements and spelling mistakes fixes

_doc/about-people-with-disabilities.md

@@ -5,7 +5,7 @@ nav: menu-about-users
 
 # About people with disabilities
 
-A problem in accessibility is the result of an interaction between an user and the content (or functionality) that he or she tried to access, use, perceive or understand but couldn't because of a disability.
+A problem in accessibility is the result of an interaction between a user and the content (or functionality) that he or she tried to access, use, perceive or understand but couldn't because of a disability.
 
 Looking beyond people's disability, everyone is different and it would be meaningless to describe all the accessibility problems resulting from the content and functionalities of a site or web application lacking adaptability.
 

_doc/accessibility/colors/information-by-color.md

@@ -53,7 +53,7 @@ The ways of transmitting information other than by colour can be:
 
 <div class="important">
 <svg role="img" aria-label="Important" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 576 512" width="40" height="36"><title>Important</title><path d="M569.517 440.013C587.975 472.007 564.806 512 527.94 512H48.054c-36.937 0-59.999-40.055-41.577-71.987L246.423 23.985c18.467-32.009 64.72-31.951 83.154 0l239.94 416.028zM288 354c-25.405 0-46 20.595-46 46s20.595 46 46 46 46-20.595 46-46-20.595-46-46-46zm-43.673-165.346l7.418 136c.347 6.364 5.609 11.346 11.982 11.346h48.546c6.373 0 11.635-4.982 11.982-11.346l7.418-136c.375-6.874-5.098-12.654-11.982-12.654h-63.383c-6.884 0-12.356 5.78-11.981 12.654z"/></svg>
-When using `aria-current`, make sure that the information is not given by color and `aria-current` only. Visually impaired people who cannot perceive color may not necessarily use a assistive technology capable of interpreting `aria-current`. In this case it is necessary to add shape, size or position to the element.
+When using `aria-current`, make sure that the information is not given by color and `aria-current` only. People with visual impairment who cannot perceive color may not necessarily use a assistive technology capable of interpreting `aria-current`. In this case it is necessary to add shape, size or position to the element.
 </div>
 
 ### Examples

_doc/accessibility/consultation/files-for-downloading.md

@@ -19,7 +19,7 @@ description: Accessibility of office documents
 
 ## Explanation
 
-Blind and severely visually impaired people will have great difficulty if the documents to be downloaded are not accessible or if they do not have an accessible alternative.
+People who are blind or severely visually impaired will have great difficulty if the documents to be downloaded are not accessible or if they do not have an accessible alternative.
 
 ### Make downloadable documents accessible or propose an accessible alternative
 If possible, it is necessary to make a document accessible for download. If the software used to create the document is not compatible with accessibility, it is necessary to provide an accessible equivalent in another format (.doc,.odt... or a web page).

_doc/accessibility/consultation/moving-or-blinking-content.md

@@ -12,7 +12,7 @@ description: Accessibility of moving or flashing content
 
 **Impact:** Strong to major
 
-**Users mainly impacted:** Blind, visually impaired, physically handicapped, mentally handicapped.
+**Users mainly impacted:** Blind, visually impaired, physically impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 13.8](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-13-8)
 {: .criteria }

_doc/accessibility/consultation/no-new-window-without-user-action.md

@@ -12,7 +12,7 @@ description: Accessibility of links opening new windows
 
 **Impact:** Moderate to strong
 
-**Users mainly impacted:** Blind, visually impaired, physically impaired, mentally handicapped.
+**Users mainly impacted:** Blind, visually impaired, physically impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 13.2](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-13-2)
 {: .criteria }

_doc/accessibility/forms/complex-selection-list.md

@@ -12,14 +12,14 @@ description: Accessibility of complex selection list
 
 **Impact:** Strong to major
 
-**Users mainly impacted:** blind, severely visually impaired, visually impaired, mentally handicapped.
+**Users mainly impacted:** blind, severely visually impaired, visually impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 11.8](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-8)
 {: .criteria }
 
 ## Explanation
 
-Blind and severely visually impaired, visually impaired and mentally handicapped persons may encounter difficulties if selection lists that are complex or contain many items are not structured by groupings.
+People with visual and mental impairment may encounter difficulties if selection lists that are complex or contain many items are not structured by groupings.
 
 If the list offers a limited choice, the options should be presented in a logical order.
 

_doc/accessibility/forms/group-related-fields.md

@@ -12,7 +12,7 @@ description: Accessibility of group of fields
 
 **Impact:** Strong to major
 
-**Users mainly impacted:** Blind, visually impaired, mentally handicapped.
+**Users mainly impacted:** Blind, visually impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 11.5](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-5) - [Criterion 11.6](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-6) - [Criterion 11.7](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-7)
 {: .criteria }

_doc/accessibility/forms/input-errors.md

@@ -12,7 +12,7 @@ description: Accessibility of wrong fields
 
 **Impact:** Strong to major
 
-**Users mainly impacted:** Blind, severely visually impaired, visually impaired, mentally handicapped.
+**Users mainly impacted:** Blind, severely visually impaired, visually impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 11.10](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-10) - [Criterion 11.11](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-11)
 {: .criteria }

_doc/accessibility/forms/input-help.md

@@ -12,7 +12,7 @@ description: Help users complete a field that requires specific data formats
 
 **Impact:** Strong to major
 
-**Users mainly impacted:** Blind, severely visually impaired, visually impaired, mentally handicapped.
+**Users mainly impacted:** Blind, severely visually impaired, visually impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 11.10](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-10) - [Criterion 11.11](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-11)
 {: .criteria }

_doc/accessibility/forms/relevance-of-field-labels.md

@@ -12,7 +12,7 @@ description: Label allows to identify the controls in a form
 
 **Impact:** Strong to major
 
-**Users mainly impacted:** Blind, visually impaired, physically impaired, mentally handicapped.
+**Users mainly impacted:** Blind, visually impaired, physically impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 11.1](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-1) - [Criterion 11.2](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-2)
 {: .criteria }

_doc/accessibility/forms/relevant-button.md

@@ -12,7 +12,7 @@ description: Accessibility of the buttons
 
 **Impact:** Strong to major
 
-**Users mainly impacted:** Blind, visually impaired, physically impaired, mentally handicapped.
+**Users mainly impacted:** Blind, visually impaired, physically impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 11.9](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-9)
 {: .criteria }

_doc/accessibility/forms/required-fields.md

@@ -12,7 +12,7 @@ description: Accessibility of the required fields
 
 **Impact:** Strong to major
 
-**Users mainly impacted:** Blind, severely visually impaired, visually impaired, mentally handicapped.
+**Users mainly impacted:** Blind, severely visually impaired, visually impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 11.10](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-11-10)
 {: .criteria }
@@ -36,7 +36,7 @@ It is not always necessary to make fields required. When a form has only one fie
 
 ### Text indication in the label
 
-The most robust solution. Indicate by an explicit term the required nature of the field directly in the label (`label`, `title`, `aria-label`...).
+The most robust solution: indicate by an explicit term the required nature of the field directly in the label (`label`, `title`, `aria-label`...).
 
 ```html
 <label for="name">Name<em aria-hidden="true"> (required)</em></name>
@@ -45,15 +45,15 @@ The most robust solution. Indicate by an explicit term the required nature of th
 
 <div class="tip">
 <svg role="img" aria-label="Tip" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 352 512" width="28" height="40"><title>Tip</title><path d="M96.06 454.35c.01 6.29 1.87 12.45 5.36 17.69l17.09 25.69a31.99 31.99 0 0 0 26.64 14.28h61.71a31.99 31.99 0 0 0 26.64-14.28l17.09-25.69a31.989 31.989 0 0 0 5.36-17.69l.04-38.35H96.01l.05 38.35zM0 176c0 44.37 16.45 84.85 43.56 115.78 16.52 18.85 42.36 58.23 52.21 91.45.04.26.07.52.11.78h160.24c.04-.26.07-.51.11-.78 9.85-33.22 35.69-72.6 52.21-91.45C335.55 260.85 352 220.37 352 176 352 78.61 272.91-.3 175.45 0 73.44.31 0 82.97 0 176zm176-80c-44.11 0-80 35.89-80 80 0 8.84-7.16 16-16 16s-16-7.16-16-16c0-61.76 50.24-112 112-112 8.84 0 16 7.16 16 16s-7.16 16-16 16z"/></svg>
-You will notice the addition of the attribute `aria-hidden="true"` which allows you not to vocalize the information in order not to create redundancy of information in case the field has an attribute `required` or `aria-required`.
+You will notice the addition of the attribute `aria-hidden="true"` which allows you not to vocalize the information. This will avoid redundancy of information in case the field has an attribute `required` or `aria-required`.
 </div>
 
 ### Indication by a symbol
 
 It is very common to find the required field indication by means of an asterisk. This practice is completely consistent if you give a caption to this symbol before the form concerned.
 
 ```html
-<p aria-hidden="true">Fields preceded by an asterisk (*) are required</p>
+<p aria-hidden="true">Fields marked with an asterisk (*) are required</p>
 <form>
     <label for="name">Name<em aria-hidden="true"> *</em></label>
     <input type="text" name="name" id="name" required>

_doc/accessibility/images.md

@@ -16,7 +16,7 @@ There are two types of images:
 
 Sometimes, images convey non-text information. This information, which can help to understand the content to which it relates, must be accessible for all.
 
-Providing an alternative is essential for users who do not perceive visual content. This is the case for blind or partially sighted people. A screen reader will be able to access this alternative and will return it to the user.
+Providing an alternative is essential for users who do not perceive visual content. This is the case for people who are blind or partially sighted. A screen reader will be able to access this alternative and will return it to the user.
 
 Similarly, for people who have difficulty understanding certain visual representations (iconography, paintings, multi-dimensional representations, graphics, etc.), an alternative can help to understand their meaning or extract important information.
 

_doc/accessibility/information-structure/quotation.md

@@ -12,18 +12,18 @@ description: Accessibility of quotes
 
 **Impact:** Low to high
 
-**Users mainly impacted:** Blind, severely visually impaired, mentally handicapped.
+**Users mainly impacted:** Blind, severely visually impaired, mentally impaired.
 
 **RGAA criteria:** [Criterion 9.4](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-9-4)
 {: .criteria }
 
 ## Explanation
 
-Failure to report quotations can make the content more complex for blind and severely visually impaired people to understand and generate ambiguities and misunderstandings.
+Not flagging quotations can make the content more complex for people who are blind or severely visually impaired to understand and generate ambiguities and misunderstandings.
 
 Correctly marking a quote allows users who are visually impaired, blind or have difficulty reading and who use a screen reader to understand that it is a quote and to find precisely the beginning and end of the quote, without having to search through all the characters for opening and closing quotation marks.
 
 There are two types of quotations:
 
-* short quotations, called online quotations;
-* long quotations, called block quotations.
+* short quotations, called inline quotes;
+* long quotations, called block quotes.

_doc/accessibility/information-structure/semantic-structure-and-aria-landmarks.md

@@ -12,7 +12,7 @@ description: Accessibility and semantic structures
 
 **Impact:** Moderate to high
 
-**Users mainly impacted:** Blind, severely visually impaired, motor handicapped.
+**Users mainly impacted:** Blind, severely visually impaired, motor impaired.
 
 **RGAA criteria:** [Criterion 9.2](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-9-2) - [Criterion 12.6](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-12-6)
 {: .criteria }
@@ -21,9 +21,9 @@ description: Accessibility and semantic structures
 
 Screen readers or some browser plug-ins provide quick navigation based on the structural elements of the HTML5 document.
 
-In their absence, blind and severely visually impaired people may have difficulty identifying large areas of the document or moving quickly through the page, for example on navigation elements.
+In their absence, people who are blind or severely visually impaired may have difficulty identifying large areas of the document or moving quickly through the page, for example on navigation elements.
 
-The motor handicapped will see the fast access functionalities to the large areas of the document as inoperative.
+People with motor disabilities will see the fast access functionalities to the large areas of the document as inoperative.
 
 ### HTML5 elements and ARIA landmarks
 
@@ -33,7 +33,7 @@ The large areas that allow to structure a web page are:
 * the main content;
 * the footer (legal information, etc.) ;
 * the search engine;
-* the main navigation and any secondary navigation.
+* the main navigation and any secondary navigations.
 
 Each of these zones has a specific ARIA property that will allow them to be identified with certainty. These properties are implemented with the `role` attribute:
 

_doc/accessibility/information-structure/structure-information-by-headings.md

@@ -12,7 +12,7 @@ description: Content hierarchized by relevant headings
 
 **Impact:** Moderate to high
 
-**Users mainly impacted:** Blind, severely visually impaired, motor handicapped, cognitive disability.
+**Users mainly impacted:** Blind, severely visually impaired, motor disability, cognitive disability.
 
 **RGAA criteria:** [Criterion 9.1](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-9-1)
 {: .criteria }
@@ -69,7 +69,7 @@ The following example is non-compliant.
 </ul>
 
 #### Inappropriate order
-The hierarchy of the content must be respected through the headings. This example is non-compliant. Radish is a child of vegetables, he can't be higher than vegetables.
+The hierarchy of the content must be respected through the headings. This example is non-compliant. Radish is a child of vegetables, it can't be higher than vegetables.
 
 ```html
 <h3>Vegetables</h3>
@@ -84,7 +84,7 @@ The hierarchy of the content must be respected through the headings. This exampl
 Even if it is preferable to use headings for content sections, this does not represent non-compliance.
 
 #### Missing h1
-Similarly, it is not mandatory to beginning a heading hierarchy with an `<h1>`.
+Similarly, it is not mandatory to start a heading hierarchy with an `<h1>`.
 
 #### A single `<h1>`
 Very often the heading `<h1>` is reserved for the main heading of the page, but this is not a requirement. Having several `<h1>` does not represent a non-compliance.

_doc/accessibility/information-structure/unordered-ordered-definition-lists.md

@@ -12,7 +12,7 @@ description: Accessibility of unordered, ordered and definition lists
 
 **Impact:** Moderate to high
 
-**Users mainly impacted:** Blind, severely visually impaired, motor handicapped, cognitive disability.
+**Users mainly impacted:** Blind, severely visually impaired, motor impaired, cognitive impaired.
 
 **RGAA criteria:** [Criterion 9.3](https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/#crit-9-3)
 {: .criteria }
@@ -21,11 +21,9 @@ description: Accessibility of unordered, ordered and definition lists
 
 Structuring content with the right elements provides an enhanced navigation experience for screen reader users.
 
-A blind, visually impaired or reading impaired user who uses a screen reader to browse the content of a page will use keyboard shortcuts to navigate between item types. It can navigate from title to title, go to the next form field, or go to the previous list.
+A user who is blind, visually or reading impaired, and uses a screen reader, will use keyboard shortcuts to browse the content of a page. So, he will be able to reach or skip the previous/next header, link, form, field, list, iframe...
 
-In addition to allowing you to navigate between elements, it also allows you to avoid them.
-
-In the case of a list, the number of items in the list is announced, as well as the level of the item in the list. Thus, if the user finds the list too long, he or she can simply avoid it rather than go through it in its entirety, or go to the beginning of the list, or to the end directly.
+In the case of a list, the number of items in the list is announced, as well as the level of the item in the list. Thus, if the user finds the list too long, he/she can simply skip it rather than go through it in its entirety, or go to the beginning of the list, or to the end directly.
 
 ### Three types of lists are identified
 
@@ -45,6 +43,6 @@ A menu with a large tree structure should use the nested lists to better priorit
 
 <div class="tip">
 <svg role="img" aria-label="Tip" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 352 512" width="28" height="40"><title>Tip</title><path d="M96.06 454.35c.01 6.29 1.87 12.45 5.36 17.69l17.09 25.69a31.99 31.99 0 0 0 26.64 14.28h61.71a31.99 31.99 0 0 0 26.64-14.28l17.09-25.69a31.989 31.989 0 0 0 5.36-17.69l.04-38.35H96.01l.05 38.35zM0 176c0 44.37 16.45 84.85 43.56 115.78 16.52 18.85 42.36 58.23 52.21 91.45.04.26.07.52.11.78h160.24c.04-.26.07-.51.11-.78 9.85-33.22 35.69-72.6 52.21-91.45C335.55 260.85 352 220.37 352 176 352 78.61 272.91-.3 175.45 0 73.44.31 0 82.97 0 176zm176-80c-44.11 0-80 35.89-80 80 0 8.84-7.16 16-16 16s-16-7.16-16-16c0-61.76 50.24-112 112-112 8.84 0 16 7.16 16 16s-7.16 16-16 16z"/></svg>
-It is notalways  necessary to list a succession of elements, reading a list in a technical assistance can be very verbose. For example, with a breadcrumb trail, this sequence of pages does not necessarily have to be listed.
+It is not always necessary to list a succession of elements, reading a list in a technical assistance can be very verbose. For example, with a breadcrumb trail, this sequence of pages does not necessarily have to be listed.
 <br>*See the breadcrumb of this page*.
 </div>