I strive to make this blog usable for as many people as possible, including readers who use keyboards, screen readers, zoom, or other assistive technologies. The core site is built around clear text, readable type, structured HTML, and steady improvements against common accessibility standards.

In practice, the main HTML site aims for the technical bar shared by WCAG (the usual target is Level AA), which is also the reference most often used under ADA, Section 508, the EAA (via EN 301 549), and AODA. I am not claiming formal certification or a full legal audit—only that the core public pages are designed and maintained with those guidelines in mind.

What is already in place on the core site:

• Semantic structure (header, nav, main, article, footer) and a language attribute on pages
• Skip link to jump to the main content
• Unique page titles and current-page indicators in navigation
• Keyboard focus styles and support for zoom (page scaling is not locked)
• Light and dark color schemes with improved contrast on body and meta text
• Respect for reduced-motion preferences where animations are used
• Labeled form fields (search, subscribe, comments, guestbook) and clear success or error messages
• Comments and page metadata exposed to assistive technologies (not hidden from them)
• Alternative text on gallery images and portrait alt text on the home page; post images keep author-provided alt when present
• Pagination and filter controls named for assistive tech; blog filters stay available on small screens
• External links announced as opening in a new tab where that applies
• Text-oriented alternate formats (Markdown, plain text, raw, e-ink) for lighter reading

If you hit a barrier, find something that does not work with your setup, or have a suggestion, please contact me. Feedback is welcome and helps improve the site for everyone.