This website is being built in public and is very much under construction

Accessibility Specialist

Hello World

Posted:

For a long time I've been wanting to get back into regular blogging. Life often gets busy - work, family, children etc can leave little time for other things. Back in the early 2010's I used to blog on my exploration into developing "hybrid" mobile apps, I then had a spate of posts on Medium - both of which I thoroughly enjoyed writing. These days my primary focus is digital accessibility. So, going forward, this site will act as a dumping ground for my thoughts, ideas and discoveries as well as offer resources to people starting out in digital accessibility. It's also going to be a creative playground, allowing me to experiment with different technologies - at the moment, this site is built with 11ty.

In ~2008, when I first started learning about web accessibility, I found it difficult to find authoritive technical guides and documented patterns. Many of the resources and articles available were contradictory and typically focused on the basics, such as colour contrast. Many more focused on advocating for accessibility (which is 100% important) but as I was involved in building design systems, component libraries and enterprise-level UIs I wanted technical code-focused examples. Finding tried and tested solutions and examples of certain patterns was challenging.

With that in mind, I intend to add regular posts and guides on digital accessibility - with the aim of building up a resource for people new to accessibility.

At the time of writing (a sunny but cold day in January 2025), the web accessibility community has come on leaps and bounds with some amazing minds putting out regular, highly detailed content (which I aspire to do).

Here's a small list of links to some of the, in my opinion, best accessibility related content creators and professionals on the web:

In addition, here's some resources I'd encourage everyone interested in web accessibility to become familiar with (more on these in another post!):