Accessibility Statement

Our commitment

Every page on shieldstack.pro is built and tested to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That is the standard most accessibility laws point to, including the Americans with Disabilities Act (ADA) in the US, the Equality Act 2010 in the UK, and the European Accessibility Act in the EU.

If we cannot stand by the standard on our own marketing site, we have no business auditing yours.

How we test

On every release, before deploy:

• Automated axe-core scans across each page on the latest build.
• A line-by-line review of the source that renders each page: semantic structure, names and roles, form labels, color values, focus handling and keyboard operability.
• Color contrast verified against the 4.5:1 ratio for normal text and 3:1 for large text and UI components.

Periodically, and on significant changes, we add a full manual pass: keyboard-only navigation end to end, VoiceOver on Safari, and NVDA on Firefox. We do not claim to run the full manual screen reader pass on every single release, and we say so plainly.

Known limitations

We publish our own audit in full, findings and all, at shieldstack.pro/sample. As of 15 June 2026: zero critical, zero serious, no open violations. The one moderate flag we were tracking, the hero badges, did not reproduce on the VoiceOver pass. NVDA testing on Windows is now in place: in June 2026 shieldstack.pro had an NVDA pass on Firefox (structure, headings, and landmarks), alongside the VoiceOver pass on Safari. Minor and advisory items are tracked openly there.

Feedback

If anything on this site is not working for you, please tell us. We treat accessibility reports as priority bugs and aim to respond within 2 business days.

Email hello@shieldstack.pro with the page URL, what you were trying to do, and what broke. Screen reader, browser, and assistive tech details help us reproduce faster.

Verify it yourself

Run any page on shieldstack.pro through our own free quick scan at shieldstack.pro/scan to see the results live. If you find a real WCAG 2.2 AA failure we missed, email it to the address above and we will fix it and credit you on this page.