Trust Center · Accessibility
For everyone who uses orengen.io, and for buyers who need our accessibility position: we build this site to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That's a target, not a claim of conformance. This page covers what the target means, the design rules we build to, and how to report a barrier.
Target: WCAG 2.2 Level AA
Conformance: not claimed
The target
WCAG is the W3C's standard for accessible web content, and Level AA is the level most often referenced in accessibility regulations and procurement requirements. Its success criteria sit under four principles.
Text alternatives for images, captions for audio and video, and enough contrast to read text against its background.
Everything works from a keyboard, focus stays visible and isn't completely hidden behind other content, and controls are big enough to hit.
Clear labels and instructions, navigation that behaves predictably, and error messages that say what went wrong and how to fix it.
Standard, well-formed markup, so screen readers and other assistive technology can interpret each page correctly.
WCAG 2.2 added criteria aimed at forms, sign-in and small screens. A focused element can't be completely hidden by a sticky header. Targets need to be at least 24 by 24 pixels. Anything done by dragging needs a simpler alternative. Help appears in the same place from page to page. People aren't asked to re-enter information they've already given. And signing in doesn't require solving a puzzle or remembering something unless there's another way to do it.
In the build
These rules are part of the design system every page uses. They make AA easier to reach; they don't replace testing.
Our brand orange isn't used for small text on navy, where it falls short of AA contrast. Dark backgrounds use a lighter orange tint, and orange buttons use a deeper ember fill so white labels stay readable.
Buttons and links in our design system show a 3-pixel focus outline, so anyone navigating by keyboard can see where they are on the page.
Buttons in page content are at least 48 pixels tall, and links in page content get a 44-pixel touch height. The header buttons are at least 44 pixels tall, and the footer links are 32 pixels, all above the 24-pixel minimum in WCAG 2.2.
Body copy is set at 16 pixels or larger with generous line spacing, and multi-column layouts reflow to a single column on small screens.
Our page rules call for a single H1 and headings in sequence, so screen-reader users can move through a page section by section.
Each page opens with one or two plain sentences on what it offers and who it's for, so nobody has to read the whole page to find out whether it's relevant.
Conformance
Design rules are a starting point. Conformance is shown by testing: automated checks, a manual review against each success criterion, and real use with screen readers, keyboard-only navigation and zoom. We haven't published an evaluation of this site, so we don't state a conformance level.
Some pages we link to run on other platforms, including the booking pages and the sign-in applications. Their accessibility depends on those platforms. If you meet a barrier there, report it the same way and tell us which page you were on.
Report a barrier
If something on this site is hard or impossible to use the way you browse, we want to know, including problems this page doesn't mention. You don't need to tell us about any disability or health condition to report one.
Where: the page address, or the page name if you don't have it.
What happened: what you were trying to do, and what stopped you.
Your setup, if you're comfortable sharing it: browser, device, and any assistive technology such as a screen reader, magnifier or voice control.
How to reply: the email address or phone number you'd like us to use.
Contact form: start your message with the word Accessibility.
Email: support@orengen.io
Phone: 833-ORENGEN (833-673-6436)
Tell us if you need a page's content in another format, such as plain text.
Related
Security, privacy, responsible AI, compliance and credentials in one place.
Trust Center →How we govern our own use of AI, including disclosure in communications and human review.
Responsible AI →Mission Brief
Bring your requirements, including any accessibility standard your organization or contracts name, and we'll work through what they mean for the build.
