Skip to main content
Disclaimer: This software is for radiation protection education, screening calculations, and professional support only. It does not replace qualified health physicist judgment, regulatory requirements, approved procedures, emergency response tools, or formal shielding design review. Exposure, absorbed dose, equivalent dose, and effective dose are distinct quantities; do not equate R and Sv without explicit context and assumptions.

Accessibility

HPCalc targets Section 508 / WCAG AA practices but is not formally certified 508 compliant. The app aims for a Section 508 / WCAG 2.1 Level AA baseline for contrast, keyboard access, and form labeling. This page describes what that means today—not a certification of full federal 508 conformance.

Contrast and readability

Semantic colors (background, card, foreground, warning, danger, success) are tuned so body text and disclaimers stay readable in light and dark themes. Charts use CSS variables for axes, grid lines, and tooltips so they track the active theme.

If any screen still feels low-contrast, note the page URL and theme mode when you report it (see the reporting section below).

Keyboard navigation

Use Tab and Shift+Tab to move between links, buttons, and fields. Buttons and theme toggles show a visible focus ring. Calculator hubs and cards are regular links so they participate in standard tab order.

Forms and labels

Workspace inputs use visible labels or accessible names (including fieldset legends for grouped controls such as nuclide pickers). Required documentation fields pair text with export readiness messaging—not color alone.

Reports and print

On-screen reports use theme tokens; print uses a light palette for legible hardcopy. Use the browser print preview before relying on printed output.

Known limitations

HPCalc has not completed a formal third-party Section 508 audit, VPAT, or ACR. Automated contrast checks cover selected semantic pairs only; they do not replace manual review of every view state.

How to report accessibility issues

Open an issue in the project repository with “accessibility” in the title, include the URL, browser and OS, theme (light/dark), and steps to reproduce. Link to the detailed accessibility baseline and manual checklists if helpful.