ORYGN LLC ("ORYGN", "we", "us") is committed to making the website at orygn.tech (the "Site") usable by as many people as possible, including people with disabilities. We measure the Site against the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. Accessibility testing is part of the work ORYGN does for clients, so we assess our own site rather than only asserting that it is accessible.
1) Conformance status
WCAG defines how to make web content more accessible to people with disabilities. Conformance is reported using defined terms. The Site is partially conformant with WCAG 2.2 Level AA.
Partially conformant means the Site meets the standard across the areas we have assessed, with the specific exceptions recorded in section 4. We use this term deliberately. Claiming full conformance would require every success criterion to be verified on every page, template, and interaction state, including against assistive technology we have not yet tested. We would rather tell you precisely where the Site stands than claim more than we have measured.
2) How the Site was assessed
Assessment is carried out by a certified DHS Trusted Tester and combines automated checks with manual keyboard and code review, rather than relying on an automated scan alone. The most recent review was completed on September 8, 2026.
Automated testing covered WCAG 2.0, 2.1, and 2.2 Level A and AA across representative page templates, in both the light and dark themes, at desktop and mobile viewport sizes. Manual testing covered keyboard traversal and focus order, focus visibility, heading structure, landmark regions, the bypass-to-content mechanism with scripting both enabled and disabled, the navigation disclosure pattern, and reduced-motion behaviour.
The September 2026 review closed three of the areas previously listed as unassessed. Text contrast over the animated background was measured from the pixels the browser actually paints, sampling the background canvas underneath every run of text on the page in both themes, rather than comparing the two colour values a stylesheet declares. Reflow was checked by rendering every page at a 320 pixel viewport in both themes. Error handling on the contact form was exercised by driving a real failed submission. Each of the three turned up defects, and those are described in section 4 along with what was done about them.
Anything a review turns up is fixed and re-tested rather than logged and deferred. The findings from the most recent review were resolved the same day.
3) What supports accessibility on the Site
The Site is built as semantic HTML with landmark structure and a single top-level heading per page. Every page begins with a keyboard-accessible skip link that moves focus past the navigation; it is present in the served markup, so it does not depend on scripting to work. Interactive controls are reachable and operable by keyboard, including the navigation menus: the top-level item is a link and Enter follows it, Space or Down opens the menu beneath it, expanded state is exposed, and Escape closes it with focus returned to the trigger. Every destination in those menus is also reachable from the mobile navigation. Focus indicators are visible throughout. Images carry text alternatives and decorative graphics are hidden from assistive technology. The animated background stops automatically when the operating system requests reduced motion, and can also be switched off manually.
4) Known limitations and scope of assessment
Third-party components. The bot-protection challenge on our contact form is provided by an external service. We do not control its markup or behaviour and cannot represent that it meets the standard.
The animated background. The background is drawn on a canvas that sits behind the page, so decorative shapes pass under live text. Measuring it found that the drifting asteroid was opaque enough to blank a word as it crossed a line of body copy in the light theme, and that the light theme link colour cleared the AA threshold by so little that any texture behind it pushed it under. Both were corrected. What remains is that an individual star can still land behind a glyph; at its worst that is a run of about five pixels, and it does not obscure the word. The background can be switched off entirely from the header, and it does not start at all when the operating system asks for reduced motion.
Not yet assessed. Our testing has not yet covered output with screen readers such as NVDA, JAWS, or VoiceOver. Browser testing to date has been carried out in current Chromium-based browsers, and not yet in Firefox or Safari.
These areas remain open, and this statement will be updated as they are completed. We list them because an assessment that does not state its scope is not an assessment. If you rely on assistive technology and encounter a barrier that is not described here, we would genuinely like to know.
5) Technical specifications
Accessibility of the Site relies on HTML, CSS, and JavaScript, and on their support in current browsers and assistive technologies. Page structure, content, and the bypass-to-content mechanism do not require JavaScript.
6) Feedback and contact
We welcome your feedback on the accessibility of the Site. If you encounter an accessibility barrier, or if you need any part of the Site provided in a different format, please contact us and we will work to resolve it.
ORYGN LLC
Email: contact@orygn.tech
You can also reach us through our contact form. We aim to respond within a few business days.