Accessibility

This site is built using progressive enhancement principles, meaning it should be fully usable even without CSS and JS. Here are the features this site uses to improve accessibility:
  1. Autism friendly colour scheme, with high contrast text
  2. Media with alt text (enforced by pre-commit check)
  3. Semantic HTML
  4. Large, descriptive buttons
  5. Blogs are (mostly) in simple English with few large blocks of texts
  6. Simple and consistent, linear page layouts
  7. Custom keyboard shortcuts are disablable
  8. Respects reduced motion: gallery pauses and videos pause
  9. SSML pronounciation markup on 'McLoughlin' so screen readers can pronounce it properly

Ways this site could improve

Accesibility isn't a Boolean, it's a scale, and there's always work to be done. Here are some ways this site could be improved:
  1. Dyslexia friendly font
  2. Splide gallery is unfriendly to keyboard users
  3. Mail to link relies on JS email obfuscation, so doesn't adhere to progressive enhancement principles
  4. More extensive use of SSML
  5. Blogs entries could be re-written with fewer large blocks of text and more images/diagrams to split up content
  6. On-screen controls to change font size
  7. Some links lack sufficient affordance that they are interactable
I am aware that screen readers currently mis-pronounce several words on this site eg ('pytest', 'lead developer') but I haven't yet worked out a way to ensure easy and consistent SSML markup on dynamic elements.
Back to Home

Keyboard shortcuts