1. Introduction
ORDENTRA is committed to making the ORDENTRA platform, our websites, and our support materials usable by everyone, including people who rely on assistive technologies, people with temporary impairments, and people in constrained environments such as noisy warehouses or bright loading docks. Accessibility is a product requirement at ORDENTRA, not a feature — we track it in the same cadence as performance, security, and reliability.
This statement describes our conformance target, the assistive technologies we support, the accessibility features of the product, the limitations we know about, and how to reach us if you encounter a barrier. It applies to ordentra.com, the ORDENTRA web application, our documentation, and our help-center content. It is reviewed every six months and updated whenever the scope of conformance changes.
2. Standards conformance
ORDENTRA targets conformance with the Web Content Accessibility Guidelines (WCAG) version 2.2 at Level AA, published by the W3C Web Accessibility Initiative. Level AA is the globally recognized benchmark for enterprise software and forms the basis of most national and sectoral accessibility regulations.
- WCAG 2.2 Level AA — primary standard for the web application and marketing website. Substantial conformance as of the last audit, with the limitations described in Section 5.
- EN 301 549 v3.2.1 — European harmonized standard that incorporates WCAG 2.1 AA for ICT products and services. Used for European public sector procurement under the Web Accessibility Directive (Directive (EU) 2016/2102).
- US Section 508 (Revised Section 508) — applicable to procurement by US federal agencies.ORDENTRA publishes an Accessibility Conformance Report (ACR) using the ITI VPAT® 2.5 template; the current report is available on request from accessibility@ordentra.com.
- European Accessibility Act (Directive (EU) 2019/882) — applicable to in-scope services from 28 June 2025. We have assessed our exposure and maintain a tracked roadmap of remediations.
3. Supported assistive technologies
We routinely test the ORDENTRA platform with the assistive technologies listed below. Support extends to the latest stable release at the time of testing; older versions will generally work but are not part of our formal support matrix.
- Screen readers — NVDA with Firefox and Chrome on Windows; JAWS with Chrome and Edge on Windows; VoiceOver with Safari on macOS and iOS; TalkBack with Chrome on Android.
- Speech recognition — Dragon NaturallySpeaking on Windows; Voice Control on macOS and iOS.
- Keyboard-only navigation — full support across all supported browsers, including tab, shift-tab, arrow-key, space, and enter for all interactive elements, plus documented keyboard shortcuts for common actions.
- Switch access and alternative pointers — supported through the operating-system switch-control subsystem and through the keyboard interface described above.
- Zoom and text resizing — the interface is usable at 200% browser zoom and with user-agent text resizing, without loss of content or functionality in most surfaces.
- Reduced motion and high contrast — we honor the operating-system
prefers-reduced-motionandprefers-contrastmedia queries. A dedicated high-contrast theme is planned for Q3 2026.
4. Accessibility features by product area
The following sections summarize accessibility features in the main product areas. Each area is tested against WCAG 2.2 AA before release and has a named engineering owner accountable for its accessibility posture.
Dashboard and navigation
- Semantic landmark structure with a single main heading per view.
- Skip-to-content link on every page and persistent focus ring on interactive elements.
- Full keyboard navigation with logical tab order, including for the command palette and date pickers.
- Minimum 4.5:1 contrast ratio for body text and 3:1 for large text, verified by automated tooling on every release.
Reports and data tables
- All tables use proper <caption>, <thead>, and <scope> markup so screen readers can announce row and column headers.
- Sort and filter controls expose their current state through aria-sort and aria-pressed attributes.
- Charts include an accessible text alternative and a toggleable data-table view for screen-reader users.
- Numeric data is announced with locale-aware formatting (thousands separators, currency symbols) rather than raw digits.
Procurement flows
- Multi-step forms use fieldset and legend to group related fields and expose progress through aria-current.
- Inline validation errors are announced via live regions without moving focus away from the current field.
- Required fields are programmatically indicated with both aria-required and a visible marker that does not rely on color alone.
- Document uploads expose file name, size, and status updates to assistive technology as they progress.
Approvals and notifications
- Notifications use aria-live regions tuned to the urgency of the event, so screen-reader users are not interrupted unnecessarily.
- Approval actions can be completed entirely from the keyboard, including bulk approvals from the inbox view.
- Time-sensitive prompts (such as two-factor authentication) include an accessible countdown and a request-more-time action.
- Email and in-product notifications include plain-text equivalents and meaningful subject lines.
Settings and administration
- All settings pages follow a consistent structure so assistive technology users can rely on learned patterns.
- Color is never the sole signal for state; icons, text labels, and aria attributes always accompany it.
- Destructive actions require confirmation with a dialog that traps focus and restores it on close.
- A high-contrast theme is planned for Q3 2026 and is being tested with low-vision users.
5. Known limitations and workarounds
Despite our best efforts, some areas of the product do not yet fully meet our WCAG 2.2 AA target. We publish this list transparently so customers can plan, and so the engineering teams responsible can be held accountable. Each item has a planned remediation quarter.
Complex pivot tables in legacy reports
A handful of legacy pivot-style reports render with custom grid markup rather than a semantic table, so screen readers announce the structure imperfectly.
- Workaround
- Users can export the underlying data to CSV or open an accessible data-table view from the report toolbar.
- Planned fix
- Q3 2026 — migration of all legacy reports to the v2 table primitive.
Drag-and-drop reordering in the workflow builder
The workflow builder uses pointer-based drag-and-drop, which is difficult to operate with keyboard or switch devices.
- Workaround
- A keyboard-accessible 'Move up' and 'Move down' action is available in the context menu for each workflow step.
- Planned fix
- Q2 2026 — native keyboard drag-and-drop shipping with the workflow builder v3.
PDF exports from older report templates
Some of our older PDF templates do not include tagged PDF structure, so the reading order in assistive technology is not fully predictable.
- Workaround
- Users can request an accessible HTML or CSV version of the same report through the 'Download as' menu.
- Planned fix
- Q2 2026 — full migration to tagged PDFs generated from the v2 report engine.
Live chat widget
Our third-party chat widget does not expose all of its controls to screen readers and cannot be fully operated with a keyboard.
- Workaround
- Users can contact support directly at support@ordentra.com or through an in-product ticket form that is fully accessible.
- Planned fix
- Q3 2026 — replacement of the third-party widget with a first-party accessible chat component.
Video content without transcripts
A small number of older product videos on our marketing site and documentation do not yet have full transcripts or captions in all supported languages.
- Workaround
- Every video has an English transcript; translations and captions in other languages are being added.
- Planned fix
- Q2 2026 — captions in English, French, German, Dutch, and Spanish across the entire library.
6. How we test accessibility
Accessibility testing at ORDENTRA uses a four-layer approach, combining automated scanning, manual expert review, third-party audit, and usability testing with people with disabilities. Each layer catches different categories of defect, and no single layer is treated as sufficient on its own.
- Automated tooling — axe-core, Pa11y, and Lighthouse run on every pull request and block merges that introduce new violations. We supplement these with custom rules that cover ORDENTRA-specific components such as the command palette, date pickers, and data grids.
- Manual expert review — our in-house accessibility specialists review every material UI change against the WCAG 2.2 success criteria before it ships. Reviews include keyboard-only testing, screen-reader walkthroughs, and color-contrast checks on real content.
- Third-party audits — we engage an independent accessibility firm (Deque Systems, Inc.) twice a year to conduct a full WCAG 2.2 AA audit and produce a public-facing conformance summary. The most recent audit was completed in March 2026; the next audit is scheduled for October 2026.
- Usability testing with people with disabilities — at least once per quarter, we run moderated usability sessions with participants recruited through an accessible research panel, covering screen-reader, low-vision, motor, and cognitive use cases. The findings are tracked in the same backlog as other product work and have named owners.
7. Feedback and contact
If you encounter an accessibility barrier, need content in an alternative format, or would like to provide feedback on our accessibility work, please get in touch. Every email to the address below goes directly to our accessibility team, and we acknowledge receipt within one business day.
Our accessibility team sits within the platform engineering organization and is led by our Head of Inclusive Design. They own the roadmap, the audit schedule, and the response SLA.
Response SLA: acknowledgment within one business day, substantive response within five business days, and a remediation plan within twenty business days for any confirmed issue.
Attn: Accessibility Team
Herengracht 412
1017 BZ Amsterdam
Netherlands
Requests for alternative formats — including large-print documents, accessible PDFs, plain-text transcripts, or alternative presentation of data — are fulfilled at no cost to the requester. If you need urgent support while using the product, call your customer success manager or contact support@ordentra.com and note that you need accessibility assistance.
8. Formal complaint process and regulatory bodies
If our accessibility team is unable to resolve your concern to your satisfaction, you may escalate to the appropriate regulatory body in your jurisdiction. We will cooperate fully with any investigation and will provide the information required to close out a complaint.
- European Union — under the Web Accessibility Directive (Directive (EU) 2016/2102) and the European Accessibility Act (Directive (EU) 2019/882), each Member State designates a national enforcement authority. For users in the Netherlands, this is the College voor de Rechten van de Mens (Netherlands Institute for Human Rights).
- United Kingdom — complaints relating to services subject to the Public Sector Bodies Accessibility Regulations 2018 can be escalated to the Equality and Human Rights Commission (EHRC) or, in Northern Ireland, the Equality Commission for Northern Ireland.
- United States— US federal employees and individuals procuring from federal agencies may raise complaints under Section 508 of the Rehabilitation Act with the agency's Section 508 coordinator. Complaints under the Americans with Disabilities Act (ADA) may be filed with the US Department of Justice.
- Other jurisdictions — users outside the EU, UK, and US can contact the accessibility or human rights regulator in their country; our accessibility team can help identify the correct body on request.
9. Page-specific accessibility notes
This page itself was built to the same standards we apply to the product. It has a single H1, a hierarchical heading structure, proper landmark roles, a sticky table of contents that is keyboard-navigable, and sufficient contrast for all text and interactive elements. The disclaimer banner at the top of the page uses an amber color purely for emphasis; the meaning is conveyed by the badge label and by the text next to it, so the banner does not rely on color alone.
The last automated and manual audit of the Accessibility Statement page was completed in March 2026. No outstanding WCAG 2.2 AA issues are known for this page at the time of publication. If you encounter a problem with this page specifically, please email accessibility@ordentra.com with the word “statement” in the subject line so it routes correctly.