Accessibility Statement

Last audited: 2026-05-10

PrintingPay (operated by Black Asterisk LLC) is committed to making the operator portal at printingpay.com usable by the widest possible audience, including people who rely on assistive technologies. This statement explains the standard we hold ourselves to, the issues we currently know about, and how to reach us when something gets in your way.

1. Conformance target

PrintingPay targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. WCAG 2.2 AA is the operative standard under both the Americans with Disabilities Act (ADA Title III) and the European Accessibility Act (EAA, Directive (EU) 2019/882, in force June 2025).

Where a feature partially conforms today, it is documented under Known issues below with the remediation owner and target date. We treat regressions against this target as defects and ship fixes through the same release process as any other production bug.

2. Measures we take

Automated WCAG 2.2 AA scans (axe-core) run on every pull request across the top admin routes and every public storefront route. Critical and serious findings block merge.
Lighthouse accessibility audits run on the admin app on every pull request with a hard floor of 0.95; the build fails below it.
Manual keyboard-only navigation and screen-reader smoke tests (NVDA + JAWS on Windows, VoiceOver on macOS + iOS, TalkBack on Android) are performed each release.
Color contrast is enforced at the design-token layer; the generic muted-text token meets WCAG 2.2 AA contrast against every surface it is used on.
New components added to packages/ui, packages/storefront-components, and packages/storefront-ui ship with axe coverage before merge.

3. Known issues

We track known accessibility defects in the BA-PWAF audit report (Black Asterisk Production Web Accessibility Floor). The latest report and the per-finding remediation owners live under audits/ in the PrintingPay repository. The most recent audit was completed on 2026-05-10.

Highlights of currently-tracked items as of the 2026-05-10 audit:

A small number of icon-only buttons in operator views still rely on tooltip text; we are migrating them to use aria-label in the same release window.
The Conformance Report (VPAT 2.5) is in preparation under BA-PWAF Wave 1 and will be linked from this statement once published.
A handful of legacy data tables on the analytics surface are being rebuilt to add explicit row + column header semantics.

See the latest BA-PWAF audit at audits/ for the full list, severity classifications, owners, and target dates.

4. Standards beyond WCAG

Where it improves the experience for assistive-technology users, PrintingPay also follows:

WAI-ARIA 1.2 Authoring Practices for composite widgets (combobox, dialog, menu, tabs, tree).
Section 508 as revised in 2017, which incorporates WCAG 2.0 AA by reference and is used for U.S. federal procurement.
EN 301 549 v3.2.1, the European harmonised standard supporting the EAA.

5. Feedback and contact

If you encounter an accessibility barrier on PrintingPay — anything from a missing alt-text to a workflow you cannot complete with a screen reader or keyboard — please tell us. Your report is taken as a bug report and routed to the same engineers who fix production defects.

Email: [email protected]

When you contact us, please include:

The page or feature where the barrier occurred (URL helps).
The assistive technology you were using (browser, screen reader, OS, version) if relevant.
A short description of what happened and what you expected.

6. Response time

We acknowledge every accessibility report at [email protected] within 30 days of receipt. The acknowledgment includes a tracking reference, the engineer assigned, and either a fix target date or a clear next step (for example, a request for more information). Critical barriers that block a user from completing core workflows are escalated and worked the same day.

7. Enforcement procedure (EU users)

EU residents who believe PrintingPay is not meeting the accessibility requirements of the European Accessibility Act may, after contacting us at [email protected] and allowing us a reasonable opportunity to respond, escalate to the national enforcement body designated under EAA Article 14 in their member state.

8. Compatibility

PrintingPay is designed to be compatible with the current and previous major release of the following assistive technologies on modern browsers (latest release of Chrome, Edge, Firefox, and Safari):

NVDA on Windows
JAWS on Windows
VoiceOver on macOS and iOS
TalkBack on Android
Dragon NaturallySpeaking voice control

We do not formally support browsers more than two major releases behind current. Some features may still work but are not part of our automated test matrix.