Accessibility

Last updated Nov 2, 2026

HostCalmly should work for every host, whether you use a screen reader, a keyboard, voice control, a zoomed screen or a small phone. Our target is the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA.

What we do

  • Every page is plain HTML before any script runs, with one heading structure, labeled fields and a “Skip to content” link.
  • Everything works with a keyboard. Focus is always visible, and the search dialog keeps focus inside it until you close it with Escape.
  • When a calculator result changes, screen readers hear a short summary of the new result, without your focus moving.
  • Text and field borders meet WCAG contrast minimums in the light and dark themes, and buttons, fields and choice chips are at least 44 pixels tall.
  • Pages reflow to 320 pixels wide without sideways scrolling, and respect your reduced-motion setting.

How we test

Our automated test run scans 23 key pages with axe-core against WCAG 2.1 A and AA rules, and browser tests check keyboard focus, horizontal overflow and the dark theme. Automated checks can't catch everything, so we also fix problems readers report.

Known gaps

  • Not every tool announces its result yet. We're adding the spoken summary tool by tool; until then, the result follows the fields in reading order.
  • Long tables, such as the shopping list, can take a while to explore with a screen reader, and the small count fields inside them are under 44 pixels tall.
  • Printed sheets and PDFs you save from the browser (house manual, Wi-Fi sign, checklist) aren't tagged PDF documents.
  • The downloadable spreadsheet and CSV files follow the layout of their tools and have no extra descriptions for assistive technology.
  • Links to vendor and retailer sites lead to pages we don't control.

Tell us about a barrier

If something on HostCalmly is hard or impossible to use, email hostcalmly@gmail.com with the page address and what happened. We'll reply, and tell you when it's fixed.

Wrong facts and broken links go through the corrections process.

Privacy · Terms · Editorial policy