You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: general/development/policies/accessibility/index.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ Moodle is designed to provide equal functionality and information to all people.
18
18
19
19
## Accessibility conformance
20
20
21
-
As part of our ongoing commitment to accessibility and continuously improving conformance with the WCAG 2.1 Level AA success criteria, Moodle is working with an external team of accessibility specialists to review the accessibility of its products through regular accessibility audits.
21
+
As part of our ongoing commitment to accessibility and continuously improving conformance with the WCAG 2.2 Level AA success criteria, Moodle is working with an external team of accessibility specialists to review the accessibility of its products through regular accessibility audits.
22
22
23
23
### Accessibility accreditations
24
24
@@ -143,13 +143,13 @@ All text that is presented needs to be displayed in a colour with sufficient con
143
143
144
144
It is worth noting that colour alone **must not** be used to imply meaning. An example of a failure for this would be to display error messages in "red" with no other information to convey that this is an error message.
145
145
146
-
See [the W3C advice on the use of colour](https://www.w3.org/TR/WCAG21/#use-of-color) from WCAG 2.1 for more information.
146
+
See [the W3C advice on the use of colour](https://www.w3.org/TR/WCAG22/#use-of-color) from WCAG 2.2 for more information.
147
147
148
148
### Icons
149
149
150
150
Icons (Images) can be displayed in a variety of ways, and the correct use of icons will depend on the context in which they are used.
151
151
152
-
See [the WCAG 2.1 requirement for text alternatives](https://www.w3.org/TR/WCAG21/#text-alternatives) for more information.
152
+
See [the WCAG 2.2 requirement for text alternatives](https://www.w3.org/TR/WCAG22/#text-alternatives) for more information.
153
153
154
154
#### Solitary Icons
155
155
@@ -165,13 +165,13 @@ When multiple icons are displayed in a row as links, it is important that each i
165
165
166
166
The minimum valid size for a link target is 44 by 44 pixels.
167
167
168
-
See [the WCAG 2.1 requirement for target size](https://www.w3.org/TR/WCAG21/#target-size) for more information.
168
+
See [the WCAG 2.2 requirement for target size](https://www.w3.org/TR/WCAG22/#target-size) for more information.
169
169
170
170
### Keyboard Support
171
171
172
172
All components should be entirely operable through a keyboard-only interface.
173
173
174
-
See [the WCAG 2.1 requirement for keyboard accessibility](https://www.w3.org/TR/WCAG21/#keyboard-accessible) for more information.
174
+
See [the WCAG 2.2 requirement for keyboard accessibility](https://www.w3.org/TR/WCAG22/#keyboard-accessible) for more information.
175
175
176
176
Some important things to consider is that all components should be focusable with the keyboard (available in the tab sequence), and should allow the focus to be moved away using only the keyboard.
177
177
@@ -186,13 +186,13 @@ Moodle forms created with the standard forms library are designed to be accessib
186
186
- All form elements must have a label
187
187
- The form must be able to be completed entirely with the keyboard
188
188
- Invalid entries in the form fields should be indicated with the "aria-invalid" attribute set to "true"
189
-
- Warning messages for invalid form fields should be associated with the invalid field using the "aria-describedby" attribute. See [the WCAG 2.1 success criteria for Error Identification](https://www.w3.org/TR/WCAG21/#error-identification) for further information on this.
189
+
- Warning messages for invalid form fields should be associated with the invalid field using the "aria-describedby" attribute. See [the WCAG 2.2 success criteria for Error Identification](https://www.w3.org/TR/WCAG22/#error-identification) for further information on this.
190
190
191
191
### Presentation Only
192
192
193
193
Any component that contains no information or functionality that is not provided by other components on the page can be considered decorative only. Content that meets this description can be hidden from screen readers using a suitable technique (aria-hidden or presentation role).
194
194
195
-
See [the WCAG 2.1 description of pure decoration](https://www.w3.org/TR/WCAG21/#dfn-pure-decoration) for more information.
195
+
See [the WCAG 2.2 description of pure decoration](https://www.w3.org/TR/WCAG22/#dfn-pure-decoration) for more information.
196
196
197
197
### Landmark regions
198
198
@@ -216,7 +216,7 @@ Some tips for providing a meaningful page title:
216
216
217
217
(not to be confused with Moodle's `\core\context` class and its implementations)
218
218
219
-
According to the [WCAG 2.1 Understanding Docs](https://www.w3.org/WAI/WCAG21/Understanding/on-focus.html#dfn-changes-of-context), a change in context is a major change that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously. It can include changes of user agent, viewport, focus, or content that changes the meaning of the web page.
219
+
According to the [WCAG 2.2 Understanding Docs](https://www.w3.org/WAI/WCAG22/Understanding/on-focus.html#dfn-changes-of-context), a change in context is a major change that, if made without user awareness, can disorient users who are not able to view the entire page simultaneously. It can include changes of user agent, viewport, focus, or content that changes the meaning of the web page.
220
220
221
221
:::
222
222
@@ -276,8 +276,8 @@ This is automatically handled by `$PAGE->set_title()`.
0 commit comments