We are committed to ensuring that our web application is accessible to all users, regardless of their abilities or disabilities. We have conducted a compliance test using Axe Dev Tools Google Chrome Extension on AtoM 7.2 on all accessible pages and subpages of the application.
Instances of Non-Compliance
During the testing, we discovered several instances of non-compliance with WCAG 2.1. Level AA. In most cases we were able to rectify these. However, there are several instances where the issue cannot be rectified without making fundamental changes to the application’s business logic and these are detailed below.
- IDs used in ARIA and labels must be unique
This issue was found on the following page in AtoM:
Authority Records Landing Page
Add / Edit Accession Records
Add Authority Record
Add Archival Description
Edit Archival Institutions
Edit Terms
Edit Function
This issue potentially violates Success Criterion 4.1.2: Name, Role, Value and can cause confusion to assistive technologies such as screen readers
- ul and ol elements must only directly contain lior template elements
This issue was found on the following page in AtoM:
Individual Authority Record
Individual Archival Institution
This issue potentially violates Success Criterion 1.3.1 Info and Relationships and can cause confusion to assistive technologies such as screen readers stopping them accurately conveying list structures to users.
- Form elements must have labels
This issue was found on the following page in AtoM:
Admin Plugins
Admin Themes
This issue potentially violates Success Criterion 1.3.5: Identify Input Purpose and Success Criterion 3.3.2: Labels or Instructions. Form elements should always have associated labels or instructions. This is crucial for visually impaired users who rely on screen readers, as the screen reader will read the label when the user interacts with the form element.
What We Are Doing To Address These Issues
We recognize the importance of web accessibility and will continue to monitor and improve our application to ensure that it conforms to the WCAG 2.1. Level AA guidelines.
We are currently looking at ways to make the application fully compliant with WCAG 2.1. Level AA criteria and will update this accessibility statement when any changes are made.