Website accessibility statement

These websites are built on the Mosaic platform, which has its own technical accessibility statement.

In addition:

• Image maps and the websites logo are not accompanied by a text alternative. This doesn’t meet WCAG 2.2 success criterion 1.1.1 (Non-text Content).
• There are skipped heading levels throughout the website. This doesn't meet WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• Pre-recorded videos don't always include an audio description. This doesn't meet WCAG 2.2 success criterion 1.2.5 (Text-based Media)
• Some of our documents don’t meet accessibility standards: for example, they may not be marked up so that they’re accessible to a screen reader

SOLO is built on a third-party product called Primo. Where no fix date is supplied, we are in the process of obtaining timescales from our supplier and will update this statement no later than December 2024 with the outstanding dates.

• Some form elements have missing labels. This is the two input boxes: Any field contains AND Any field contains’ at the base of the ‘advanced search criteria’ box. This fails WCAG 2.2. Success Criterion 4.1.2: Name, Role, Value (Level A) and we are liaising with the supplier to provide a fix for this.
• There are issues with the ARIA roles in the navigation bar div element, the search result list and the list below the list below the ‘Export Options’ heading. This fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships (Level A) and will be resolved by the end of November 2024.
• There is a missing ARIA label with the input box next to 'contains' in the search string below the 'Search Criteria' heading which fails WCAG 2.2 Success Criterion 1.3.1: Info and Relationships and WCAG 4.1.2 Name, Role, Value and we are liaising with the supplier to provide a fix for this.
• The tabbing order is counterintuitive when the ‘search criteria’ menu is expanded using the down arrow. Users have to tab backwards to access the menu. This fails WCAG 2.2 Success Criterion 2.4.3 Focus Order and will be resolved by the end of December 2024.
• At 200% zoom, the two 'Enter a search term' input boxes and the 'Add a new line' span element in the 'Advanced Search' menu are partly cut off. This fails WCAG 2.2 Success Criterion 1.4.4 Resize Text and will be resolved by the end of March 2025.
• In some instances at 400% zoom and in mobile view, the 'Simple Search/'Advanced Search' button is no longer available. Usually this is available in the '...' more button, but that is not always the case. This fails WCAG 2.2 Success Criterion 1.4.10 Reflow. We are investigating this issue to further to understand when this issue occurs.
• The focus is missing for one tab between the 'Tags' link and the close button in the modal that appears when the user activates the 'More' button in the navigation bar. The focus on the search results is not always visible, making the section confusing to navigate. This fails WCAG 2.2 Success Criterion 2.4.7 Focus Visible and will be resolved by the end of February 2025.

• Not all content can be navigated by keyboard, including forms. It is also not possible to always navigate from expanded images. This doesn’t meet WCAG 2.2 success criterion 2.1.1 (Keyboard).
• Some of our search inputs and forms aren’t labelled appropriately. This doesn't meet WCAG 2.2 success criterion 3.3.2 (Labels or Instructions).
• There are skipped heading levels throughout our blogs. This doesn't meet WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
• Some link text doesn’t make sense when read on its own (for example, ‘click here’). This doesn't meet WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context).
• Some link text on the page is repeated but links to different destinations. This doesn't meet WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context).
• Some text is in a very small font;
• There are colour contrast issues with some of the text found across the blogs. This doesn't meet WCAG 2.2 success criterion 1.4.3 Contrast (Minimum).
• Some images are missing alt tags or have alt tags which are not meaningful. This doesn't meet WCAG 2.2 success criterion 1.1.1 (Non-text Content).
• Not all video has captions, text or audio description. This doesn’t meet WCAG 2.2 success criterion 1.1.1 (Non-text Content). 
• Videos and other iframe elements don’t contain a title. This doesn’t meet WCAG 2.2 success criterion 4.1.2 (Name, Role, Value). 
• Some of our links to PDFs and other documents are not clearly signposted in links. This doesn't meet WCAG 2.2 success criterion 2.4.4 Link Purpose (In Context).
• Embedded prerecorded videos do not contain audio descriptions. This doesn't meet WCAG 2.2 success criterion 1.2.5 (Audio Description (Prerecorded)).
• It is not easy to understand the input purpose for some of our form inputs. This doesn't meet WCAG 2.2 success criterion 1.3.5 (Identifying Input Purpose).
• Some functionality is lost at 400% zoom, particularly the cookies notice at the top of the page. This doesn't meet WCAG 2.2 success criterion 1.4.10 (Reflow).
• Many of our documents don’t meet accessibility standards – for example, they may not be marked up so that they’re accessible to a screen reader.

These platforms are developed by the SpringShare.

LibGuides

• Some ARIA labels have been used incorrectly, making it hard for accessibility tools to navigate the website. This fails WCAG 2.2 Success criterion 1.3.1 (Info and Relationships (Level A));
• Some link text doesn’t make sense when read on its own (for example, ‘click here’).  This doesn't meet WCAG 2.2 success criterion 2.4.4 (Link Purpose (In Context));
• Some tables do not have table row or column headers. This doesn't meet WCAG 2.2 1.3.1 (Info and Relationships);
• Some images are missing alt tags or have alt tags which are not meaningful. This doesn't meet WCAG 2.2 success criterion 1.1.1 (Non-text Content);
• Videos and other iframe elements don’t contain a title. This doesn’t meet WCAG 2.2 success criterion 4.1.2 (Name, Role, Value);
• The focus doesn't get reset to the first content on top of page after the 'Back to top' button is accessed via keyboard navigation. This doesn't meet WCAG 2.2 2.4.3  (Focus Order);
• Tooltips are dismissible only when the tooltip has lost hover or focus.This doesn't meet WCAG 2.2 1.4.13 (Content on Hover or Focus);
• Many of our documents don’t meet accessibility standards – for example, they may not be marked up so that they’re accessible to a screen reader;
• Some of our links to PDFs and other documents are not clearly signposted in links;

LibCal

• The available booking tool by week on LibCal doesn't include table headers. This doesn't meet WCAG 2.2 1.3.1 (Info and Relationships);
• Images do not have alt tags which are not meaningful. This doesn't meet WCAG 2.2 success criterion 1.1.1 (Non-text Content);
• Colour is used to convey availability of slots. This doesn't meet WCAG 2.2 success criterion 1.4.1 (Use of Colour);
• When a user makes a new booking from the equipment, seat, space, and event pages, users must complete the reservation form within 10 minutes of when they begin their request for events and 5 minutes for equipment/seat/space bookings. A user is unable to adjust this timeout. This doesn't meet WCAG 2.2 success criterion 2.2.1 (Timing Adjustable);
• The daily availability view can only be accessed by scrolling horizontally. This doesn't meet WCAG 2.2 success criterion 1.4.10 (Reflow).
• The search by facilities checkboxes are missing a title for these fields. This doesn't meet WCAG 2.2 success criterion 3.3.2 (Labels and Instructions).

• Not all content – such as the Gift Aid form – can be navigated by keyboard. This fails WCAG 2.2 criterion 2.1.1 (Keyboard);
• Some of our forms and input buttons aren’t labelled appropriately. This fails WCAG 2.2 criterion 1.3.5 (Identifying Purpose);
• There is some inappropriate use of ARIA labels, making it hard for accessibility tools to navigate the website. This fails WCAG 2.2 Success criterion 1.3.1: Info and Relationships (Level A).

• Not all content can be navigated by keyboard, such as the collection navigation trees;
• Focus states are always clear when using a keyboard to move through site, such as the collection navigation trees;
• Some of our search inputs and forms aren’t labelled appropriately;
• Some ARIA labels have been used incorrectly, making it hard for accessibility tools to navigate the website;
• If styling is removed, not all content is displayed in a logical manner.
• There are colour contrast issues with some of the text found across the websites.
• Some information has just been presented graphically with no alternative, in particular the list of items included in the database on the homepage.

This covers a suite of websites built on the same technology platform:

• Armenian Manuscripts
• Fihrist
• Genizah Cairo
• Georgian Manuscripts
• Hebrew Manuscripts
• Medieval Manuscripts
• Shan Buddhist manuscripts in UK and SE Asian collections
• South Asian Manuscripts
• Tibetan Manuscripts

The issues are:

• Some of our search inputs and forms aren’t labelled appropriately;
• Some ARIA labels have been used incorrectly, making it hard for accessibility tools to navigate the website;
• The language of the websites is not defined. 

• Not all components have ARIA labels, making it hard for accessibility tools to navigate the website;
• Some of our form fields aren’t labelled correctly.
• Not all text has sufficient contrast against the background colour.

• Some pages contain HTML validation errors effecting the robustness of the website.
• Some issues with text display at different resolutions and orientations on some portable devices – such as overlap of text when reading horizontally on a tablet;
• Some information has been presented graphically or as an image with no alternative text, in particular content included on the statistics pages.
• Many of the documents available from the website don’t meet accessibility standards – for example, they may not be marked up so that they’re accessible to a screen reader.

In 2024–25 we will continue to improve accessibility by doing the following:

• Continue bringing our HTML up to W3C standards
• Improve responsive text display to avoid overlap
• Improve alternative text for the images on the statistics page
• Continue to explore accessible PDF for meeting 10.4 requirements

• There are minor issues with navigability of two elements on the New Request and My Basket pages. These do not prevent the user from entering the required information.