Skip to main content


Accessibility is intrinsic to everything I work on, whether a design or the HTML, CSS and JavaScript a web page is built with.

When designing an interface, it’s vital that the visuals cater for the broadest possible audience, ensuring:

  • colour contrast thresholds are met
  • focus states for links, forms and buttons are obvious
  • the typefaces used won’t prove problematic for visitor with dyslexia
  • text size isn’t too small for some users to read

There are hundreds of considerations that go into designing an accessible interface, and the code is no different:

  • semantic HTML must be used
  • ARIA enhancements should be used where needed
  • CSS and JavaScript should not interfere with users’ experience of the page

This means assistive technology like screen reader and speech recognition software can interpret page contents correctly, giving their users as good an experience anyone else.

Not only should we code in a way that doesn’t harm the experience for users of assistive technology, but users that have activated settings like Dark Mode or reduced motion in their operating system’s preferences should be respected.

Accessibility in your inbox

I send an accessibility-centric newsletter on the last day of every month, containing:

  • A roundup of the articles I’ve posted
  • A hot pick from my archives
  • Some interesting posts from around the web

I don’t collect any data on when, where or if people open the emails I send them. Your email will only be used to send you newsletters and will never be passed on. You can unsubscribe at any time.