Close
This accessibility statement applies to Axiom Planning Tools
Axiom is a third-party owned application. We want as many people as possible to be able to use this application, which means that you should be able to:
- change colours, contrast levels and fonts
- zoom in up to 400% without the text spilling off the screen
- navigate the website using just a keyboard
- navigate the website using speech recognition software
- listen to most of the website using a screen reader
There are a number of customisation options for your browser and device that could help you use this application and other applications more effectively. AbilityNet has advice on making your device easier to use if you have a disability.
Feedback and contact information
Please contact us via MyServices if you have an accessibility query including:
- If you are experiencing issues with accessing information or using the application
- If you find an accessibility problem not listed on this statement
- If you have positive feedback on the accessibility considerations made.
When you contact the Axiom team Via MyServices, there is a process in place to acknowledge your contact, you will receive an email stating who is dealing with your query. This response should also outline potential timescales by which you can expect a reply.
We aim to respond to all contacts within 3-5 working days.
Reporting accessibility problems with this application
We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG (Web Content Accessibility Guidelines) 2.2 AA standards.
We're always looking to improve the accessibility of this application. If you find any problems not listed on this page or think we're not meeting accessibility requirements, please contact us via MyServices.
Read tips on contacting organisation about inaccessible websites.
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about this application's accessibility
University College London is committed to making this application accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
This application is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons. A limited sample of 2 pages was looked at to gauge whether any accessibility failures were present with Axiom. These failures have been fed back to Axiom with a request for them to conduct a full audit of their software.
Non-compliance with the accessibility regulations
There are several issues found using MS Insights. These include:
- Language of page. This fails WCAG 3.1.1 Language of Page (A).
- Colour Contrast issues. This fails WCAG 1.4.3 Contrast (Minimum) (AA).
- Scrollable regions. This fails WCAG 1.3.1 Info and Relationships (A).
Main home screen
A series of figures are in red with a grey background making it hard to see. This fails WCAG 1.4.3 Contrast (Minimum) (AA).
When a user uses the Tab key to move around the page, the order is not correct, or the focus is not seen on some of the elements when you move to them. These fail WCAG 2.4.3 Focus Order (A), WCAG 2.4.7 Focus Visible (AA), and WCAG 1.3.2 Meaningful Sequence (A).
On the main screen, there are a series of menu items that you can navigate to and open. Once opened by a keyboard-only user, they cannot close these items as traditional keys do not work, so the menu stays open and the user journey ends. This fails WCAG 2.1.1 Keyboard (A).
Magnifying to 110% and beyond introduces horizontal scroll bars. The higher the magnification to worse the screen gets for a user. At 250% menu options are lost to the 3 dot button, but the user cannot navigate to this as the tabbing goes behind the option. The 3 dots appear even when there is no magnification turned on. This fails WCAG 1.4.10 Reflow (AA).
With no magnification used, there is a scroll bar to see the figures in the middle of the screen. A keyboard user would not be able to interact with this section. This fails WCAG 2.1.1 Keyboard (A).
There are charts on the page that cannot be read correctly due to the text being squashed. This is with no magnification options being used. This fails WCAG 1.4.1 Use of Colour (A)
There are no headings on this page, so navigation would be harder for some user groups. This fails WCAG 2.4.6 Headings and Labels (AA).
The ‘Show this year’s budget’ or ‘hide this year’s budget’ are only activated by a mouse click, meaning some user groups would not be able to use this section. This fails WCAG 2.1.1 Keyboard (A).
Various clickable icons on the screen are not big enough to pass minimum standards. The minimum is 24x24, but the icons on this page are 16x16. If there is space on the page. This fails WCAG 2.5.8 Target Size (Minimum) (AA).
Some information is presented in a table-style format, but there is no table on the page making it hard for some user groups to get the required information. This fails WCAG 1.3.1 Info and Relationships (A).
D06 Screen
When you open this tab – a user is not told that a new tab opens so a user may think they are on the same updated tab, which could confuse some user groups. This fails WCAG 1.3.1 Info and Eelationships (A).
None of the edit boxes are labelled correctly. This fails WCAG 1.3.5 Identify Input Purpose (AA) and WCAG 1.3.1 Info and Relationships (A).
The graph is not read out. Not able to tab on to it. This fails WCAG 1.4.1 Use of Colour (A) and WCAG 2.4.5 Multiple Ways (AA).
Any combination boxes that are interacted with using the keyboard, result in the next option being chosen rather than allowing a user to cycle through options first. This fails WCAG 2.1.1 Keyboard (A).
When a user is on ‘Grade’ – they do not know what this is or that you can select it to change the graph. Especially if they are using a screen reader. This fails WCAG 1.3.1 Info and Relationships (A).
From 110% magnification and beyond horizontal scroll bars appear. This fails WCAG 1.4.10 Reflow (AA).
Error messages are not read out when they appear. This fails WCAG 3.3.1 Error Identification (A).
Disproportionate burden
At this time, we have not made any disproportionate burden claims.
Content that’s not within the scope of the accessibility regulations
This section covers issues that we do not need to fix right now. The law calls these exemptions.
Third-party content
Our websites may contain third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make best endeavours to work with the third-party to improve its accessibility. This may include:
- links to non-UCL websites
- content/functionality on our website
- content hosted on other websites, such as social media sites.
To help accessibility compliance across the sector, University College London supports searchBOX, a centralised, independent directory of third-party accessibility information.
searchBOX catalogues the contact information and accessibility statements of third-party suppliers, enables the sharing of community-generated accessibility statements, and allows users to map their supplier ecosystem.
Users can access third-party accessibility statements using the free searchBOX Finder service.
University College London encourages all our partners and suppliers to support this effort by ensuring that their accessibility information is included in the searchBOX directory.
Our testing processes
We tested a sample of 2 pages on this web application using a combination of manual and automated checks. If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to the web app owner who will review the issue, make sure it is included in our plan to fix issues and add it into the accessibility statement when it is next updated.
Preparation of this accessibility statement
This statement was prepared on 11 November 2024. It was last reviewed on 11 November 2024. This application was last tested on 24 October 2024. The test was carried out by the Digital Accessibility team.
What we’re doing to improve accessibility
University College London (UCL) are working to fix or provide alternatives for all issues that we are made aware of and as identified by our periodic internal testing and auditing processes.