Nathan Knowler

Accessibility Statement

The Web is for everyone and so I’d like for that to be the case for this website as well. I am committed to making this website accessible as I can. I would like to conform to level AA of the Web Content Accessibility Guidelines (WCAG) 2.2. This document outlines how I plan to do so and calls out any shortcomings I am aware of.

Features

This website uses the following features:

  • Semantic HTML:
    • Headings for all content.
    • Landmarks such as main, banner, nav, and contentinfo on every page.
  • Accessible Rich Internet Applications attributes (ARIA when necessary to improve the experience.
  • Light and dark colour schemes which are applied based on your system setting.
  • A “skip to content” link, so you can skip past the site banner to the main content.
  • The entire site works without JavaScript with the exception of some blog posts that include demos.

Testing

Most of my testing is done manually. The following are the assistive technologies I am currently manually testing:

  • Manual testing of the following screen readers:
    • NVDA on Windows in Firefox and Edge.
    • Windows Narrator in Edge.
    • VoiceOver for iOS and macOS.
    • TalkBack on Android (though I am using an older version, due to only having an older device).
  • Voice Control on iOS and macOS.
  • Windows High Contrast Mode.
  • Reduced motion settings on various operating systems.

Occassionally, I will run my website through automated testing tools such as Axe or WAVE.

Known issues

The following are known issues that I do plan on addressing at some point in the future.

  • On the blog index page, the non-text contrast of the overlapping underline for the links and the background is insufficient to pass WCAG 2.2 Success Criterion 1.4.11 Non-text Contrast (Level AA).
  • On the blog index page, the skip link will clear the query params from the URL, so for now avoid using it on paginated pages.
  • The iframes used in blog posts are not titled, so some blog posts are not currently passing WCAG 2.2 Success Criterion 2.4.1 Bypass Blocks (Level A).
  • When using Windows High Contrast Mode, the syntax highlighting in blog posts with code blocks is removed. I will explore a high contrast syntax highlighting theme.
  • I cannot guarantee that the demos meet the same accessibility standard I use for the rest of the site.

Feedback

If you find any other issues that I haven’t accounted for, please help me address them by either submitting an issue on GitHub or sending an email to nathan@knowler.dev.