review note
This is a product-specific launch draft, not legal advice. The final live policy should be approved against the current company setup, launch jurisdictions, processor list, pricing model, and enterprise commitments.
1. Our commitment
wrxstack is committed to making Folio usable by as many people as possible, including people who use assistive technology. We treat accessibility as part of product quality rather than an afterthought, and we test for it as part of our release gates.
This draft accessibility statement applies to the Folio platform at portfolio.wrxstack.com, app.portfolio.wrxstack.com, tenant subdomains, and connected custom domains. It must be reviewed and approved before it is treated as the live statement.
2. Conformance target
Our target is conformance with the Web Content Accessibility Guidelines (WCAG) version 2.2 at Level AA. WCAG explains how to make web content more accessible to people with a wide range of disabilities.
Conformance is a target rather than a guarantee. Some user-generated portfolio content is outside our direct control, and we depend on portfolio owners to supply accessible text alternatives for the media they upload.
- Standard: WCAG 2.2, Level AA.
- Scope: the platform user interface, public portfolio themes, and the documents in this legal center.
- Out of scope: third-party embeds and user-supplied media where the owner controls the alternative text.
3. Measures we take
We build accessibility into design and engineering and verify it with automated and manual checks before release.
- Automated accessibility scans run against public and legal pages as part of the test suite, including axe checks at WCAG A and AA tags.
- Semantic structure, landmark regions, skip links, focus management, and visible focus styles are part of the shared chrome.
- Color and contrast, responsive layout down to small viewports, and reduced-motion preferences are considered in the design system.
- Forms expose labels, error messages, and programmatic state for assistive technology.
4. Assistive technology compatibility
We aim to support recent versions of common browsers and assistive technologies. Accessibility depends on the combination of browser, operating system, and assistive technology, so behavior can vary.
- Recent versions of Chrome, Edge, Firefox, and Safari on desktop and mobile.
- Screen readers such as VoiceOver, NVDA, and JAWS, and platform magnification and contrast tools.
- Keyboard-only navigation across interactive controls.
5. Known limitations
Despite our efforts, some content may not yet be fully accessible. We list known limitations honestly and work to resolve them.
- User-uploaded images, audio, video, and documents may lack text alternatives or captions until the portfolio owner adds them.
- Third-party embeds, such as media players or scheduling widgets, follow the accessibility of their provider.
- Complex data visualizations and some rich interactions may need further refinement.
6. Feedback and requesting accommodations
We welcome your feedback on the accessibility of Folio. If you encounter a barrier, or need information in a different format or an accommodation to complete a task, please contact us and we will try to provide what you need.
- Send accessibility feedback and accommodation requests to support@wrxstack.com.
- Include the page URL, the browser and assistive technology you use, and a description of the barrier.
- We aim to acknowledge accessibility requests promptly; final response targets should be confirmed before launch.
7. Formal complaints and escalation
If you contact us about an accessibility barrier and are not satisfied with our response, you may escalate the matter. Depending on where you live, you may also have the right to contact a national enforcement body.
- Escalate an unresolved accessibility concern to legal@wrxstack.com.
- We will document the concern, the steps taken, and the expected timeline for a fix.
8. How we assess accessibility
We assess accessibility through a mix of automated testing, manual review, and self-evaluation against WCAG success criteria. This statement reflects our self-assessment and should be confirmed by an independent review before launch.
- Automated axe scans in the test suite.
- Manual keyboard and screen-reader spot checks of core flows.
- Self-evaluation against WCAG 2.2 AA success criteria.
9. Ongoing review
Accessibility is continuous. We review this statement and our testing as the product changes, as standards evolve, and as we receive feedback. The review date below reflects the most recent update.
10. Contact
Accessibility feedback, accommodation requests, and legal-signoff comments should be sent to support@wrxstack.com. Include the page URL, the browser and assistive technology you use, and a description of the issue.
Review references
Product sources
- lib/legal/content.ts
- tests/e2e/legal-docs.spec.ts
- components/legal/LegalChrome.tsx
- components/legal/LegalDocumentView.tsx