Accessibility statement

Pyrenth is built so a wide range of people can actually use it. A clinician with shaky hands at the end of a long shift. A billing staffer on a screen reader. A supervisor squinting at a chart from two feet back. A patient on their phone in a clinic waiting room. We design for them, not for a perfect twenty five year old with a 27 inch monitor.

What we follow

Pyrenth meets the Web Content Accessibility Guidelines version 2.1 at Level AA. We also follow the US Section 508 Revised 2017 rules for software and documentation, and we informally track the European EN 301 549 V3.2.1 standard so we are ready when a customer asks.

What that looks like in the app

• Body text is at least 14 point with extra line spacing. Older staff and users with low vision are who we design for first.
• Everything you can click you can also reach with the keyboard. The focus ring is visible on light and dark backgrounds.
• Every tap target is at least 44 by 44 pixels, so a finger or a stylus does not miss.
• Color never carries information by itself. If something is critical, it also has an icon and a word, so a colorblind user never has to guess.
• Every form field has a real label, not just a placeholder. When a field is wrong, the screen reader actually says so.
• Pages use real HTML headings and landmarks so a screen reader can jump to the part you want.

The VPAT for procurement

For federal procurement and for any enterprise vendor review, we keep a current VPAT 2.5 Accessibility Conformance Report on file. Email accessibility@pyrenth.app and we will send it.

When something is broken

If something blocks you from doing your job in Pyrenth, tell us. Email accessibility@pyrenth.app or call (602) 622-4077. We reply within five business days, and for anything that stops work we target a fix or a workaround within thirty days.