Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-65034

Improve accessibility of forum discussion

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 3.7
    • Fix Version/s: 3.7
    • Component/s: Forum
    • Labels:
    • Testing Instructions:
      Hide
      1. Create a site with a course and a few users enrolled in the course
      2. Create a forum with a discussion
      3. Log in as each of the users and create a few replies in the discussion (make sure you reply to a few different posts not just the first post)
      4. Log in as a user and view the discussion page using a screen reader
      5. Navigate around the discussion page with the screen reader
      6. CONFIRM that the first post mentions how many replies are in the discussion when it's focussed
      7. CONFIRM that replies to other posts mention the author of their parent post when they are focussed
      8. CONFIRM that the up/down/home/end keys navigate through the list of forum posts
      9. Tab into the list of post actions (edit, delete, reply etc) and CONFIRM that the screen reader announces which post the menu bar belongs to
      10. CONFIRM that you can change which action is focussed by using the left/right/home/end buttons
      11. Tab away from the menu bar and then back into it
      12. CONFIRM that the when focus goes back into the menu bar it goes back to the last item that was focussed before leaving it (only one item in the menu bar should be in the tab index at any given time)
      Show
      Create a site with a course and a few users enrolled in the course Create a forum with a discussion Log in as each of the users and create a few replies in the discussion (make sure you reply to a few different posts not just the first post) Log in as a user and view the discussion page using a screen reader Navigate around the discussion page with the screen reader CONFIRM that the first post mentions how many replies are in the discussion when it's focussed CONFIRM that replies to other posts mention the author of their parent post when they are focussed CONFIRM that the up/down/home/end keys navigate through the list of forum posts Tab into the list of post actions (edit, delete, reply etc) and CONFIRM that the screen reader announces which post the menu bar belongs to CONFIRM that you can change which action is focussed by using the left/right/home/end buttons Tab away from the menu bar and then back into it CONFIRM that the when focus goes back into the menu bar it goes back to the last item that was focussed before leaving it (only one item in the menu bar should be in the tab index at any given time)
    • Affected Branches:
      MOODLE_37_STABLE
    • Fixed Branches:
      MOODLE_37_STABLE
    • Epic Link:
    • Pull Master Branch:
      MDL-65034-master

      Description

      Improve the accessibility of discussions in the forum.

      Some feedback we've had on what needs improving:

      1. Semantic structure is vague. Screen reader users can’t be sure who is replying to whom.
      2. “Show parent” wasn’t clear. Also JAWS focus is unexpectedly moved when “Show parent” is selected – no warning.
      3. Basic forum navigation difficulties often require extensive tabbing.
      4. No announcement about the number of discussions and number of replies in a forum.
      5. No in-page reply available.
      6. JAWS user has to tab through all the Atto tools in order to set focus in a text field and begin typing. A simple editor would be preferable (see Advanced forum example).
      7. No confirmation or audio notification that a reply has been successfully posted.
      8. When Permalink is selected, JAWS automatically starts reading everything from start to finish - unpredicatable behavior.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  20/May/19

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours, 30 minutes
                  3h 30m