Policy · Last updated September 18, 2026

Accessibility statement

This site is built around the practice of accessibility. This statement describes the standards followed, known limitations, and how to share a barrier you encounter.

Conformance target

This site is designed to meet the Web Content Accessibility Guidelines (WCAG) version 2.2 at Level AA. It is built with the four principles behind those guidelines, which are perceivable, operable, understandable, and robust.

Build method for this site

Heading hierarchy is preserved end to end. Semantic landmarks are used in place of generic containers — header, nav, main, and footer. Interactive controls have visible focus indicators with an offset large enough to read against the site’s light and dark themes.

All informative images include a text alternative. Decorative ornaments are hidden from assistive technology. The ink wash and paper grain in the hero are drawn in CSS and never enter the accessibility tree, and the image plates on the home, about, and writing pages are decorative, so a screen reader does not announce them and no visible label appears. Form fields have visible labels, helpful hints, and inline error messages tied to the field they describe, so a screen reader announces the error together with the label.

Every interactive control meets the minimum target size required at Level AA, and buttons and form fields are well above it. The site honors prefers-reduced-motion by suppressing transitions and reveal animations for visitors who request it. Color is never the only carrier of meaning.

Testing method

The site has been reviewed on every page, in both the light and dark themes, using automated tooling and manual testing.

The automated scans were run with axe DevTools and WAVE in Firefox, and with Lighthouse through PageSpeed Insights on mobile and desktop. WAVE’s contrast checks covered both themes. Manual testing covers keyboard navigation and focus behavior on every page, and the contact form with VoiceOver in Safari. A custom WCAG 2.2 checklist informed by the WebAIM Million study covers the criteria automated tools do not reach.

Known limitations

Two items remain open.

In Firefox, one card on the writing page takes keyboard focus without the page scrolling to bring it into view. The card can still be reached and activated, and every other element on the page scrolls into view as expected. This is logged for repair.

The portrait on the about page and the image plate on the home page are placeholders pending photography.

Reporting a barrier

If you encounter a barrier on this site, please write to tanisa.imoto@gmail.com with a short description of what happened, the page you were on, and the assistive technology in use. The contact form is a second route, and its subject list includes an option for reporting an accessibility problem with this site. A reply usually arrives within a few working days. Reported barriers are taken as a meaningful contribution to the work, not a complaint.

Continuous improvement

Accessibility is approached as continuous practice. Each new page is reviewed against the same checklist used for client work, and the statement above is revised as the site evolves.