Accessibility Statement

Prosigns is committed to making prosigns.io and the products we build accessible to people with disabilities. We design, build, and operate to the standards documented below — and treat accessibility as a release-gate concern, not a backlog item.

This statement covers the public Prosigns website. Engagement-level accessibility commitments for software we build for clients are set in the relevant Statement of Work and reflect the regulatory frame of the deployment jurisdiction (ADA Title III, EN 301 549, Section 508, etc.).

• WCAG 2.2 Level AA. Our target conformance level for prosigns.io. We test against AA criteria continuously and address AAA where it does not introduce trade-offs that harm other users.
• EN 301 549. European harmonized standard, reflecting WCAG 2.1 AA with additional ICT requirements.
• Section 508 (Revised). U.S. federal procurement standard, harmonized with WCAG 2.0 AA.
• ADA Title III. Applied as a guiding principle for U.S. public-facing surfaces.

As of the “Last updated” date above, prosigns.io is assessed as partially conformant with WCAG 2.2 AA. Partially conformant means some content does not yet fully conform to the accessibility standard.

We perform automated accessibility tests in CI on every change, run quarterly manual audits with assistive technology (NVDA, VoiceOver, TalkBack, Dragon NaturallySpeaking), and engage an independent third-party accessibility auditor annually. Audit summaries are available on request under NDA.

We disclose known accessibility limitations transparently. The following are the current open items being remediated:

• Some embedded third-party content (e.g., webinar recordings, podcast embeds) may not yet provide full keyboard and screen-reader support equivalent to our first-party content. Captions and transcripts are provided alongside.
• Decorative imagery is marked appropriately, but a small number of legacy images may have suboptimal alt text. Remediation is ongoing as we replace stock imagery with self-hosted assets.
• Interactive tools (assessments, calculators) are designed for keyboard and screen-reader use, but charting components are still under accessibility refinement.

If you encounter a barrier not listed here, please tell us — see the reporting section below.

• Full keyboard navigation across all content surfaces, with visible focus indicators and consistent skip links.
• Semantic landmark regions and heading hierarchy for screen reader navigation.
• Color contrast meeting AA on body text and AAA on the majority of headlines.
• Form fields with labels, error messages, and aria-describedby associations. The lead form preserves state and announces transitions.
• Reduced-motion preference honored for animation and transitions.
• Text resizing to 200% without loss of content or function.

If you encounter content that is difficult to access, please tell us. We aim to acknowledge within one business day and provide either a remediation plan or an accessible alternative within ten business days.

Email [email protected] with:

• The URL of the page where you encountered the barrier.
• A description of the barrier and the assistive technology used (if any).
• The outcome you were trying to achieve.

You can also reach us through the contact page.

For software we build for clients, our GUARDIAN (quality) and CANVAS (design) departments operate to the same WCAG 2.2 AA target unless the client explicitly contracts to a different standard. We publish an accessibility test report at the close of each release gate, with named issues, severity, and remediation plans. Section 508 and EN 301 549 deliverables are produced when the engagement contracts to those standards.