This website is committed to providing a usable experience for anyone visiting it, regardless of technology or ability. It strives to meet the level AA standards outlined in the Web Content Accessibility Guidelines (WCAG) 2.2. This guide helps to explain how to make web content easier to use for disabled people.
Accessibility features #
The pages are structured with semantic elements like
footer. Hopefully this will help you move around more quickly. Heading
h1 elements mark the main content area of each page, and each page’s structure should follow a logical heading order from there.
Every page on this website has a “skip to the main content” link at the top and bottom, as well as a “back to top" link at the very bottom which will return you to the start of this page / document.
Images and inline SVGs are described with text equivalents, to ensure everyone can access graphical content. You should be able to zoom each page up to at least 300% without any issues.
label and associated
input fields use a unique value for their respective
There are no
This website has been tested on modern browsers, with occasional checks in older devices or browsers to make sure it’s usable. I frequently test my work with the VoiceOver screen reader as well as the built in screenreader for Microsoft Edge. I occasionally run accessibility audits in aXe and WAVE.
Known issues #
Sometimes I embed media in my posts, like audio or video. Some of these posts may have media that isn’t adequately described. I plan to correct this, but if you encounter confusing media, please email me to let me know.
Send me feedback #
I do care about accessibility but am still learning new things about it most days. If there are any issues with this site’s accessibility please let me know by submitting a GitHub issue, or by emailing me directly. I will try to remedy the problem as quickly as time allows. I honestly would welcome your feedback or suggestions.