Do audits support webhooks and async polling?

Yes. Create audits with POST /audit, poll with GET /audit/{job_id}, or register webhooks at POST /webhooks. Webhooks are HMAC-SHA256 signed.

Yes. Vertaa provides a public REST API with OpenAPI spec plus JS/TS and Python SDK scaffolds. See /developer-docs for quickstarts.

How do I handle rate limits?

On 429, respect Retry-After and backoff; SDKs include retry helpers. Check GET /quota for plan limits before bulk runs.

Accessibility Statement

Last updated: 1 December 2025

Vertaa (operated by Digitaltableteur) is committed to providing a product and web experience that is accessible to the widest possible audience, regardless of ability. We continually improve the user experience for all visitors and apply relevant accessibility standards.

Conformance status

This website is designed to conform with WCAG 2.1 Level AA. Current status: partially conformant. Some areas may not yet fully meet all criteria; we are actively addressing remaining gaps.

Measures we take

Regular automated and manual accessibility testing
Keyboard-first navigation checks and focus management
Color-contrast validation and non-color cues
Semantic HTML with ARIA where appropriate
Ongoing training for design and engineering teams
Periodic third-party reviews of key flows

Current conformance target

We target WCAG 2.1 level AA for our marketing site and product UI. Some areas may still be in progress; we track and prioritize fixes as part of our regular release cycle.

Feedback and contact

If you encounter any accessibility barriers, need content in an alternative format, or have suggestions, please contact us at support@vertaaux.ai. We will respond as soon as possible and work to address the issue.

Technical specifications

HTML5 semantic structure
CSS3 for responsive presentation
JavaScript with WAI-ARIA 1.2 patterns for interactive components

Compatibility with assistive technology

Designed for modern browsers (Chrome, Firefox, Safari, Edge) and common assistive tech (NVDA, JAWS, VoiceOver) with keyboard-only navigation support. Older browsers or AT may have reduced functionality.

Known limitations

Some third-party embeds (e.g., maps, videos) may lack full accessibility; alternatives provided where possible.
Older PDFs may not meet current standards; remediation is ongoing.
Some complex interactive components may need improved focus order or announcements.
Dynamically loaded content may not always announce changes immediately to screen readers.

We actively work to resolve these issues. Please report any barriers you encounter.

Assessment and testing

We assess accessibility through automated scans (axe-core, Lighthouse where applicable), manual keyboard testing, screen reader checks (NVDA, VoiceOver), and periodic external reviews. This statement was last reviewed on 1 December 2025.

Alternative access

If you cannot access certain content or features, contact us and we will provide the information in an alternative format or assist you directly.

Assistive technology

We test with screen readers (VoiceOver, NVDA), keyboard-only flows, and common browsers. If you use a specific assistive technology and encounter issues, let us know so we can prioritize compatibility.

Ongoing improvements

Accessibility is an ongoing effort. We maintain a backlog of fixes and improvements, and integrate checks into QA (automated audits and manual verification) before releases.