Uploaded image for project: 'Moodle Community Sites'
  1. Moodle Community Sites
  2. MDLSITE-6321

Add accessibility check as part of the peer review process


    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Low Low
    • Coding style
    • None

      Policy: Optional accessibility check

      If a patch introduces a change on the front end, an optional accessibility check can be done during peer reviews.

      This item has been added to the Peer review checklist.

      In the spirit of keeping accessibility in mind during the development process, in cases where a patch affects the user interface, peer reviewers should make sure to check the accessibility impact of the patch.
      Some quick checks that can be included:

      1. Does it pass automated accessibility checks? (e.g. via axe or WAVE)
      2. Does it generate valid HTML? (e.g. checked via Nu HTML validator)
      3. Can you successfully navigate through the interface via keyboard?
      4. If you're using a screen reader (e.g. ChromeVox, NVDA, JAWS), are the UI components being properly announced?

      This will also raise awareness about accessibility among the devs and help us all upskill in terms of web accessibility.


      Option A
      • Yes!
      Option B
      • Meh!
      Option C

            4 Vote for this issue
            17 Start watching this issue


                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.