Moodle
  1. Moodle
  2. MDL-28354 High priority accessibility problems in Moodle 2.1
  3. MDL-28355

Resource (File, URL, etc) Open action intermediate page link not screenreader-friendly

    Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.1
    • Fix Version/s: None
    • Component/s: Accessibility, Resource
    • Labels:
      None
    • Testing Instructions:
      Hide

      1. Create a new file resource called 'Answers':
      a. Set it to 'Open'.
      b. Add a file named cf101answersv2.pdf.
      c. Save and display.

      2. Observe link to view the file.

      Verify that the link does not contain the filename (cf101answersv2.pdf) which is likely to be difficult for a screenreader to read. Instead the link should use readable English text such as the name manually entered for the item ('Answers') or standard text.

      Show
      1. Create a new file resource called 'Answers': a. Set it to 'Open'. b. Add a file named cf101answersv2.pdf. c. Save and display. 2. Observe link to view the file. Verify that the link does not contain the filename (cf101answersv2.pdf) which is likely to be difficult for a screenreader to read. Instead the link should use readable English text such as the name manually entered for the item ('Answers') or standard text.
    • Workaround:
      Hide

      Well I guess you could rename all your files to be readable by screenreaders, but that is unlikely to happen given institutional file naming standards etc.

      Show
      Well I guess you could rename all your files to be readable by screenreaders, but that is unlikely to happen given institutional file naming standards etc.
    • Affected Branches:
      MOODLE_21_STABLE
    • Rank:
      18026

      Description

      Depending on the option chosen, these resources may display an intermediate page which shows the name and description of the link or file. This page contains a link to actually download the file or go to the URL. At present the text of this link is the filename or the URL itself.

      Example: Say you have a file called b179.bk2chp4.e1i1.pdf. You create a file resource called 'Book 2 Chapter 4' and select Open for the action. When the user clicks on the link on the home page, they see the name ('Book 2 Chapter 4') as a heading, the description, and then a link to the file. The text of the link is:

      Click b179.bk2chp4.e1i1.pdf link to view the file.

      Screenreaders do a very bad job of reading this name. In addition although this is not so much an accessibility problem, the link is worded badly (use of 'click' and English slightly wrong.)

      Two solutions solve this problem:

      1) Always use generic link text:

      View the file

      2) Reuse the item name in the link text instead of the filename:

      View file: Book 2 Chapter 4

      Initially I thought there might be a problem with this because what happens if people upload more than one file, but actually in that case there is always one 'main file' so there is only ever one such link and it is not necessary to include the filename.

      Anyone have opinions on whether this is OK and if so, which approach is preferable?

      NOTE: I realise there are many other places where filenames appear to users, even students, such as forum attachments. These haven't been reported to us - presumably because we don't have any way to give a human-readable name for those files so it would be infeasible to fix them, whereas when files have been uploaded to main course, somebody has already been required to type one.

      In other words we definitely can't fix all of them but we could fix this one.

        Activity

        Hide
        Sam Marshall added a comment -

        Note: OU is happy to code and submit this if HQ are happy with one or other approach.

        Show
        Sam Marshall added a comment - Note: OU is happy to code and submit this if HQ are happy with one or other approach.
        Hide
        Michael de Raadt added a comment -

        Thanks for reporting this issue.

        We have detected that this issue has been inactive for over a year. It was reported as affecting versions that are no longer supported.

        If you believe that this issue is still relevant to current versions (2.5 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

        Michael d.

        TW9vZGxlDQo=

        Show
        Michael de Raadt added a comment - Thanks for reporting this issue. We have detected that this issue has been inactive for over a year. It was reported as affecting versions that are no longer supported. If you believe that this issue is still relevant to current versions (2.5 and beyond), please comment on the issue. Issues left inactive for a further month will be closed. Michael d. TW9vZGxlDQo=
        Hide
        Michael de Raadt added a comment -

        I'm closing this issue as it has been inactive for over a year has been recorded as affecting versions that are no longer supported.

        This is being done as part of a bulk annual clean-up of issues.

        If you still believe this is an issue in supported versions, please create a new issue.

        Show
        Michael de Raadt added a comment - I'm closing this issue as it has been inactive for over a year has been recorded as affecting versions that are no longer supported. This is being done as part of a bulk annual clean-up of issues. If you still believe this is an issue in supported versions, please create a new issue.

          People

          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: