Current navigation and structure
Every page has a skip link, one main heading, landmark navigation, ordinary crawlable links and a breadcrumb outside the homepage. Content order remains meaningful without CSS. Calculator choices use native labels and controls; expandable audits and FAQs use native details/summary elements.
Form labels, errors and result updates
Inputs have persistent programmatic labels and supporting instructions. Blocking errors appear in an alert summary with links back to affected fields. Dynamic place suggestions expose combobox/listbox semantics. Successful calculations use a polite live region and move focus to the result; Edit and Reset return focus deliberately.
Exact, approximate and unknown confidence is expressed in text, not color alone. Unknown-time Rising omission and unsupported states use explanatory copy rather than an empty result card.
Keyboard, focus, motion and target size
All current controls are operable without a pointer. Focus indicators are visible, the skip link becomes visible on focus, and buttons/interactive choices are designed around at least 44-by-44 CSS-pixel targets. Reduced-motion preference removes nonessential transition duration and the interface does not require dragging.
Responsive text and visual design
Layouts collapse to one column at narrow widths, tables remain horizontally scrollable rather than clipping content, and action buttons expand on small screens. The build is checked at a 320-pixel viewport and 200 percent zoom. Status meaning is not conveyed by color alone; high-contrast focus and text labels carry the state.
Known limitations and remaining checks
Formal WCAG conformance has not been established. Remaining checks include current desktop and mobile browsers, keyboard-only use, zoom and reflow, forced-colors and high-contrast modes, screen readers on representative browser and operating-system pairs, touch exploration, error recovery and review by people with relevant access needs where feasible.
Accessibility feedback can be sent through the Contact page. Report the affected page and interaction only; do not include birth details.
Accessibility change control
A component or content change must preserve name, role, value, keyboard behavior, focus order, visible focus, error association and reflow. Automated checks can catch structural regressions, but they do not replace manual assistive-technology testing or user feedback.