Skip to main content
Table of contents

This is for internal use by the PaaS team. Public-facing documentation is located at docs.cloud.service.gov.uk.

Accessibility statement for the GOV.UK Platform as a Service team manual

This accessibility statement applies to the GOV.UK PaaS team manual at https://team-manual.cloud.service.gov.uk/.

This website is run by the GOV.UK PaaS team at the Government Digital Service (GDS). We want as many people as possible to be able to use this website. For example, that means you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without problems
  • navigate most of the website using just a keyboard
  • navigate most of the website using speech recognition software
  • listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

We know some parts of this website are not fully accessible:

one page has images in JPEG format multiple pages have screenshots and diagrams that are not explained in the surrounding content

What to do if you cannot access parts of this website

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please contact gov-uk-paas-support@digital.cabinet-office.gov.uk with details of your request.

We’ll aim to reply within 2 working days.

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 gov-uk-paas-support@digital.cabinet-office.gov.uk.

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)[https://www.equalityadvisoryservice.com]

Technical information about this website’s accessibility

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

There are parts of this documentation that are not accessible because of issues caused by our Technical Documentation Template.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

The following pages have images in JPEG format:

https://team-manual.cloud.service.gov.uk/support/shipping_elasticsearch_metrics_to_tenants/#shipping-elasticsearch-metrics-to-our-tenants

There are screenshots and diagrams that are not explained in the surrounding content:

https://team-manual.cloud.service.gov.uk/support/shipping_elasticsearch_metrics_to_tenants/#shipping-elasticsearch-metrics-to-our-tenants

https://team-manual.cloud.service.gov.uk/team/working_practices/#these-are-guidelines-not-rules

https://team-manual.cloud.service.gov.uk/monitoring_alerting/audit/#audit

https://team-manual.cloud.service.gov.uk/technical_design/bosh/#bosh

https://team-manual.cloud.service.gov.uk/architecture_decision_records/ADR039-aiven-metrics-for-users/#context

https://team-manual.cloud.service.gov.uk/architecture_decision_records/ADR040-bosh-access-without-socks/#context

https://team-manual.cloud.service.gov.uk/architecture_decision_records/ADR041-bosh-access-with-mtls/#implementation

These issues should be looked at under WCAG 2.1 success criterion 1.4.5 Images of Text.

How we tested this website

We last tested this website for accessibility issues in August 2020.

We used manual and automated tests to look for issues such as:

  • lack of keyboard accessibility
  • link text that’s not descriptive
  • non-unique or non-hierarchical headings
  • italics, bold or block capital formatting
  • inaccessible formatting in general
  • inaccessible language
  • inaccessible diagrams or images
  • lack of colour contrast for text, important graphics and controls
  • images not having meaningful alt text
  • problems when using assistive technologies such as screen readers and screen magnifiers

What we’re doing to improve accessibility

When we publish new content, we’ll make sure our use of images meets accessibility standards.

We plan to fix the accessibility issues with the images by the end of 2020.

We plan to fix the other accessibility issues by updating our Technical Documentation Template by the end of 2020.

This statement was prepared on 1 September 2020. It was last updated on 1 September 2020.