How does the $12/year ($1/month) price work?

The Starter plan is $12 billed once a year, which works out to $1 per month. It covers 1 website with multi-page scans, weekly re-scans with an email report, the assistive widget, and a hosted accessibility statement. Cancel anytime, with a full refund within 14 days.

Can Accessibility Shield stop me from getting an ADA demand letter?

No tool can promise that. Accessibility Shield helps you find and fix the issues automated scans detect, keep a dated public accessibility statement, and give visitors a direct way to report barriers. Automated testing covers only part of WCAG, so manual checks still matter. We are not a law firm; if you receive a demand letter, talk to a licensed attorney.

How is Accessibility Shield different from accessiBe or UserWay?

Overlay widgets change the page in the visitor's browser with JavaScript, and their entry plans start around $490/year. Accessibility Shield costs $1/month and shows you what to fix in your own source code. Its optional widget is about 8 KB (about 3.3 KB gzipped) and only offers reading preferences and a barrier report form.

Will the widget slow down my website?

Its effect is very small. The widget is about 8 KB minified (about 3.3 KB gzipped), has no external dependencies, and loads asynchronously without blocking page rendering.

Accessibility Statement | Accessibility Shield

Accessibility Shield is dedicated to ensuring digital accessibility for all visitors, including individuals with visual, auditory, cognitive, and motor disabilities. We continually refine our user interface and apply recognized accessibility standards to ensure an equitable, frictionless experience for everyone visiting accessibilityshield.org.

1. Conformance Status

The Web Content Accessibility Guidelines (WCAG) define technical benchmarks for designers and developers to enhance digital accessibility for people with disabilities. WCAG defines three levels of conformance: Level A, Level AA, and Level AAA.

accessibilityshield.org aims to conform with WCAG 2.1 Level AA.

2. Accessibility Measures & Engineering Standards

To support and maintain digital accessibility across our platform, we enforce the following engineering practices:

Semantic HTML5 Architecture: We structure all pages using native semantic HTML elements (<header>, <main>, <nav>, <footer>, <section>, <article>) to ensure clear document landmarks for screen readers.
Keyboard Operability: We build navigation menus, dialogs, forms, and buttons to work with a keyboard (Tab, Shift+Tab, Enter, Space, and Escape). If you find a control that doesn't, please report it.
Visible Focus Rings: We provide prominent, high-contrast :focus-visible outline rings on all interactive components to ensure keyboard users never lose their visual position.
Skip-to-Content Navigation: A hidden skip link is available at the top of every page, allowing keyboard and screen reader users to bypass repetitive header navigation and jump straight to main content.
Color Contrast Ratios: We design body text for at least the 4.5:1 contrast ratio WCAG AA requires, and large headings, interactive elements, and form borders for at least 3:1.
Reading Preferences: Our optional help button (about 8 KB) lets visitors change text size, raise contrast, switch to a more readable font, highlight links, stop animations, or add text spacing. Choices are remembered only in their own browser.
ARIA Best Practices: Where custom UI primitives are required, we implement compliant WAI-ARIA roles, attributes, and live regions (aria-live="polite") without disrupting native assistive behaviors.
Automated Scanning: We scan accessibilityshield.org with our own @axe-core/playwright scanner and fix the issues it finds.

3. Technical Specifications

Accessibility of accessibilityshield.org relies on modern web technologies conforming with:

HTML5
WAI-ARIA (Accessible Rich Internet Applications)
CSS3 (with dynamic dark/light design tokens and fluid typography)
JavaScript (ECMAScript 6+)

4. Assessment Methodology

We evaluate the accessibility of accessibilityshield.org like this:

Automated Audits: Scans with Axe-Core in a headless browser.
Manual Checks: Automated scans miss some issues, so we are adding regular manual checks of our key pages (keyboard, focus, zoom, reflow, media, forms, screen reader) using the same 15-minute checklist our customers use.
Your Reports: Barrier reports from visitors go straight to us, and we treat them as bugs.

5. Feedback & Contact Channels

We welcome your questions, feedback, and suggestions regarding the accessibility of accessibilityshield.org. If you encounter an accessibility barrier or need assistance with any feature:

On-Site Widget: Select the round shield button in the bottom-right corner of any page to send a barrier report.
Email: accessibilityshieldorg@gmail.com
Response: We read every accessibility report and aim to reply within 2 business days.

6. Review Date

This Accessibility Statement was last reviewed on October 9, 2026.

1. Conformance Status

accessibilityshield.org aims to conform with WCAG 2.1 Level AA.

2. Accessibility Measures & Engineering Standards

To support and maintain digital accessibility across our platform, we enforce the following engineering practices:

Semantic HTML5 Architecture: We structure all pages using native semantic HTML elements (<header>, <main>, <nav>, <footer>, <section>, <article>) to ensure clear document landmarks for screen readers.

Keyboard Operability: We build navigation menus, dialogs, forms, and buttons to work with a keyboard (Tab, Shift+Tab, Enter, Space, and Escape). If you find a control that doesn't, please report it.

Visible Focus Rings: We provide prominent, high-contrast :focus-visible outline rings on all interactive components to ensure keyboard users never lose their visual position.

Skip-to-Content Navigation: A hidden skip link is available at the top of every page, allowing keyboard and screen reader users to bypass repetitive header navigation and jump straight to main content.

Color Contrast Ratios: We design body text for at least the 4.5:1 contrast ratio WCAG AA requires, and large headings, interactive elements, and form borders for at least 3:1.

Reading Preferences: Our optional help button (about 8 KB) lets visitors change text size, raise contrast, switch to a more readable font, highlight links, stop animations, or add text spacing. Choices are remembered only in their own browser.

ARIA Best Practices: Where custom UI primitives are required, we implement compliant WAI-ARIA roles, attributes, and live regions (aria-live="polite") without disrupting native assistive behaviors.

Automated Scanning: We scan accessibilityshield.org with our own @axe-core/playwright scanner and fix the issues it finds.

4. Assessment Methodology

We evaluate the accessibility of accessibilityshield.org like this:

Automated Audits: Scans with Axe-Core in a headless browser.

Manual Checks: Automated scans miss some issues, so we are adding regular manual checks of our key pages (keyboard, focus, zoom, reflow, media, forms, screen reader) using the same 15-minute checklist our customers use.

Your Reports: Barrier reports from visitors go straight to us, and we treat them as bugs.

5. Feedback & Contact Channels

We welcome your questions, feedback, and suggestions regarding the accessibility of accessibilityshield.org. If you encounter an accessibility barrier or need assistance with any feature:

On-Site Widget: Select the round shield button in the bottom-right corner of any page to send a barrier report.

Email: accessibilityshieldorg@gmail.com

Response: We read every accessibility report and aim to reply within 2 business days.