Accessibility roadmap for Birkbeck Data Repository
Accessibility roadmap
This page details all of the known accessibility issues affecting Birkbeck Data Repository, 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 Birkbeck Data Repository with an explanation of what they mean.
- Broken ARIA reference: No target is set for ARIA references, this means that the description will not be presented.
- Empty table header: A table header contains no text. This may result in cells with missing or incorrect header information.
- Image with title: An image has a title attribute but no alternative text value. Though this should describe the image for those using screen readers, alternative text should be used in most cases.
- 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.
- 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.
- 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.
- Missing form label: A form control does not have a corresponding label, meaning that the function or purpose of that form control may not be presented to screen reader users
- Orphaned form label: A form label is present, but it is not correctly associated with a form control. These labels do not provide functionality or information about the form control to the user.
- Plugin: An unidentified plugin is present. This may introduce accessibility issues.
- Select missing label: A select element may not have an associated label. This means that its purpose might not be clear to those using screen readers.
- Suspicious link text: A link contains extraneous text or may not make sense out of context. This may cause confusion about the purpose of the link.
Publicly accessible pages
About
The following accessibility issues are known to affect the about page:
- Missing alternative text (1)
- Plugin (1)
Deposit workflow - upload data
The following accessibility issues are known to affect the 'upload data' stage of the deposit workflow:
- Missing form label (2)
- Layout table (1)
Deposit workflow - data collection
The following accessibility issues are known to affect the 'data collection' stage of the deposit workflow:
- Orphaned form label (41)
Profile
The following accessibility issues are known to affect the user profile page:
- Suspicious link text (1)
- Layout table (3)
Pages for repository administrators
Manage deposits
The following accessibility issues are known to affect the manage deposits page:
- Orphaned form label (1)
Review
The following accessibility issues are known to affect the review page:
- Broken ARIA reference (3)
- Orphaned form label (1)
IR stats
The following accessibility issues are known to affect the IR stats reports page:
- Missing form label (1)
- Empty table header (3)
- Select missing label (5)
- Image with title (3)
- Javascript jump menu (1)
- Layout table (7)
Reports
The following accessibility issues are known to affect the reports page:
- Orphaned form label (1)
Subject editor
The following accessibility issues are known to affect the subject editor:
- Missing form label (1)
- Empty table header (1)
- Select missing label (1)