I want rickshaw.com to be usable by everyone, including readers who rely on assistive technology.
Our commitment
Rickshaw.com aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the standard most widely referenced for web accessibility. Accessibility is an ongoing effort, and I work to keep the site usable for people who browse with screen readers, keyboards, screen magnification, and other assistive technologies.
What I’ve done
The site uses a semantic page structure with proper headings and landmark regions, along with a “Skip to content” link so keyboard users can jump past the menu. Every page can be operated by keyboard alone, and a visible outline shows which link or button has focus.
Text and buttons meet AA contrast levels. Book covers, photos, and other meaningful images carry text descriptions. On phones, the menu button tells screen readers whether the menu is open, moves focus into the menu when it opens, and has a clearly labelled close button. The related-posts carousel on blog posts doesn’t move on its own, and its previous, next, and slide buttons are all labelled.
Layouts reflow when text is enlarged or the screen is small, down to a 320-pixel-wide view (the equivalent of 400% zoom), without sideways scrolling or loss of content.
Conformance status
I aim for rickshaw.com to conform to WCAG 2.2 Level AA. Automated testing of the main page types currently reports no failures, and I back that up with manual keyboard checks at phone and desktop sizes and at high zoom. Automated tools can’t catch everything, though, so I treat conformance as something to maintain and keep testing, and I’d rather hear about a barrier from you than assume there are none.
Other sites I link to
My books are sold through Amazon, my newsletter is published on Substack, and my publisher is 2FBooks. Amazon, Substack, and Goodreads are run by other companies, and I can’t control their accessibility. If one of them gets in your way, let me know and I’ll help you get what you need another way.
Tell me about a problem
If you run into an accessibility barrier on rickshaw.com, email rickshaw@rickshaw.com with the address of the page, a short description of the problem, and, if you can, the browser and assistive technology you were using. I aim to respond within a few business days and will work with you to provide the information you need in an accessible way.
How I test
I assess rickshaw.com using automated tools (including axe) and manual keyboard-only navigation at several screen sizes and zoom levels. This is a self-evaluation; the site has not been audited by an outside party.
This statement was last reviewed in November 2026.