Accessibility

We want PatchAlert to work for everyone who maintains systems, including people who use screen readers, large text, or reduced motion. Our target for the app and this website is WCAG 2.2 level AA.

What we did and tested

App (Android)

• Automated checks on every screen, run with each build: tap targets of at least 48 by 48, a label on every control, and text contrast, at normal and 200 percent text size.
• State is given in words, never by color alone: overdue, due soon, patched, mitigated, not affected, deferred, ransomware.
• Icon-only buttons say what they do and to what item. Decorative graphics are hidden from screen readers.
• Works at 200 percent text size and with Remove animations turned on (the animations stop).
• TalkBack walkthrough on an Android emulator through the main flow: welcome, status, alerts, alert detail, recording an outcome, products, settings.

Website

• Semantic headings and landmarks, a skip link, alt text on images, visible keyboard focus, and contrast that meets AA.
• An automated check on every page at desktop and phone width, with and without reduced motion: axe for WCAG 2.2 A and AA, contrast measured from the rendered pixels where axe cannot decide, and every image loading.
• The status ring on the home page moves for about 24 seconds and then stops; a Pause animation button stops it sooner. With reduced motion set, the page shows still versions and nothing moves.

Known limits

• The exported PDF report is not a tagged PDF, so screen readers may read it less well. The same figures are on the app's Report screen.
• TalkBack testing was on an emulator, not yet on a range of physical devices.
• Vulnerability text comes from the CISA catalog as published and can be technical.

Report a problem

If something is hard to use, email support@patchalert.app with the subject "Accessibility". Tell us the screen or page, what you were trying to do, and the assistive technology you use if any. We aim to reply within five business days.