Accessibility statement

How accessible this website is

This site has been designed and built with accessibility as a requirement from the first draft, not an afterthought. The following measures are in place:

• A skip-to-content link at the very start of the page, so keyboard and screen reader users can bypass the navigation and go straight to the main content.
• Semantic HTML5 landmarks throughout, including header, nav, main and footer, so assistive technology can identify and navigate the structure of each page correctly.
• A visually-hidden helper class used to give context to screen reader users, such as labelling the mobile menu button, without cluttering the visual design for sighted users.
• Full keyboard operability: every link, button and form control on this site can be reached and used with a keyboard alone, with a clearly visible focus outline at each stop.
• Colour contrast that meets WCAG 2.2 AA. Where the brand's orange did not hold sufficient contrast against white for body text and call-to-action buttons, I deepened it to a darker shade (#C2410C) specifically so that text and controls remain legible for people with low vision or colour-perception difficulties.
• A responsive layout that reflows for different screen sizes and zoom levels, rather than a fixed design that breaks or requires horizontal scrolling.
• Self-hosted fonts, so the site makes no third-party font requests. This keeps the page free of external tracking connections and avoids the layout shift and delay that third-party font services can introduce.
• Descriptive alt text on images, so people using screen readers get a meaningful description rather than a filename or nothing at all.
• This site currently scores 100 for Accessibility in Lighthouse, Google's automated auditing tool.

Compliance status

This website aims to conform to the Web Content Accessibility Guidelines (WCAG) version 2.2 at Level AA. That standard covers areas such as colour contrast, keyboard access, sensible heading structure, meaningful link text and compatibility with assistive technology. I treat WCAG 2.2 AA as the working baseline for every page I publish here, not an aspiration to get to eventually.

Known limitations

One page on this site, the AI Fundamentals for Imaging and Oncology case study, embeds a live Articulate Rise 360 module inside an iframe so visitors can play the real course rather than a description of it. Rise 360 is third-party authoring software, and while it is built with strong accessibility features, I cannot personally guarantee that every screen inside that embedded module meets every WCAG 2.2 AA success criterion, since its internal rendering is outside my direct control. I mitigate this by giving clear context around the embed on the page itself, and I am glad to provide an accessible alternative to the content, such as a written walkthrough or a version tested with your specific assistive technology, on request.

Where a limitation like this is identified, my approach is to be straightforward about it rather than to claim a standard has been met when it has not. Overstating compliance helps no one and undermines the credibility of the standard.

Why WCAG 2.2 AA matters beyond this site

WCAG 2.2 AA is not simply good practice. It is the specific standard that UK law requires public sector bodies to meet for their websites and mobile applications, under the Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018, as set out by gov.uk's guidance on accessibility requirements for public sector websites and apps. That duty is not limited to public-facing websites: it explicitly extends to intranets and extranets, which means internal staff training platforms, onboarding portals and LMS-hosted courses fall within scope wherever a public sector body is the one providing them. For anyone commissioning or designing learning in or alongside the public sector, WCAG 2.2 AA is best understood as a compliance requirement with legal consequences for getting it wrong, not a technical nicety to bolt on if time allows.

Reporting an accessibility problem

I want to know if any part of this site is difficult for you to use. If you find a problem that is not covered above, please get in touch via the contact page and describe what you were trying to do and what happened. I will look into it and respond directly.

Last reviewed: 6 July 2026.