Accessibility statement

Using this website

This website is run by the Ministry of Justice. We want as many people as possible to be able to use it. That means you should be able to:

• use the whole site, including the registration form, with a keyboard alone
• use it with a screen reader or other assistive technology
• zoom in without text disappearing off the side of the screen
• change colours and contrast through your browser or operating system
• turn animation off, and lose nothing at all by doing so

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

How accessible this website is

The site is designed against WCAG 2.2 level AA, and a number of things follow from that requirement rather than from taste:

• Every colour pair on the site was measured rather than judged by eye. Body text sits at 17.21:1 against the page background. The lowest contrast ratio used for text anywhere is 4.98:1, on the register button; AA asks for 4.5:1.
• The keyboard focus outline is never removed. Anything you can click, you can reach with the Tab key and see clearly when you get there, including in Windows High Contrast Mode.
• Every control accepts at least a 24 by 24 pixel pointer, which is what WCAG 2.2 asks for, and the ones you are most likely to reach for on a phone — the menu button, the theme tabs, the carousel arrows — are 44 by 44.
• The registration form uses ordinary browser controls with visible labels, and follows the GOV.UK error pattern: a summary at the top of the form that takes focus when something is wrong, and a message attached to each field that needs one.
• If your device is set to reduce motion, animation stops. Nothing fades, nothing slides, the moving background on the home page holds on a single frame, and no content is left hidden as a result.
• The first thing the Tab key reaches on every page is a “Skip to main content” link.

Feedback and contact information

If you need anything on this website in a different format — large print, easy read, audio, braille or plain text — email GlobalBusinessandLawSummit@amplitude.org.uk and tell us what you need. Say which page it is and what format would work for you.

Access and dietary requirements for the summit itself are collected at the invitation stage. If you would rather raise something before then, use the same address.

Reporting accessibility problems with this website

We want to hear about anything that gets in your way, including things this statement does not mention. Email GlobalBusinessandLawSummit@amplitude.org.uk with the address of the page and a description of the problem. If you were using a screen reader, magnifier or other assistive technology, telling us which one and which version makes it far quicker for us to reproduce.

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 are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website’s accessibility

The Ministry of Justice is committed to making this website 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 Web Content Accessibility Guidelines version 2.2 level AA, because of the exceptions listed below.

A detailed audit was carried out against WCAG 2.2 AA in August 2026. It examined contrast and colour, reflow and resizing, keyboard operation and focus, pointer targets and motion, forms and error handling, and the names and roles exposed to assistive technology. It found 46 issues, every one of which was then independently re-tested before being accepted. Eleven were serious, and all eleven have since been fixed — most of them in two places: text and controls sitting over the moving background at the top of the page, and the borders on the registration form’s fields, which were close to invisible to anyone with low vision.

We are still not claiming full compliance, and the reason is in the next section rather than in anything we have found and left. Automated and scripted testing finds only a minority of accessibility problems, and the things it is worst at are the things that matter most: whether alternative text is genuinely useful, whether a heading structure makes sense to someone hearing it read aloud, whether a form is understandable in practice rather than merely labelled.

Non-accessible content

These are the parts we think you should know about.

• The moving backgrounds on the home page. There are two, one behind the title at the top and one across the closing panel at the bottom. Both are decoration: they carry no words, no data and no meaning that is not written beside them, so both are hidden from assistive technology. The same artwork sits underneath each as a still image for any browser that cannot or will not run it, and each holds on a single frame if your device asks for reduced motion.
• The closing panel is a link. The artwork at the bottom of the home page links to the Industrial Strategy Professional and Business Services Sector Plan. Because the artwork itself is hidden from assistive technology, the link is named by the label printed in its lower corner, which also says that the document is a PDF and that it opens in a new tab.
• The map in the venue section. It is a drawing of the streets around Mansion House and it is marked as decorative, so a screen reader passes over it. Everything it shows is written beside it as text — the full address and postcode, and the walk from each nearby station.
• Nobody has used this site with a screen reader. The August 2026 audit measured what a browser reports and read what assistive technology would be given; it did not put the site in front of anyone driving it with NVDA, JAWS or VoiceOver, and those are not the same thing. No third-party accessibility specialist has assessed it either, and it has not been tested with disabled people. Those are the three gaps that matter, and all three are outstanding. If you find something because of that, we would genuinely rather hear it from you than not hear it.

How we tested this website

The site is tested automatically on every build, using axe-core driven by Playwright, against the WCAG 2.2 A and AA rule sets. Every page is covered: the home page, the registration page, the privacy notice, and this statement.

Each page is tested three times over, in three configurations:

• a desktop browser
• a mobile browser, at phone width
• a desktop browser with the “reduce motion” preference switched on

The third one exists because of a specific failure this design could have. Content on this site arrives by fading in, and the usual way that breaks is for somebody who has asked for less motion to be left looking at content that never appears at all. Testing with the preference turned on is the only way to catch it.

There is also a keyboard test, which checks that the first thing the Tab key reaches is the skip link, and that following it moves to the main content.

Alongside that, a detailed audit was carried out by hand in August 2026, covering the seven areas listed under compliance status above. Each finding was re-tested independently before being accepted, and nine of the fifty-five raised did not survive that check.

What has not been done: any testing with a screen reader, any testing with disabled people, and any assessment by a third-party accessibility specialist.

What we are doing to improve accessibility

Three things are outstanding, and all three are known rather than discovered: testing with a screen reader, testing with disabled people, and an independent assessment. The remaining moderate and minor issues from the August 2026 audit are being worked through in the same period. When any of that is carried out this statement will be updated with what it found, including anything it found that we had described here as fine.

Preparation of this statement

This statement was prepared on 19 August 2026 and last reviewed on 19 August 2026. The automated testing described above was carried out by the team that built the site, and runs again on every build.