Accessibility

Last updated

This accessibility statement applies to craigabbott.co.uk.

Although this is a personal website and not covered by accessibility law, I want as many people as possible to be able to use this website. This means you can:

  • zoom in up to 400% without the text spilling off the screen
  • navigate all of the website using a keyboard
  • navigate all of the website using speech recognition software
  • listen to all of the website using a screen reader
  • use forced colours mode or high contrast themes without losing content or functionality

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

Compliance status

This website is fully compliant with the Web Content Accessibility Guidelines version 2.2 AA standard.

Contact information

I’m always looking to improve the accessibility of this website. If you find any problems please contact me and let me know. You can open an issue on GitHub or contact me via one of the following ways:

Forced colours mode

This website supports forced colours mode, sometimes known as Windows High Contrast Mode or Contrast Themes.

When forced colours mode is turned on, your operating system replaces the website’s colours with the palette you have chosen. This website respects that palette, and also makes sure that:

  • buttons and other interactive controls keep visible borders
  • links and controls show a visible outline when you hover over or focus on them
  • logos keep their own colours so they stay recognisable, and any text they contain adapts to stay readable
  • the colour switches in the display settings are removed, because your system settings decide the colours instead; the Time limits switch stays

Display settings

The settings button in the header opens four switches. Three change how the website looks:

  • Dark theme swaps the light theme for the dark one
  • High contrast makes every colour a step bolder: quieter text and borders become the main text colour, patterned backgrounds go flat, and the focus indicator gets thicker
  • Greyscale shows the website in black and white, including photographs and logos

The fourth, Time limits, controls messages that appear for a moment, such as the confirmation when you copy a code block. With it on, which is the default, a message clears itself after three seconds. Turn it off and messages stay until you dismiss them with the button they then carry.

Until you move a switch, it follows your system settings: Dark theme and High contrast match your operating system’s colour scheme and contrast settings, Greyscale is off and Time limits is on. When you move a switch, your choice is saved in your browser and used on every visit. Moving it back to agree with your system clears the saved choice, so the website follows your system again. Reset clears all four at once.

The settings need JavaScript. Without it, the website follows your system’s colour scheme and the control is not shown.

Assistive technology support

This website has been tested using a variety of combinations.
Assistive technology Operating system Browser
Jaws,
2026.2603.86 		Windows 11 Home,
26200.8875 		Chrome,
150.0.7871.187
NVDA,
2026.1.1 		Windows 11 Home,
26200.8875 		Firefox,
153.0.1
Voiceover,
27.0.1 		Mac OS,
27.0.1 		Safari,
27.0.1
Voiceover,
27.0.1 		iOS,
27.0.1 		Safari,
27.0.1
TalkBack,
17.1.0.9 		Android,
17 		Chrome,
155.0.80
Voice Access,
26200.8875 		Windows 11 Home,
26200.8875 		Edge,
151.0.4129.59
Voice Control,
26.5.2 		Mac OS,
26.5.2 		Safari,
26.5.2
Contrast themes,
  • Aquatic
  • Desert
  • Dusk
  • Night sky
Windows 11 Home,
26200.8875 		Edge,
151.0.4129.59

Known issues

ARC Toolkit

  • On every page, ARC Toolkit incorrectly flags “insufficient large text contrast” on the heading level 1. This is a false positive, as ARC only appears to assess the background colours, and not the computed colour on the text outline, which is above 4.5:1.
  • On the lightbox component, when viewing images at full size, ARC incorrectly flags a “non-interactive element in the tab order”. This is a false positive. The element in question is a `
    ` containing the image, which is deliberately added to the tab order so that keyboard users can scroll the zoomed in image.

Chrome for Android with TalkBack

When the mobile navigation menu id open on mobile, activating a switch or or button in the settings makes TalkBack read the whole menu again before it announces the change. For example, turning on Dark theme reads out every link in the menu, then “On, Dark theme”.

This is a bug in Chrome, not in this website. Chrome tells TalkBack that the dialog has opened again every time focus moves inside it, and it happens on every website that uses a dialog. I have file a bug report with the Chromium project. It does not affect compliance with WCAG level AA, though I acknowledge it’s not the best user experience. Every control still works, keeps focus and announces its new state. It was found with Chrome version 155 and TalkBack 17.1 on Android 17. I will monitor this situation via the bug report, and hope to fix it in the future.