Samuel Osei

Accessibility statement

How this site is built to be usable by everyone, and how to tell me when it is not

I want everyone to be able to read what I write here, whatever device, browser or assistive technology they use. This statement explains what I have done to make that possible, where the site still falls short, and how to reach me if something gets in your way.

The standard I aim for

I aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The site is a small collection of text pages with no forms, media players or interactive applications, which keeps most of the guidelines straightforward to meet.

What I have done

  • Plain, semantic HTML. Headings are nested in order, lists are real lists, and each page has one main landmark, a header and a footer, so screen readers can move around by structure.
  • Keyboard access. Every link, button and control can be reached and operated with the keyboard alone, and the focused element is always visibly outlined.
  • Readable type. Body text is set at 20 pixels in a serif designed for reading, with generous line spacing and a measure of about 65 characters. Text can be enlarged to 200 percent, and the page reflows at narrow widths without sideways scrolling.
  • Colour and contrast. Text and background colours in both the light and dark themes exceed the 4.5:1 contrast ratio required by WCAG. Colour is never the only way information is conveyed; links are underlined.
  • A choice of theme. The site follows your operating system’s light or dark setting and lets you override it with the switch in the header. Your choice is remembered on your device.
  • Reduced motion. The few transitions on the site are switched off when your system asks for reduced motion.
  • Footnotes that work two ways. On a desktop browser, footnote numbers show their text in a tooltip on hover or keyboard focus. The same text is always available in the numbered list at the end of the article, and each number is a link that jumps to it and back.
  • Nothing to get past. There are no cookie banners, pop-ups, sign-ups or CAPTCHAs. The site works with JavaScript disabled; you lose only the tooltips, the table of contents panel and the image lightbox.

Known limitations

  • Images in articles. Every image has alternative text, but complex charts or diagrams may not yet have a full text description. Where one is missing, the surrounding paragraphs explain the point the image makes.
  • External links. I link to other websites, videos and PDFs that I do not control, and I cannot guarantee their accessibility.
  • Older browsers. Some styling relies on modern CSS. The text remains readable in older browsers, but layout details such as the table of contents may differ.

Testing

I check pages with keyboard-only navigation, browser zoom and automated tools such as axe and Lighthouse, and I re-check whenever the design changes.

Tell me if something is wrong

If any part of this site is hard to use, or you need something in another format, please email hello@samuelosei.com. Tell me the page address and what happened, and I will fix it or send you the content another way. I aim to reply within a week.