Page History

...

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 to conform with the most recent current version of WCAG level AA. However, as of this writing, we are partially conformant because of limitations noted below. We consider any non-conformant code to be a bug and ask you to report it as detailed below, we acknowledge that achieving full accessibility is a work-in-progress at this time.

How we test for accessibility

...

• 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 ask institutions who use DSpace to share any of their own accessibility testing results with DSpace developers. Accessibility issues discovered 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.
• In 2021, we conducted an accessibility audit of the DSpace application with Deque to get specific feedback on our accessibility conformance. Their feedback has guided our design and coding standards mentioned above.

...

1. We track all known DSpace accessibility issues in our GitHub issue tracker with the "accessibility" label.
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 We accept code 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 please consider contributing a fix back to DSpace.  We ask that you let us know about any fixes you plan to contribute Please claim open tickets by commenting on the issue ticket .  That helps ensure - this ensures that no other institution institutions will duplicate your workefforts.
3. As Since the DSpace User Interface allows users to upload content, we cannot ensure the quality accessibility of user contributions.  DSpace does try to build has some 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, at this time, the WebVTT captioning files must be uploaded separately alongside the original video. 
   2. At this time, DSpace does not support custom alternative text (alt text) for either thumbnail images (generated from uploaded files) or Community/Collection logos.

...

Report accessibility issues

We consider all accessibility issues to be bugs.  Our goal is to achieve and maintain WCAG level AA compliance.  We encourage you to Please report any accessibility 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 issue ticket.  This will help our volunteer developers to analyze the issue more quickly. Ideally, you should provide the following information in the ticketWe will prioritize accessibility issues all of our future releases.

In the ticket, please include the following details:

• 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?  For example, provide the URL of the page or a description of how to get to that page.
• 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 youIf you've found a way to fix the issue, we encourage you to please submit a GitHub pull request to our codebase.  Service providers are also available to for hire to fix issues and donate them back to the DSpace codebase.

...