Our commitment: Origentum is committed to making our website and products accessible to all users, including people with disabilities. We are actively working to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and will continue to improve accessibility over time.
1. Conformance Status
✅ Target Standard: Web Content Accessibility Guidelines (WCAG) 2.1 Level AA
Current Status: Partially conformant — most criteria are met; known limitations are described in Section 4 below.
Assessed by: Internal review, March 2026.
Origentum's primary public-facing interfaces include the order/checkout form, product sample pages, and informational pages (About, Blog). This statement covers all of these properties.
2. Technical Specifications
Our website relies on the following technologies for accessibility:
- HTML5 semantic markup
- CSS3 for visual presentation (all layout and color separate from content)
- Vanilla JavaScript (ES5-compatible) for interactive elements
- ARIA landmark roles and labels where applicable
Our web properties are designed to be compatible with the following assistive technologies:
- Screen readers: NVDA (Windows), VoiceOver (macOS and iOS), TalkBack (Android)
- Keyboard-only navigation
- Browser zoom up to 200% without loss of content or functionality
- High-contrast display modes
3. Accessibility Features
Order / Checkout Form
| Feature |
Status |
Notes |
| Keyboard navigation |
Supported |
All form controls reachable via Tab key; logical focus order follows visual flow |
| Form labels |
Supported |
All input fields have associated label elements; required fields marked with asterisk and announced to screen readers |
| Error messages |
Supported |
Inline validation errors appear adjacent to each field; errors described in text, not color alone |
| Color contrast |
Supported |
Body text (#2a2a2a on #f9f6f1): ratio ≥ 7:1. Gold accent on dark: ratio ≥ 4.5:1. All text passes WCAG AA minimum. |
| Font sizing |
Supported |
Base font 16px minimum; scalable with browser zoom; no text rendered in images |
| Focus indicators |
Supported |
Visible focus ring on all interactive elements; not suppressed |
| Product selection cards |
Supported |
Cards use checkbox inputs with visible labels; selection state indicated in text and visual styling |
| Success and error screens |
Supported |
Confirmation and error messages are visible text; not reliant on color alone |
| GEDCOM file upload |
Partial |
Standard file input element — accessible to most assistive technologies. See known limitations in Section 4. |
| Responsive / mobile |
Supported |
Form is fully responsive; touch targets sized appropriately for mobile use |
Informational Pages and Blog
- Pages use semantic heading hierarchy (H1 → H2 → H3)
- Paragraphs and lists use standard HTML elements
- All links have descriptive text (no "click here" links)
- Images include descriptive alt text
- Pages are readable without CSS enabled
4. Known Limitations
Disclosure: The following limitations are known. We are working to address them in upcoming releases.
-
GEDCOM file upload feedback: When a GEDCOM (.ged) file is uploaded, the form displays a visual confirmation (file name and record count). This confirmation may not be fully announced by all screen readers without additional ARIA live region support. Workaround: the file input itself is keyboard-accessible and the form will proceed correctly even if the confirmation message is not read aloud.
-
Dynamically shown form sections: When selecting a product, additional detail fields appear. These dynamic sections use standard DOM show/hide and may not be announced by all screen readers in all configurations. All required fields in these sections are labeled and validated; keyboard users can Tab through them normally.
-
PDF product delivery: Documents delivered as PDFs may not be fully accessible to all screen readers depending on how they are generated. We recommend opening delivered documents in a modern PDF reader (Adobe Acrobat, Preview, or a browser-native PDF viewer). If you need an accessible alternative format, please contact us.
-
Google Docs delivery: Documents delivered as Google Doc links are rendered by Google Workspace, whose accessibility is governed by Google. Google Docs has robust screen reader support via ARIA; however, Origentum does not control the Google Docs interface.
5. Feedback and Contact
We welcome feedback on the accessibility of Origentum's website and products. If you encounter a barrier, please let us know:
- Email: Info@Origentum.com
- Subject line suggested: Accessibility Feedback
- Response time: We aim to respond to accessibility concerns within 5 business days.
When contacting us, please include:
- A description of the accessibility barrier you encountered
- The page or feature where the issue occurred
- The assistive technology and browser you were using (if known)
We will work with you to provide the information or functionality you need through an alternative method of access while we address the issue.
6. Formal Complaints
If you are not satisfied with our response to your accessibility concern, you have the right to contact a relevant oversight body:
- U.S. residents: The U.S. Department of Justice Civil Rights Division handles complaints related to web accessibility under the Americans with Disabilities Act (ADA).
- EU/UK residents: You may contact your national accessibility enforcement body. In the EU, this is typically the national authority responsible for implementing the European Accessibility Act.
7. Ongoing Efforts
Origentum is a small business committed to improving accessibility as we grow. Our current and planned efforts include:
- Testing new features with keyboard-only navigation and screen reader software before release
- Reviewing color contrast ratios for all new design elements against WCAG 2.1 AA criteria
- Adding ARIA live regions to dynamic form sections to improve screen reader announcements
- Ensuring delivered document formats meet accessibility guidelines to the extent we can control
- Conducting a full third-party accessibility audit as our web presence expands
8. Changes to This Statement
We will update this Accessibility Statement as we make improvements to our site, address known limitations, or complete formal accessibility reviews. The "Last Updated" date at the top of this page reflects when the statement was most recently revised.