Accessibility testing documentation improvements #1507
Conversation
✅ Deploy Preview for moodledevdocs ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
This PR refactors the accessibility documentation by moving the "Accessibility testing" section from the main accessibility policy page to its own dedicated page, and updates all WCAG references from version 2.1 to 2.2 throughout the developer documentation.
Changes:
- Created a new comprehensive accessibility testing guide at
general/development/policies/accessibility/testing.mdwith expanded content on automated and manual testing approaches - Updated all WCAG 2.1 references to WCAG 2.2 across the accessibility policy documentation
- Updated internal links across the documentation to reflect the new accessibility directory structure
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
| general/releases/1.8.md | Updated link to accessibility policy (removed .md extension) |
| general/documentation/accessibility.md | Updated link to accessibility policy and changed "coding standards" to "coding guidelines" |
| general/development/process/peer-review/accessibility-checklist.md | Updated link to accessibility policy page titles section (added index.md) |
| general/development/policies/codingstyle/index.md | Updated link to accessibility coding standards (added index.md) |
| general/development/policies/accessibility/testing.md | New comprehensive accessibility testing guide with automated and manual testing guidance |
| general/development/policies/accessibility/index.md | Removed accessibility testing section (moved to separate page) and updated all WCAG 2.1 references to WCAG 2.2 |
| general/development/policies.md | Updated link to accessibility policy (removed .md extension) |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| :::note | ||
|
|
||
| This page describes the accessibility of the Moodle Developer Resources site. For details of the accessibility conformance of Moodle products, coding standards and other developer resources related to accessibility, see [Accessibility](../development/policies/accessibility.md). | ||
| This page describes the accessibility of the Moodle Developer Resources site. For details of the accessibility conformance of Moodle products, coding guidelines, and other developer resources related to accessibility, see [Accessibility](../development/policies/accessibility). |
There was a problem hiding this comment.
The text "coding guidelines" is inconsistent with the actual section heading in the accessibility policy page, which is "Coding standards". This creates a mismatch between the link text and the target section heading. Either update this to "coding standards" to match the target heading, or update the heading in the accessibility policy to "Coding guidelines" if that's the preferred terminology.
| This page describes the accessibility of the Moodle Developer Resources site. For details of the accessibility conformance of Moodle products, coding guidelines, and other developer resources related to accessibility, see [Accessibility](../development/policies/accessibility). | |
| This page describes the accessibility of the Moodle Developer Resources site. For details of the accessibility conformance of Moodle products, coding standards, and other developer resources related to accessibility, see [Accessibility](../development/policies/accessibility). |
|
|
||
| You should perform accessibility testing when introducing features or bug fixes involving user interface (UI) changes. Combining automated and manual accessibility testing is essential to ensure accessibility of code contributions to Moodle. | ||
|
|
There was a problem hiding this comment.
Consider adding a note at the beginning of the document (after the frontmatter) to indicate this page is part of the Accessibility policy, following the pattern used in other subdirectory documentation pages. For example: "This page forms part of the Moodle Accessibility guidelines." Additionally, consider adding a "See also" section at the end with a reference back to the main Accessibility policy page for better navigation.
| You should perform accessibility testing when introducing features or bug fixes involving user interface (UI) changes. Combining automated and manual accessibility testing is essential to ensure accessibility of code contributions to Moodle. | |
| This page forms part of the [Moodle Accessibility](.) guidelines. | |
| You should perform accessibility testing when introducing features or bug fixes involving user interface (UI) changes. Combining automated and manual accessibility testing is essential to ensure accessibility of code contributions to Moodle. | |
| ## See also | |
| - [Moodle Accessibility](.) |
junpataleta
force-pushed
the
a11ytestingimprovements
branch
from
08ffe80 to
56207d0
Compare
1 participant
This patch moves the
Accessibility testingsection of the Accessibility policy to its own page. This patch also introduces improvements and provides more information on accessibility testing in Moodle development.A bit unrelated, but the 2nd commit of the patch updates the WCAG 2.1 references in the dev docs to WCAG 2.2.