Accessibility statement

Our commitment

Tombstone exists to give people control over their own data. That is worth very little if the tool itself is unusable with a screen reader or a keyboard. We aim to meet WCAG 2.2 Level AA. We are not claiming full conformance: this is a small graduate project with no formal audit behind it, so the list below is what we have actually built and actually tested, not a certificate.

What is in place today

• A skip to main content link is the first thing keyboard focus reaches on every page.
• Every page uses real landmarks: header, nav, main, footer. Where more than one navigation exists on a page, each one is labeled so a screen reader can tell them apart.
• The current page is marked with aria-current, so being "on" a tab is announced and not just shown in a different color.
• Keyboard focus is always visible. Focus rings appear for keyboard users and stay out of the way for mouse users.
• Every form control has a real label. Placeholder text is never the only name for a field.
• Dialogs use role="dialog" with aria-modal and a labeled heading. Tabbed panels use proper tab semantics.
• Results that appear after a breach check are announced through a live region rather than changing silently.
• Decorative icons are hidden from assistive technology. Icon-only buttons carry text labels.
• Every graphic carries the right alternative text. The brand logo is marked decorative because the link around it is already named, and all other graphics are inline SVG, either hidden from assistive technology or labeled.
• Motion respects prefers-reduced-motion: card animations and spinners stop when your system asks them to.
• The page language is declared, text resizes with browser zoom, and layouts reflow down to a 320px viewport.

Known gaps

We would rather tell you than have you discover these:

• No dark mode. The app renders in a single light theme regardless of your system setting.
• The accounts table is dense. On a narrow screen it scrolls horizontally, and at high zoom levels it is harder to scan than the rest of the app.
• No formal audit. Nothing here has been checked by a third-party accessibility assessor. Our testing is keyboard navigation, browser zoom, and screen-reader spot checks.
• Third-party screens are outside our control. The Google sign-in and permission screens are served by Google, not by us.

If something blocks you

Email accessibility@tombstonepro.com and tell us what you were trying to do, what got in the way, and what you were using (browser, screen reader, magnifier). We aim to reply within five working days.

If an accessibility barrier is stopping you from finishing something in the app, say so in that email. We will walk you through the task another way rather than leave you stuck waiting on a fix.

How this statement is maintained

We review it whenever the interface changes in a way that affects any item above, and at minimum alongside each significant release. The date at the top is the last review, not the last edit to the site.