Aiming for WCAG 2.1 Level AA
Progress Portals is working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Where feasible we follow Accessible Rich Internet Applications (ARIA) patterns, use semantic HTML for structure, and ensure the site is navigable by keyboard and usable with screen readers.
Accessibility is an ongoing effort rather than a one-time checklist. As we develop new features, accessibility is part of the review before anything ships.
Our current conformance is based on internal self-evaluation against these guidelines. We have not yet completed an independent third-party audit. When we do, we will update this statement to reflect the results.
Scope of this statement
This statement applies to the public progressportals.io website (marketing pages, pricing, sign-in, and legal documents) and to the authenticated application at progressportals.io/app, including stakeholder portals published at progressportals.io/p/<project>.
Where we currently fall short
We're being upfront about where we know we fall short today:
- Admin console and stakeholder portals: being migrated to our refreshed design system. Until that migration is complete, some interactive components in those surfaces may not fully meet AA.
- Third-party embedded content: video players, 360° viewers, and map tiles inherit the accessibility of their provider. We pick providers that support standard keyboard and screen-reader interaction, but we can't guarantee their conformance.
- User-uploaded content: images, PDFs, and drone footage are the responsibility of the account that uploads them. We surface alt-text and caption fields, but we can't add accessibility to content after the fact.
- Spatial and 360° tools: our interactive 360° walkthrough editor, map georeferencing, and drag-to-compare canvases rely on pointer-driven, visual interactions that are not yet fully operable by keyboard or screen reader. We're working on accessible alternatives. In the meantime, the underlying project data, annotations, reports, and documents, remains available in more accessible formats.
How to report an issue
If something on Progress Portals is difficult or impossible to use because of an accessibility barrier, please tell us. We take these reports seriously and will respond within five business days. If the fix is straightforward we'll ship it quickly; if it's larger we'll tell you what the realistic timeline looks like.
Baselines for our work
We reference open W3C standards as the authoritative baselines for our work. We do not use any proprietary accessibility framework or closed-source scoring tool.