Accessibility statement for TAS-S: UKRI Trustworthy Autonomous Systems Node in Security
How accessible this website is
We know some parts of this website are not fully accessible:
- Some text on some pages lacks sufficient contrast with its background colour, making it harder for users with moderate visual impairments read.
- Links like “here” may not be helpful to users with assistive technology.
- You may find links, which are not listed in a specific way to be accessed by screen readers.
- Some PDF documents aren’t fully accessible to a screen reader.
- Some images don’t have alternative text.
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, please email c.may-chahal@lancaster.ac.uk
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or Braille, please email c.may-chahal@lancaster.ac.uk. We’ll consider your request and get back to you as soon as possible.
What to do if your problem isn’t dealt with satisfactorily
If you have contacted us about an accessibility problem (e.g. because you needed information in a different format, or you think we’re not meeting the requirements of the accessibility regulations) but you feel that this has not been dealt with satisfactorily we want to know.
The first stage would be to raise your concern informally. The aim of this stage is to achieve a quick and easy solution for you. It would be appropriate to take the concern through the relevant contact listed above for reporting an accessibility problem.
But if we do not deal with your concern satisfactorily you can take it through to a formal complaint.
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 website’s accessibility
TAS-S Node is committed to making its website accessible following the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
The website has been tested against the Web Content Accessibility Guidelines (WCAG) [2.1 or 2.2] AA standard.
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard due to the non-compliances listed on this page.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
Links
- You may find link text that doesn’t make sense of it purpose when read on its own (e.g. ‘A symbol that takes to the top of the page’).
- Some links don’t provide text describing their purpose (e.g. content is an image, or link is generated automatically even when there’s no content).
- On some pages there are multiple links with the same link text to the same destinations.
This doesn’t meet WCAG success criterion 2.4.4 Link Purpose and Links with different destinations, 1.3.1 Semantic Links.
Some link text is not possible to update due to historical reasons.
Headings, Text and Tables
Some table headings used insufficient contrast with its background colour. This makes it harder for users with moderate visual impairments read it.
This doesn’t meet WCAG success criterion 1.4.3 Contrast, 1.3. Heading Scopes.
Where content is historical, no longer maintained or kept online for historical or reference reasons, we do not intend to go back and improve it. The website was created in 2020 and we can not to go back and improve it.
PDFs and other documents
We have a large number (around 100) of non-compliant PDF files and have instigated a project to address this. This project began in the autumn of 2020 and is ongoing. This project includes the update or removal of problem files, and a programme of education for web content creators.
PDF titles
- Some PDF documents do not have descriptive titles.
- This does not meet WCAG success criterion 2.4.2 Page Titled.
- Where the PDF is current, we aim to update or remove it as soon as possible We do not intend to update older PDFs.
PDF language settings
- Some PDF documents do not specify the default language of the document.
- This does not meet WCAG success criterion 3.1.1 Language of Page.
- Where the PDF is current, we aim to update or remove it as soon as possible. We do not intend to update older PDFs.
PDF Bookmarks
- Some PDF documents do not provide bookmarks within the document.
- This does not meet WCAG success criterion 2.4.5 Multiple Ways.
- Where the PDF is current, we aim to update or remove it as soon as possible. We do not intend to update older PDFs.
PDF Tags
- Some PDF documents may not contain correct accessibility tags including table headers.
- This does not meet WCAG success criterion 2.4.6 Headings and Labels.
- Where the PDF is current, we aim to update or remove it as soon as possible. We do not intend to update older PDFs.
PDF Images
- Some PDF documents may contain complex images that we are unable to explain within alt text.
- This does not meet WCAG success criterion 1.1.1 Non-Text Content.
- Where the PDF is current, we aim to update or remove it as soon as possible. We do not intend to update older PDFs.
Non-compliance with the accessibility regulations
- You may find images that don’t have a text alternative, so the information in them isn’t available to people using a screen reader.
- Some table headers do not have a valid scope attribute, which tells assistive technologies what the header refers to.
- Links like “here” are not helpful to users with assistive technology.
- You may find links, which are not listed in a specific way to be accessed by screen readers.
This doesn’t meet WCAG success criterion 1.1.1 Non-text Content; 1.3.1Table Headers and Table Heading Scopes; 4.1.2 Screen Reader Links and 2.4.4 Link Purpose.
Some images, which are additional to the text explanation, are impossible to describe due to a complex context.
The website was created in 2020 and we can not to go back and improve Table Heading.
Preparation of this accessibility statement
This statement was prepared and last reviewed on 25 August 2024.
The website was last tested on 25 August 2024 against the WCAG 2.1 AA standard. The test was carried out by TAS-S: Trustworthy Autonomous Systems Node in Security.
We used this approach to test our website for accessibility by ensuring the individual components are accessible:
- We test our website regularly using a tool that scan every page for problems: Silktide.
- We aim to fix high priority issues as they are identified.