911±¬ÁÏÍø

This accessibility statement applies to Open OnDemand.

is a web-based client portal for HPC centres. We want as many people as possible to be able to use this website, which means that you should be able to:

• change colours, contrast levels and fonts
• zoom in up to 300% 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 website and other websites more effectively.ÌýAbilityNetÌýhasÌý.

How accessible this website is

We know some parts of this website are not fully accessible. You can see a full list of issues we currently know about in the non-accessible content section of this statement.

Feedback and contact information

±Ê±ô±ð²¹²õ±ðÌýcontact usÌý[UPDATE] if you have an accessibility query including:

• If you are experiencing issues with accessing information or using the service
• If you find an accessibility problem not listed on this statement
• If you have positive feedback on the accessibility considerations made.

Reporting accessibility problems with this website

We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please contact usÌý[UPDATE].

Read .

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 .

Technical information about this website’s accessibility

University College London is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the standard, due to the non-compliances and exemptions listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

This section covers issues that we need to fix and are working to do so.Ìý

Please refer to the current for the most up-to-date information regarding its accessibility.

All or most URLs

• Screen readers will see the navigation bar landark as 'banner landmark', 'navigation' and 'navigation landmark', where really we should only have 1 single landmark.
• ManyÌýalerts do not notify screen readers.ÌýAs an example, when you start an interactive session there is an alert to notify the user of its success or failure, but screen readers are not notified of this alert.

Landing page

• The welcome logo does not provide alt text.
• Message of the Day and pinned apps use heading levels 3 & 4 instead of 2 & 3.

Batch connect session cards

• When the cardsÌýchange state, say from 'Queued' to 'Running', there is no notification for the user.
• There isÌýno good organization of these cards.
• Some ambiguous links, like the session id link that is a UUID.

Batch connect app webforms

• When a user updates a form field, another form field may automatically be updated. There is no screen reader notification when this occurs.
• Resolution form fields have labels visible to sighted users, but screen reader navigation does not automatically read them. The user is forced to navigate around the form element to hear the label.

No VNC

This functionality is fully incompatible with screen readers at the time of writing.

Dashboard files table

• The files table does not notify users of updates. When a user clicks through to another directory in the file browser table the table updates with the contents of the chosen directory. However, screen readers are not notified that this change has occured.
• Screen readers read the sorting arrows in the files tableÌýwhen they should only read the column name.
• File browsing landmarks could be better.ÌýThere's currently a little too much navigation to get anywhere interesting.

Shell application

This functionality is fully incompatible with screen readers at the time of writing.

If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Reporting accessibility problems with this website’ section of this statement.

Disproportionate burden

At this time, we have not made any disproportionate burden claims.

Content that’s not within the scope of the accessibility regulations

Third-party content

This websiteÌýcontains 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:

• content/functionality on our website
• content hosted on other websites, such as social media sites
• documents which are sent to us and uploaded, or comments left on pages by members of the public

To help accessibility compliance across the sector, University College London supports , 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 .Ìý

UCL 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

For third-party applications we have sourced accessibility statements from suppliers directly (wherever possible) and added these to (a centralised, independent directory of third-party accessibility information) and documented this in our accessibility statements.

What we’re doing to improve accessibility

UCL has created aÌýDigital Accessibility PolicyÌýto help us embed accessible by design approaches to our own development as well as externally procured digital systems and we are actively engaged in processes to assess and prioritise remediation of existing systems.

In addition, accessibility is at the heart of our new Design System that will underpin all future digital system development.Ìý

Preparation of this accessibility statement

This statement was prepared on DATE. It was last reviewed on DATE. This website was last tested on DATE. The test was carried out by WHOM.