Accessibility

What we have measured, and what we have not

We have not commissioned an independent audit, and we do not claim a conformance level we have not had tested. What follows is what was actually checked, by whom, and what is still unverified.

This website

Every page was measured in a headless browser while this site was being written. Two of those measurements — the single h1 per page, and the absence of JavaScript — are re-checked on every build by the project’s own gate. The rest were true when measured, and nothing automatic would catch a regression, which is worth knowing before you rely on them:

  • One h1 and one main landmark per page, with no skipped heading level
  • Every text colour at or above the WCAG 2.2 AA contrast minimum against its composited background
  • Every image carrying alternative text that describes what is on the screen
  • A working skip link, and a visible focus indicator on every interactive element
  • No horizontal scrolling at 390 pixels wide
  • No JavaScript at all, so nothing depends on it — the navigation and the FAQ are native disclosure elements

What has not been done: testing with a screen reader by somebody who uses one, testing with speech input or a switch device, and an independent audit.

The app itself

WarrantySync is built with Atlassian’s UI Kit, so it inherits Atlassian’s own component accessibility and follows your Jira theme in both light and dark appearance. On top of that, and checked against the running app:

  • Every form control is programmatically labelled — an earlier version had thirteen labels pointing at ids no control declared, and that is why every control now goes through one shared component
  • Every reason a control is unavailable is rendered as visible text, never as a tooltip on a disabled button, because a disabled control is neither hoverable nor focusable
  • The status tiles read their label before their count, so a screen reader announces “Expired, 33, button” rather than “33, button”
  • No surface renders its own page heading, because Jira already renders one and the page would otherwise have two

What has not been done: a full audit against WCAG 2.2 AA, and a VPAT. If you need either for a procurement process, ask and we will tell you honestly where we are.

If something here is inaccessible to you, please tell us. Write to support@itsm-ltd.com with what you were trying to do and what happened. A report about the site or the app is treated the same way as a defect, because it is one.

Find out what is out of warranty before somebody else does

It installs with no credentials and counts your estate on the first run, so you know the size of the problem before anybody has to request API access. It is free, and there is no licence check to fail.