1. Our commitment
Digital Empire Holdings LLC is committed to making PixelProof usable by everyone, including people who use screen readers, keyboard-only navigation, voice control, or browser zoom/high-contrast modes. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. This is a target we actively work toward, not a certification claim, see Section 3 for where we currently fall short.
2. Testing methodology
- Automated: axe-core and Lighthouse accessibility audits run against every page template on template changes, targeting a Lighthouse accessibility score of 90+ (Google Perfection Standard v2 §11 floor). These catch missing alt text, contrast failures, missing form labels, and heading-order violations.
- Manual: keyboard-only walkthroughs (Tab/Shift+Tab/Enter/Escape, no mouse) on every new interactive tool (the free pixel scanner, checkout flow, account dashboard) before it ships, checking focus order, visible focus indicators, and that no interactive element is a keyboard trap.
- Structural checks on every page: exactly one
<h1>, no skipped heading levels, a skip-to-main-content link as the first focusable element, and landmark regions (header/main/footer/nav).
3. Known limitations (as of August 13, 2026)
We would rather list real gaps than claim a perfection we haven't verified:
- Some data-dense tables (scan-findings breakdowns) do not yet have full screen-reader table summaries (
<caption>/scopeattributes are inconsistent across older components), a screen-reader user can read the data but the relationship between a given cell and its row/column header is not always announced. - The referral/affiliate dashboard's charts are canvas-rendered and do not currently expose an accessible data-table alternative.
- Color contrast has been automated-audited on primary templates but not yet on every promotional banner variant (e.g. seasonal exit-intent coupon styling).
- Third-party embeds (Stripe Checkout) are excluded from our own testing scope per WCAG's own third-party-content carve-out, Stripe publishes its own accessibility conformance separately.
None of the above block core task completion (running a scan, reading a report, subscribing, canceling) with a keyboard or screen reader, they are polish/completeness gaps, not hard blockers, and are logged for the next accessibility pass.
4. Ongoing improvement
Accessibility is re-audited on every template change (Section 2) and the full site gets a fresh manual pass at least quarterly, tied to the Google Perfection Standard v2 §15 quarterly review cycle (next scheduled: 2026-11-11). Regressions found in that review are fixed before further content ships on the affected template, per Standard §11's penalty clause.
5. Date of last audit
Last full manual + automated accessibility pass: 2026-08-09 (Golf-Claude-Portion 2026-08-09 a11y sweep, added the skip-nav link and landmark fixes referenced in Section 2). This statement itself published August 13, 2026.
6. Report an accessibility issue
If you encounter an accessibility barrier using PixelProof, tell us, we want to fix it. Email support@digitalempireholdings.com with the page URL, what assistive technology/browser you were using, and what happened. We aim to acknowledge within 2 business days and will follow the same 24-hour-fix-for-live-errors standard we apply to factual corrections (see our corrections policy) for accessibility defects that block a core task.
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 to convey meaning (severity badges in scan results pair color with text labels, "critical"/"warning"/"info", not color alone).
- Operable: full keyboard operability on the free scanner, checkout, and account dashboard; 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-text-only labels; error messages that state what went wrong in plain language, not a generic "invalid input." - Robust: semantic HTML landmarks (
header/main/footer/nav) and valid markup that assistive technology can parse reliably, verified via the axe-core automated pass described 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, this is a real gap, listed honestly in Section 3 rather than glossed over, and is the top item on our next accessibility improvement pass.
11. Roadmap
Next up, in priority order: a dedicated VoiceOver pass on the free scanner and checkout flow (targeting Q4 2026), full scope-attribute coverage on the scan-findings table, and an accessible data-table fallback for the affiliate dashboard charts. We update this section honestly as items land, a completed item moves out of Section 3's known-limitations list with the date it was fixed, not silently.
12. 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 (roughly 30-40% of WCAG success criteria are reliably automatable), manual review against the remaining criteria using the methodology in the W3C's Easy Checks guide, and the keyboard/screen-reader spot checks described in Section 2. We do not claim a formal third-party VPAT (Voluntary Product Accessibility Template) audit has been performed, if an Enterprise customer's procurement process requires one, email accessibility@argushq.ai and we'll scope what's realistic.
12. Related pages
Digital Empire Holdings LLC, 30 N Gould St Ste N, Sheridan WY 82801