Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Deferred
    • Affects Version/s: 2.1.1
    • Fix Version/s: None
    • Component/s: Files API
    • Affected Branches:
      MOODLE_21_STABLE

      Description

      There are numerous accessibility problems with the file picker.
      1. It is not clear to screen reader users that a modal window has popped up when the file picker starts.
      2. The focus is initially put on the last item in the file picker so the user must reverse tab through the window to access the file picker functionality.
      3. There is no semantic structure to the file picker to denote that the left side of the window is where you select your repositories and the right side shows you what is in those repositories or lets you execute other actions on the repository. The only logic to its layout is through visual cues.
      4. It is not apparent to a screen reader user that when a repository is selected on the left hand side of the window that something actually changes on the right side of the page.
      5. It is easy to accidentally tab to an area outside of the file picker modal window so that the user is no longer interacting with the file picker.

      To solve these problems there are a number of patches that could be applied, or the file picker could be re-engineered completely.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            Greg Kraus added a comment -

            I'll provide some potential implementation details after I enter the rest of the bugs from the report.

            Show
            Greg Kraus added a comment - I'll provide some potential implementation details after I enter the rest of the bugs from the report.
            Hide
            Michael de Raadt added a comment -

            Thanks, Greg.

            Any suggestions for improvements implementation would be welcomed.

            Show
            Michael de Raadt added a comment - Thanks, Greg. Any suggestions for improvements implementation would be welcomed.
            Hide
            Martin Dougiamas added a comment -

            Please note that there is an alternative file picker that is shown when JS is off (and also when the screen reader setting is set in the profile, I think). Perhaps all we need to do is make this mode be enabled more easily.

            Show
            Martin Dougiamas added a comment - Please note that there is an alternative file picker that is shown when JS is off (and also when the screen reader setting is set in the profile, I think). Perhaps all we need to do is make this mode be enabled more easily.
            Hide
            Greg Kraus added a comment -

            I just saw that alternate picker. The screen reader profile setting didn't activate it, but disabling javascript did. It has promise but I'll need to take a look at it next week when I'm back at my computer with all of my testing software. I also noticed that disabling javascript added "go" buttons to all of the jump menus.

            Show
            Greg Kraus added a comment - I just saw that alternate picker. The screen reader profile setting didn't activate it, but disabling javascript did. It has promise but I'll need to take a look at it next week when I'm back at my computer with all of my testing software. I also noticed that disabling javascript added "go" buttons to all of the jump menus.
            Hide
            Martin Dougiamas added a comment -

            Yes, there are quite a lot of accessibility features activated all over Moodle when JS is off. That used to be the way to do these things.

            Show
            Martin Dougiamas added a comment - Yes, there are quite a lot of accessibility features activated all over Moodle when JS is off. That used to be the way to do these things.
            Hide
            Martin Dougiamas added a comment -

            Also note that re-visiting the filepicker interface is something I want to do anyway for 2.3 (for everyone). A lot of people seem to have trouble with it.

            Show
            Martin Dougiamas added a comment - Also note that re-visiting the filepicker interface is something I want to do anyway for 2.3 (for everyone). A lot of people seem to have trouble with it.
            Hide
            Greg Kraus added a comment -

            It used to be quite common that to make something accessible you had to provide a noscript option. With WCAG 2.0, and the imminent changes to US Law Section 508 (which basically says you need to meet Section 508 Level AA conformance), scripting technologies can be used as long as they are done accessibly.

            http://www.w3.org/WAI/WCAG20/wcag2faq#othertechs

            http://www.w3.org/TR/WCAG20-TECHS/client-side-script.html

            The trend now in accessible design is to provide a single user interface for all people to use as opposed to having to manage an accessible and a more "feature-rich" interface.

            Show
            Greg Kraus added a comment - It used to be quite common that to make something accessible you had to provide a noscript option. With WCAG 2.0, and the imminent changes to US Law Section 508 (which basically says you need to meet Section 508 Level AA conformance), scripting technologies can be used as long as they are done accessibly. http://www.w3.org/WAI/WCAG20/wcag2faq#othertechs http://www.w3.org/TR/WCAG20-TECHS/client-side-script.html The trend now in accessible design is to provide a single user interface for all people to use as opposed to having to manage an accessible and a more "feature-rich" interface.
            Hide
            Greg Kraus added a comment -

            I just checked the noscript version of the file picker. While it is better, screen reader users will still have a hard time with it.

            Since you are using YUI for lots of your interface, there are some accessibility features in there that can be utilized to make the file picker accessible.

            Show
            Greg Kraus added a comment - I just checked the noscript version of the file picker. While it is better, screen reader users will still have a hard time with it. Since you are using YUI for lots of your interface, there are some accessibility features in there that can be utilized to make the file picker accessible.
            Hide
            Greg Kraus added a comment -

            This isn't a scientific study, but the WebAIM Screen Reader User Survey definitely shows a trend toward screen reader users keeping JavaScript enabled. It shows that over 98% of the respondents have JavaScript enabled.

            http://webaim.org/projects/screenreadersurvey3/#javascript

            Show
            Greg Kraus added a comment - This isn't a scientific study, but the WebAIM Screen Reader User Survey definitely shows a trend toward screen reader users keeping JavaScript enabled. It shows that over 98% of the respondents have JavaScript enabled. http://webaim.org/projects/screenreadersurvey3/#javascript
            Hide
            Greg Kraus added a comment -

            To make the file picker more accessible, you might want to look at my comments here.

            http://tracker.moodle.org/browse/MDL-30847?focusedCommentId=138674&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-138674

            The file picker is in essence a modal window with a tab view in it. Using YUI's built-in ARIA capabilities, the file picker can be made much more accessible.

            Show
            Greg Kraus added a comment - To make the file picker more accessible, you might want to look at my comments here. http://tracker.moodle.org/browse/MDL-30847?focusedCommentId=138674&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-138674 The file picker is in essence a modal window with a tab view in it. Using YUI's built-in ARIA capabilities, the file picker can be made much more accessible.
            Hide
            Michael de Raadt added a comment -

            I believe this issue is covered in detail by the linked sub-tasks of MDL-35816. I'm closing this issue as deferred in the hope that we will achieve what this issue sets out to fix in a more fine-grained way.

            Show
            Michael de Raadt added a comment - I believe this issue is covered in detail by the linked sub-tasks of MDL-35816 . I'm closing this issue as deferred in the hope that we will achieve what this issue sets out to fix in a more fine-grained way.

              People

              • Votes:
                22 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: