Accessibility Statement (WCAG 2.2 AA & EAA)
Targeted WCAG 2.2 Level AA for guest pages: what was tested (axe, keyboard, NVDA 2026.2), known gaps, and how to report a barrier.
1. Conformance Status with WCAG 2.2 Level AA
WCAG 2.2 AA — targetedAI-Software (ai-software.pro) aims to meet WCAG 2.2 Level AA and the European Accessibility Act (EAA / Directive (EU) 2019/882). This statement covers public guest pages (home, software, prints, gallery, blog, contact, legal). The content-studio CMS is out of guest scope. We do not treat a Lighthouse score as a certificate.
Body text uses ink-400 (7.76:1 on #09090b). Content photos have alt text.
Skip link, logical Tab order, Escape on overlays. Dialogs use an intentional focus trap.
html lang from the URL; visible labels; errors via role=alert.
Landmarks, dialog aria-modal, unique control names. Axe 0 violations on sampled pages.
2. Implemented Technical Measures & Architecture
Accessible components- Universal Focus Indicator: Every interactive element features an explicit, high-contrast visual focus ring (2px solid outline with 3px offset) adhering to WCAG 2.4.7.
- Support for Reduced Motion: For users sensitive to motion sickness, all visual animations and smooth scroll transitions are automatically suppressed via CSS prefers-reduced-motion rules.
- Accessible Forms & Real-Time Feedback: Input fields feature programmatic label associations, validation errors are announced via role="alert" and aria-invalid, and submissions trigger aria-live announcements.
3. Keyboard Shortcuts & Navigation Aids
Keyboard operableAll guest features are operable via keyboard. A visible Skip Link is the first control in the DOM. In a gallery item it is named skip-to-artwork and targets the artwork heading. Gallery thumbnails use a listbox (one Tab stop, arrow keys).
Sequential navigation across interactive controls in logical reading order.
Dismisses modal dialogs, cookie banner, and gallery overlay, with focus returned to the opener where applicable.
4. Screen Reader Compatibility & Assistive Tech
NVDA 2026.2 · JAWS untestedMarkup is prepared for NVDA, JAWS, VoiceOver, TalkBack and Orca (landmarks, accessible names, live regions, `html lang` from the URL). On 20 September 2026 the Polish homepage and gallery overlay were checked with axe-core 4.10.3 (0 violations) and a keyboard / accessibility-tree pass. The same day NVDA 2026.2 read the Polish statement in Chrome and Firefox. JAWS was not run. English-tagged fragments (for example Local-First) stay `lang=en`; the installed OneCore voice is Polish-only, so NVDA does not switch language. Please report any remaining barrier.
Meaningful photos and product screenshots have alternative text. Decorative Lucide icons use aria-hidden. Hover-swap print images use empty alt on the second frame.
5. Audit Methodology & Quality Assurance
Axe-core 4.10.3Evaluation follows WCAG-EM in reduced form: sample pages, automated + keyboard + tree review:
- Automated axe-core 4.10.3 against WCAG 2.2 A/AA on 20 September 2026: 0 violations on the Polish homepage and gallery overlay. Duplicate IDs: 0. A Lighthouse score is a snapshot, not a 100/100 certificate.
- Manual keyboard-only traversal of the contact form, cookie dialog, gallery overlay, and product/print detail pages, plus an accessibility-tree name/role/value review of those views.
- Reflow at 320 CSS px; gallery CSS zoom 200% with no horizontal overflow. Chrome UI 200% at 1280×720 remains a recommended extra check.
- NVDA 2026.2 (OneCore voice pl-PL Paulina) was run on 20 September 2026 in Chrome and Firefox on the Polish statement, plus a keyboard/accessibility-tree pass of the gallery overlay and contact form (heading jump, listbox one tab stop, required fields set aria-invalid). JAWS was not run. OneCore logs “Language en not supported” on lang=en fragments because only a Polish voice is installed.
6. Known limitations
Honest gapsWe list remaining gaps so this page is not a fake certificate:
- Content-studio / admin UI is out of guest WCAG scope.
- JAWS not run. NVDA 2026.2 covered the Polish statement (Chrome + Firefox) and a tree/keyboard pass of gallery overlay + contact validation; OneCore pl-PL does not switch to English for lang=en parts.
- Product demo clips have no spoken dialogue; captions (1.2.2) apply only if speech is added later.
- Axe color-contrast is incomplete on some glass/gradient surfaces; body copy uses the ink-400 token (pass on #09090b).
7. Accessibility Feedback & Escalation Channel
Reply on business daysIf you encounter any accessibility barriers or need documentation in another format, contact:
If a reported barrier is not resolved, you may contact the market surveillance authority of your EU member state under the EAA.
Statement closed for this stage: 20 September 2026. Methods: WCAG-EM sample, axe-core 4.10.3 (0 on PL home + gallery overlay), keyboard, accessibility-tree, NVDA 2026.2 on Chrome and Firefox (PL statement). JAWS not run. Not an AA certificate.