Accessibility

Accessibility Statement

DSpace continually works to improve the usability and accessibility of the user interface for all users, including those who use assistive technologies such as screen readers.  In addition to working to provide accessible design and features, DSpace's user interface does not interfere with assistive technologies that users may use to navigate web-based applications in general.

Conformance status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.

The DSpace User Interface strives for conformance with WCAG 2.1 level AA. However, as of this writing, we are partially conformant because of limitations noted below. Some AAA criteria may also be supported.  We consider any non-conformant code to be a bug and ask you to report it as detailed below.

How we test for accessibility

Development on DSpace is active and ongoing and we use several methods to ensure accessibility for both existing and new development.  

• We use design principles and coding standards informed by accessibility concerns as documented in User Interface Design Principles & Accessibility. 
• We run automated accessibility scanning tools (Axe by Deque) across the user interface in our end-to-end tests (run via Cypress). These automated tests run for every GitHub pull request submitted to our user interface codebase.
• We also contracted with Deque for an accessibility audit of the DSpace 7 application in Spring 2021. Their feedback was used to inform our design and coding standards.
• We ask institutions who use DSpace to share any of their own accessibility testing results with DSpace developers. Issues found are turned into bug tickets for developers to address in upcoming DSpace releases.
  • If your institution has accessibility testing results to share, please contact Tim Donohue or anyone on our DSpace Steering Group.

Known limitations

Despite our best efforts to ensure accessibility of DSpace, there may be some limitations.  Below is a description of known limitations:

1. We track all known DSpace accessibility issues in our issue tracker with the "accessibility" label: https://github.com/DSpace/dspace-angular/issues?q=is%3Aissue+is%3Aopen+label%3Aaccessibility
2. DSpace development is primarily volunteer-based, and therefore some accessibility tickets may be waiting on a volunteer to claim them.  While we do our best to ensure critical issues are addressed quickly, non-critical issues may not receive attention until a volunteer gets to them.  However, we accept contributions from anyone (in the form of GitHub Pull Requests). 
   1. If an issue is important to you and you have developers on staff (or can hire a service provider), we ask you to consider contributing a fix back to DSpace.  We ask that you let us know about any fixes you plan to contribute by commenting on the issue ticket.  That helps ensure no other institution will duplicate your work.
3. As the DSpace User Interface allows users to upload content, we cannot ensure the quality of user contributions.  DSpace does try to build features that allow administrators to make uploaded content more accessible, but some limitations exist
   1. The MediaViewer (used to view video/audio content) supports subtitles/captioning. However, the captioning files must be uploaded separately at this time.
   2. Thumbnail images (generated from uploaded files) and logos do not yet support custom alternative text. See https://github.com/DSpace/dspace-angular/issues/1306

Reporting accessibility issues

We consider all accessibility issues to be bugs.  Our goal is to achieve and maintain WCAG 2.1 level AA compliance.  We encourage you to report any issues you find, as we regularly improve accessibility in our major and minor releases.

If you locate an accessibility issue, please report it in a GitHub Issue ticket at https://github.com/DSpace/dspace-angular/issues This will help our volunteer developers to analyze the issue more quickly. Ideally, you should provide the following information in the ticket:

• What is the accessibility issue you've found?  If you know of a way to fix the issue, please include it as well.
• Which page(s) of the DSpace web application can this issue be found on?  You may provide simply an example URL of the page on which it is found.
• How could someone else reproduce this issue?  For example, what tool or browser plugin did you use when you found this issue?  If the issue is browser-specific, also note which browser(s) are affected.
• If possible, provide links/screenshots to document the issue or potential fixes. This might include a screenshot showing the issue, a link to WCAG describing the issue or a description from an internal accessibility audit.

We also welcome contributions / accessibility fixes from anyone. If you've found a way to fix the issue, we encourage you to submit a GitHub pull request to our codebase.  Service providers are also available to hire to fix issues and donate them back to the DSpace codebase.