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

Follow up forum accessibility improvements

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 3.7
    • 3.7
    • Accessibility, Forum
    • MOODLE_37_STABLE
    • MOODLE_37_STABLE
    • MDL-65373-master
    • Hide
      1. Use a screen reader to test each of the CONFIRM steps
      2. Create a course with a couple of users enrolled
      3. Add a forum activity
      4. Add a couple of discussions to the forum activity
      5. In one of the discussions add a few replies from a few of the different users
      6. Log in as admin
      7. View the forum activity
      8. CONFIRM that when focus moves into the table of discussions the screen reader reads out the number of visible discussions and total discussions in the format "showing X of Y discussions"
      9. View the discussion with all of the posts
      10. Tab to the actions for the first post (the section with "reply", "delete", "split" etc)
      11. CONFIRM that the screen reader announces which post the menu bar belongs to, it should be in the format of "<subject> by <author> menu bar"
      12. Move focus to the "Permalink" item (you can use the left/right keys to change focus inside the menu bar)
      13. CONFIRM that the screen reader reads out "Permanent link to this post" rather than "Permalink"
      14. Move focus to the "Show parent" item
      15. CONFIRM that the screen reader reads out "Permanent link to the parent of this post" rather than "Show parent"
      16. You no longer need the screen reader for the next confirmations
      17. Use the up/down/home/end arrows to navigate through the forum posts (the focus must already be in the list of posts)
      18. CONFIRM that as each post receives focus it gets the blue focus outline
      19. CONFIRM that using the navigation keys doesn't scroll the page if the post is already visible on the page
      20. CONFIRM that using home/end to jump to a post that isn't visible on the page scrolls that post into visibility
      21. Open the in page reply section of one of the posts by clicking the "Reply" link
      22. CONFIRM that while focus is inside the in page reply section that the up/down/home/end keys don't move focus to another post
      Show
      Use a screen reader to test each of the CONFIRM steps Create a course with a couple of users enrolled Add a forum activity Add a couple of discussions to the forum activity In one of the discussions add a few replies from a few of the different users Log in as admin View the forum activity CONFIRM that when focus moves into the table of discussions the screen reader reads out the number of visible discussions and total discussions in the format "showing X of Y discussions" View the discussion with all of the posts Tab to the actions for the first post (the section with "reply", "delete", "split" etc) CONFIRM that the screen reader announces which post the menu bar belongs to, it should be in the format of "<subject> by <author> menu bar" Move focus to the "Permalink" item (you can use the left/right keys to change focus inside the menu bar) CONFIRM that the screen reader reads out "Permanent link to this post" rather than "Permalink" Move focus to the "Show parent" item CONFIRM that the screen reader reads out "Permanent link to the parent of this post" rather than "Show parent" You no longer need the screen reader for the next confirmations Use the up/down/home/end arrows to navigate through the forum posts (the focus must already be in the list of posts) CONFIRM that as each post receives focus it gets the blue focus outline CONFIRM that using the navigation keys doesn't scroll the page if the post is already visible on the page CONFIRM that using home/end to jump to a post that isn't visible on the page scrolls that post into visibility Open the in page reply section of one of the posts by clicking the "Reply" link CONFIRM that while focus is inside the in page reply section that the up/down/home/end keys don't move focus to another post

    Description

      Further to MDL-65034 we've had some additional feedback from our testers about how we can make some more changes.

      Further suggestions as follows:

      1. JAWS reads out "in reply to" now when reading replies to replies, which is great. Our recommendation would be to have everyone see the information that JAWS is reading out so the user experience is equivalent. Everyone benefits from this information, especially users with cognitive or print disabilities, for example.
      2. Parent link is predictable and has the correct re-focus now. The Parent link reads out shortcut keys for navigating to the Parent link, but does not read out a title per se that would give the user more information about what the link does.
      3. The need for extensive tabbing through Atto has been resolved as much as we had time to test. However, we did note one major problem with posting replies. When a JAWS user writes a reply and exits the text field to submit their reply, JAWS' focus jumps unexpectedly to the next reply, prohibiting the user from canceling or submitting the reply they had just written. JAWS didn't detect the Cancel or Submit buttons until Jolynn navigated backward to them. Hope this makes sense.
      4. The number of replies is announced now when a discussion is opened, which is great. The number of discussions is still not announced.
      5. JAWS just goes directly into a plain text field now and the first item in the Atto toolbar was not even detected by JAWS. (Jolynn was testing using JAWS 2018.1811.2.400 and Chrome v. 73.0)
      6. There is no confirmation or audio notification to a JAWS user that a reply has been successfully posted.
      7. JAWS is not detecting a title in the "permalink" link yet, but your work may not have been complete when we tested last Thursday. Chrome is accepted as the standard browser for JAWS testing, but we can try some other browsers. We also need to see how NVDA behaves.

      Additionally, as noted by Peter while testing MDL-65034:

      1. Up/down/home/end keys still scroll the page when shifting focus. Preventing the browser default actions is ok when a screen reader is enabled because it automatically scrolls to the element with focus however without the screen reader the scrolling doesn't seem to be managed so well.
      2. (Damyon also noticed this) the item with focus isn't highlighted on the page (with the blue outline) so when a post has focus you can't visually see it

      Attachments

        Issue Links

          is duplicated by

          Improvement - An enhancement to an existing Moodle feature. MDL-41773 Forum: code an accessible layout

          • Major - Major loss of function, incorrect output
          • Closed

          Activity

            People

              ryanwyllie Ryan Wyllie
              ryanwyllie Ryan Wyllie
              Mihail Geshoski Mihail Geshoski
              Andrew Lyons Andrew Lyons
              Simey Lameze Simey Lameze
              Adrian Greeve, Ilya Tregubov, Kevin Percy, Mathew May, Mihail Geshoski, Shamim Rezaie
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                20/May/19

                Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 2 hours, 2 minutes
                  1d 2h 2m