Aberystwyth Arts Centre is committed to making its website accessible
Aberystwyth Arts Centre is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
If you experience any problems with this website, please contact the Marketing Department.
Aberystwyth Arts Centre, Aberystwyth University, Aberystwyth, Ceredigion, SY23 3DE Tel: 01970 622894 / Email: artscentre-marketing@aber.ac.uk
This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to ‘the non-compliances and exemptions’ listed below.
Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services. Information in some of these PDFs have now been used to create pages in HTML. However, some PDFs still exist.
The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.
Any new PDFs or Word documents we publish will meet accessibility standards.
We do not plan to add captions to live video streams because live video is exempt from meeting the accessibility regulations. However, we do plan to add captions to any new videos uploaded to the website.
These regulations do not apply to the content of websites and mobile applications qualifying as archives. In this regulation— “archives” means a website or mobile application which: (i) only contains content that is not needed for active administrative processes; and (ii) is not updated or edited after 23rd September 2019
This statement was prepared on [26.10.2023]. It was last reviewed on [26.10.2023].
This website was last tested in October 2023 The test was carried out by web providers Creo and ticketing system Ticketsolve.
We used this approach to deciding on a sample of pages to test:
Tools used for Ticketsolve:
- Jaws
- NVDA
- VoiceOver
- Axe DevTools was used to programmatically find existing accessibility issues within the application
- Keyboard Testing
Multiple Browser environments have been tested:
- MacOS: Chrome, Firefox, Safari
- Windows 10: Chrome, Edge
- Mobile (iOS): Safari
- Mobile (Android): Chrome
Pages Creo tested:
- Home – Home https://aber-arts.ubuntu.staging.creo
- Whats On – Events https://aber-arts.ubuntu.staging.creo
- Your Visit – Flexible
- Staff Directory – Flexible
- Contact – Contact
Tools used by Creo:
- Page Insights
- Axe
- WAVE
- BrowserStack
- Siteimprove
You can read an accessibility test report here: https://googlechrome.github.io/lighthouse/viewer/?psiurl=https%3A%2F%2Faberystwythartscentre.co.uk%2F&strategy=mobile&category=performance&category=accessibility&category=best-practices&category=seo&category=pwa&utm_source=lh-chrome-ext
The pages tested proved to be compliant with the Lighthouse Accessibility score = 89-96
Further Work & Recommendations
Ticketsolve
While Ticketsolves Ticketbooth application does meet the requirements for WCAG 2.1 levels A &
AA compliance there are areas which could be improved.
Alternative Text for Shows
Show listings include images that are hidden from visually impaired users to comply with
accessibility standards and prevent navigation issues. Future work should include enabling
us to provide alternative text for show images, allowing for a comprehensive display of
both descriptions and images.
Relevant WCAG 2.1 criteria, 1.1.1 Non-text Content.
Enhanced keyboard navigation
The application currently implements “Skip Links” which allows keyboard users to skip to the
pages content. This satisfies the requirements but it could be expanded to provide a number of
useful links for a given page. This would also alleviate issues arising from any timer related
functionality.
Relevant WCAG 2.1 criteria, 2.4.5 Multiple Ways.
Greater usage of autocomplete
Increased autocomplete functionality in Ticketbooth forms would enhance the user experience,
reducing effort for completing operations like checkout and mitigating issues with timer-related
functionality.
Relevant WCAG 2.1 criteria, 1.3.5 Identify Input Purpose
