WCAG 2.2 AA
Our standard
We target Web Content Accessibility Guidelines 2.2 Level AA across the entire product surface — the dashboard you use to generate sites, and the sites generated for your visitors. AA is the level required by US Section 508, the EU Accessibility Act, and most enterprise procurement processes.
We don't claim AAA compliance on either surface. Some AAA criteria (sign-language interpretation, reading-level, audio descriptions) require content judgment we can't fully automate. AA is the practical, enforceable target.
Default behaviors
What we ship in generated sites
- Semantic HTML5 structure.
<header>,<main>,<nav>,<section>,<article>,<footer>on every page. ARIA landmark roles where appropriate. - Heading hierarchy. One H1 per page (the hero headline). H2s section the page. H3-H6 nest correctly. No skipped levels.
- Alt text on every image. Generated images get descriptive alt text from the content model; decorative images get
alt="". - Color contrast. 4.5:1 minimum for body text, 3:1 for large text and non-text UI. Auto-checked at generation time; sites with failing contrast are flagged before publish.
- Keyboard navigation. Every interactive element (links, buttons, form fields, accordions) is keyboard-reachable. Visible focus rings on all focusable elements.
- `prefers-reduced-motion` respected on the framer-motion primitives shipped in /components/hero-effects (parallax, scroll-velocity, reveal animations). Three.js shader heroes don't yet fully respect it — tracked for 2026 Q3.
- Form accessibility. Every form input has a visible label; errors are announced to assistive tech via
aria-invalidandrole="alert". - Document language.
<html lang="en">on every site (locale-specific lang attributes when localization ships in Phase 3).
Honest about the work left
Audit log of known gaps
Three.js hero shaders lack screen-reader fallback announcement
Impact: Decorative only; no functional content lost
Fix: Adding aria-hidden + visible static fallback for `prefers-reduced-motion`
ETA: 2026 Q3
Some 'dark luxury' palette tokens push 3:1 minimum on body text
Impact: Body text in 4 of 50 design taxonomies is borderline 3.0:1 — 3.5:1
Fix: Token adjustment in dark-mode palette to lift contrast above 4.5:1
ETA: 2026 Q2
Live preview iframe doesn't expose the parent dashboard's keyboard shortcuts
Impact: Power users have to focus the dashboard explicitly to use shortcuts
Fix: Adding shortcut bridge in iframe message protocol
ETA: 2026 Q3
Auto-generated alt text quality varies by image source
Impact: Stock imagery from third-party libraries gets descriptive but generic alt text
Fix: Improving alt-generation prompt to include surrounding context (heading, section purpose)
ETA: 2026 Q2
Get in touch
Reporting an accessibility issue
Email accessibility@killerwebsite.ai with:
- The URL or area of the product where the issue occurs.
- What you were trying to do.
- Which assistive technology you're using — screen reader (NVDA / JAWS / VoiceOver / TalkBack), keyboard-only navigation, voice control, switch device, etc.
- Operating system and browser.
We aim for a substantive reply within 2 business days. Issues blocking a core workflow get a fix within 30 days; nice-to-haves enter the public roadmap.
FAQ
Frequently asked questions
Is the Website Killer dashboard accessible?
We target WCAG 2.2 AA across the dashboard. The chat editor, project list, settings panels, and billing flows have been audited for keyboard navigation, focus management, and screen-reader compatibility (NVDA on Windows, VoiceOver on macOS, TalkBack on Android). Known gaps and the timeline to fix them are listed in the audit log section below; we update quarterly.
Are sites generated by Website Killer accessible by default?
Generated sites use semantic HTML5 (`<header>`, `<main>`, `<nav>`, `<section>`, `<article>`, `<footer>`), proper heading order (one H1 per page, sequential H2-H6), alt text on every generated image, ARIA landmark roles, color-contrast checked against WCAG AA (4.5:1 for body, 3:1 for large text), keyboard-navigable interactive elements, and visible focus states. Pages also pass a Lighthouse Accessibility score of 95+ in our automated tests.
What's not accessible yet?
Known gaps: (1) some animations don't fully respect `prefers-reduced-motion` — fixing in 2026 Q3. (2) The 3D / WebGL hero shaders are decorative-only but lack a fallback announcement for screen readers — adding aria-hidden + a static fallback in 2026 Q3. (3) Color contrast in some 'dark luxury' design taxonomies pushes the 3:1 minimum on body text — adjusting the dark-mode palette tokens in 2026 Q2.
Can I generate WCAG-compliant sites for my clients?
Yes — and we recommend you do. The generated output meets WCAG 2.2 AA on most measurable criteria out of the box. For full WCAG 2.2 AAA compliance (sign-language interpretation, advanced reading-level, etc.), you'll need to add additional content — but the structural baseline is solid. Run an axe DevTools or Lighthouse audit on the generated site to confirm before client delivery.
Do you offer a separate accessibility-focused service?
Not as a separate offering. Accessibility is treated as a default behavior of the product, not a paid add-on. Enterprise customers can request a formal VPAT (Voluntary Product Accessibility Template) for procurement and ADA compliance documentation.
How do I report an accessibility issue?
Email accessibility@killerwebsite.ai with: (1) the URL where the issue occurs, (2) what you were trying to do, (3) which assistive technology you're using (screen reader, keyboard-only, voice control). We aim to respond within 2 business days and to ship a fix within 30 days for any issue blocking a core workflow.
Are you compliant with the EU Accessibility Act (EAA)?
We're tracking the EAA's June 2025 enforcement deadline for B2C SaaS. Our dashboard targets WCAG 2.2 AA, which is the EAA's de-facto compliance baseline. For B2B-only customers in the EU, the act doesn't strictly apply but we maintain the same standard. Specific EAA documentation (conformance statement) is available to enterprise customers on request.
Keep exploring
Related
- → Security — encryption, subprocessors, SOC 2 path, vulnerability disclosure
- → Privacy — what we collect, how we use it, GDPR / CCPA rights
- → What is WCAG? — glossary entry on Web Content Accessibility Guidelines
Generate accessible-by-default sites.
Every site shipped on Website Killer starts with WCAG 2.2 AA defaults — semantic HTML, alt text, contrast, keyboard navigation. Free to try.