Our target. Qvert aims to design public websites and supported product interfaces toward WCAG 2.2 Level AA. This is an engineering target, not a claim that every current page, prototype, or pre-release product has completed formal conformance testing.
1. Approach
Qvert works to support keyboard navigation, visible focus, semantic structure, sufficient contrast, meaningful labels, adaptable layouts, reduced-motion preferences, and compatibility with common assistive technologies. Accessibility is considered during design, implementation, and QA as products mature.
2. Product maturity
The Qvert catalog includes released, preview, prototype, and development-stage products. Accessibility coverage may differ by product, operating system, browser, embedded third-party component, and release stage. A product listing will not claim accessibility certification unless that product has been specifically engineered and tested for the stated scenarios.
3. Known limitations
Complex diagrams, canvas-based visualizations, dense technical tables, terminal output, third-party authentication windows, generated reports, and legacy utilities may require additional alternatives or may not yet expose every relationship to assistive technology. Qvert prioritizes practical alternatives as these areas are identified.
4. Requesting assistance
If a Qvert page, document, installer, extension, or application creates an accessibility barrier, contact jmarshall@qvert.net. Include the product or page, version, operating system, browser or assistive technology, the task you were attempting, and the format or accommodation that would help.
5. Response and remediation
Qvert will review accessibility reports in good faith, provide a reasonable alternative when practical, and prioritize remediation based on impact, product maturity, affected workflow, and available engineering capacity. A separate customer agreement may establish additional accessibility commitments.
6. Third-party content
Some Qvert products integrate storefronts, identity providers, cloud portals, browsers, operating-system controls, or third-party content outside Qvert’s control. Qvert will identify actionable integration barriers but cannot guarantee the accessibility of independent third-party services.
7. Feedback
Accessibility feedback is welcome even when no formal accommodation is required. Reports should avoid credentials, private keys, customer data, or unrelated personal information.