Accessibility roadmap for Northeastern University London Repository

This page details all of the known accessibility issues affecting [name of organisation], the method that was used to find issues, and the plans in place to fix them.


Plans for fixing known accessibility issues

All of the issues that have been highlighted in this review will be fixed in a planned upgrade to this repository


Method for testing accessibility

This repository was tested using WAVE's web accessibility tool. This tool returns a comprehensive list of features that may limit the ability of users to access a website, especially those using assistive technology such as screen readers. We ran this tool on a version of the repository without branding customisation, covering the pages that users most frequently interact with.


Known accessibility issues, listed by page

These issues are listed by page. Pages that are publicly accessible are listed first, and those for repository administrators can be found lower down. The number in brackets following the description represents the number of instances of that issue on the page. Below is a list of all the accessibility issues known to affect [name of organisation] with an explanation of what they mean.

  • Missing alternative text:There is no alternative text given for an image included in the page. This means that those using screen readers will not be able to access this content.
  • Linked image missing alternative text: There is no alternative text given for an image that is linked to from this page. This means that a screen reader has no content to present to the user regarding the function of a link.
  • Missing form label: A form control does not have a properly associated text label. This means that the function of the form control may not be presented to those using screen readers. The lack of visible description may also make the page harder to navigate for all users.
  • Empty link: A link does not contain any explanatory text. This means that the purpose of the link is not presented to the user, which may cause confusion for those using screen readers.
  • Very small text: Text is very small. This may make reading text on this page difficult for users, particular those with low vision.
  • Layout table: Layout tables are being used to position content visually, for example, to create columns or align content neatly for sighted users. These can introduce reading and navigation order issues especially for those using screen readers.
  • Javascript jump menu: A javascript jump menu is a select element that triggers a new web page with the onchange event handler. This may cause difficulty for users navigating the page with a keyboard as the page will change with each change in the select menu.
  • Broken ARIA reference: No target is set for ARIA references, this means that the description will not be presented.

Publicly accessible pages

Deposit workflow - upload

The following accessibility issues are known to affect the 'upload' stage of the deposit workflow:

  • Missing form label (2)
  • Layout table (1)

Deposit workflow - subject

The following accessibility issues are known to affect the 'subjects' stage of the deposit workflow:

  • Broken ARIA reference (1)

Pages for repository administrators

Review

The following accessibility issues are known to affect the review page:

  • Broken ARIA reference (3)

IR stats

The following accessibility issues are known to affect the IR stats reports page:

  • Missing alternative text (1)
  • Linked image missing alternative text (3)
  • Missing form label (6)
  • Empty link (2)
  • Empty table header (1)
  • Very small text (78)
  • Layout table (7)
  • Javascript jump menu (1)

Reports

The following accessibility issues are known to affect the reports page:

  • Missing form label (14)
  • Broken ARIA reference
  • Layout table (4)

Subject editor

The following accessibility issues are known to affect the subject editor:

  • Missing form label (2)
  • Empty table header (1)