Accessibility Statement

1. Our commitment

Digital Empire Holdings LLC is committed to making EntryProof usable by everyone, including people who use screen readers, keyboard-only navigation, or browser zoom/high-contrast modes. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA , a target we actively work toward, not a certification claim.

2. Testing methodology

Automated: axe-core and Lighthouse accessibility audits on every page template on template changes, targeting a Lighthouse a11y score of 90+ (Google Perfection Standard v2 §11 floor).
Manual: keyboard-only walkthroughs on every new interactive tool (the readiness checker, checkout flow) before it ships.
Structural checks: exactly one <h1>, no skipped heading levels, skip-to-main-content link, landmark regions on every page.

3. Known limitations (as of August 13, 2026)

The readiness-checker's multi-step gap breakdown does not yet expose a full screen-reader table summary (scope attributes inconsistent across older components).
Platform-specific integration guides ([platform] route) have not each been through a dedicated manual keyboard pass, only the shared template has.
Third-party embeds (Stripe Checkout, once paid tiers ship) are excluded from our own testing scope per WCAG's third-party-content carve-out.

None of the above block core task completion (running the checker, reading results, requesting the full report) with a keyboard or screen reader.

4. Ongoing improvement

Re-audited on every template change and at least quarterly (tied to Standard v2 §15, next scheduled 2026-11-11). Regressions are fixed before further content ships on the affected template.

5. Date of last audit

Last full manual + automated pass: 2026-08-09 (Golf-Claude-Portion 2026-08-09 a11y sweep). This statement published August 13, 2026.

6. Report an accessibility issue

Email hello@citationsafe.com with the page URL, assistive technology/browser used, and what happened. We aim to acknowledge within 2 business days.

8. Conformance by WCAG principle

Perceivable: text alternatives on informative images, sufficient color contrast on primary templates (automated-audited per Section 2), and content that does not rely on color alone -- severity/status indicators pair color with a text label, not color alone.
Operable: full keyboard operability on the readiness checker; visible focus indicators; a skip-to-main-content link as the first focusable element on every page; no content that flashes more than three times per second.
Understandable: consistent navigation and labeling across every page; form fields with real <label> elements, not placeholder-only labels; error messages that state what went wrong in plain language.
Robust: semantic HTML landmarks (header/main/footer/nav) and valid markup assistive technology can parse reliably, verified via the axe-core automated pass in Section 2.

9. Assistive technology we test with

Manual keyboard-only walkthroughs (Section 2) are run in Chrome and Safari on macOS. We do not yet run a dedicated screen-reader (VoiceOver/NVDA/JAWS) pass on every release -- a real gap, listed honestly in Section 3 rather than glossed over, and the top item on our next accessibility improvement pass.

11. Roadmap

Next up, in priority order: a dedicated VoiceOver pass on the readiness checker (targeting Q4 2026), full scope-attribute coverage on results tables, and a written conformance report we can share directly with Enterprise customers' own accessibility/procurement teams on request. We update this section honestly as items land.

12. Why this matters for EntryProof specifically

EntryProof exists to help sellers meet a hard regulatory deadline. A tool that's inaccessible to a keyboard-only or screen-reader user isn't just a UX gap, it's a barrier between that person and a compliance deadline that doesn't care whether the tool worked for them. That's why we treat accessibility defects on the core task flow as fix-fast issues, not backlog items.

13. How we scope a conformance check

A "WCAG 2.1 AA conformance check" can mean very different things depending on how thorough it is. Ours combines the W3C's own Accessibility Conformance Testing (ACT) rules where an automated rule exists, manual review against the remaining criteria using the methodology in the W3C's Easy Checks guide, and the keyboard spot checks described in Section 2. We do not claim a formal third-party VPAT audit has been performed, if an Enterprise customer's procurement process requires one, email hello@citationsafe.com and we'll scope what's realistic.

14. Mobile and responsive accessibility

the readiness checker is built mobile-first with a 390px minimum viewport target, tap targets sized at least 44×44px, and no horizontal scroll on any screen size we test against. Pinch-to-zoom is never disabled, some sites block zoom to protect a fragile layout; ours doesn't need to.

15. Feedback shapes the roadmap

Every accessibility report we receive (Section 6) directly informs Section 13's roadmap ordering, a barrier that blocks someone from finishing the readiness checker jumps ahead of a cosmetic contrast tweak, every time. We would rather hear about a real problem from a real user than wait for our own quarterly audit to catch it.

15. Related pages

Digital Empire Holdings LLC, 30 N Gould St Ste N, Sheridan WY 82801