Accessibility Statement
Official technical verification report of AIfa Works conformance with WCAG 2.2 Level AA, testing methodology, and open self-audit evidence.
1. Scope & Ecosystem Properties
This accessibility statement applies directly to the primary website https://aifa.works/. Other web properties operated within the CODE Eternal / AIfa ecosystem maintain their own respective accessibility parameters as documented in our cross-ecosystem audit below.
2. Our Latest Self-Assessment Results (27 August 2026)
Research MethodologyOn 27 August 2026, AIfa Works performed a rigorous manual keyboard traversal and automated verification of all 4 websites in its ecosystem using the exact reproducible methodology published in our nationwide municipal research:
| Web Property | Focus Outline | Interactive Elements | Unnamed Elements | Focus Loss |
|---|---|---|---|---|
| aifa.works | solid 2px | 104 | 0 | 0.0% |
| codeofdigitaleternity.com | solid 3px | 91 | 0 | 0.0% |
| aifa.digital | solid 3px | 67 | 0 | 0.0% |
| radiocode.space | auto 1px | 46 | 0 | 0.0% |
3. Assessment Approach & Testing Environment
Accessibility evaluation of aifa.works was executed using a rigorous combined approach of automated rule-checking and live human manual validation across assistive environments:
- axe-core v4.9 engine
- W3C Nu HTML Validator
- Lighthouse a11y ruleset
- Automated contrast analyzers
- Keyboard-only navigation (no mouse)
- 200% browser zoom reflow check
- prefers-reduced-motion triggers
- Form label & error state audit
- NVDA 2024.2 + Firefox on Windows
- VoiceOver + Safari on macOS/iOS
- TalkBack + Chrome on Android
- High Contrast Mode (OS level)
4. What Users Should Be Able to Do
Traverse all 104 interactive nodes using Tab, activate links with Enter, toggle controls with Space, and dismiss modals with Esc.
Enlarge page view up to 200% without horizontal text clipping, overlapping components, or layout breakage.
Track active position via persistent high-contrast focus rings (solid 2px cyan) with zero focus traps.
Press Tab upon initial page load to immediately jump past top navigation bars directly to primary content.
5. Known Limitations & Workarounds
In adherence to W3C transparency standards, we document specific non-conformances alongside viable alternatives:
| Area / Element | Non-Conformance Detail | Workaround / Alternative | Target Roadmap |
|---|---|---|---|
| Decorative Canvas Particle Shaders | Under specific browser engines, WebGL particle shaders may trigger brief initial paint before prefers-reduced-motion listener binds. | Enable OS-level reduced motion or toggle theme switch to enforce static canvas rendering. | Q4 2026 |
| Dense Scanner Data Tables | On narrow viewports (< 360px), dense multi-column tabular audit matrices require horizontal scroll gesture. | Download direct machine-readable JSON/CSV data export or request plain-text summary. | Q4 2026 |
Transparency Case Study: The "outline: none" Audit
During the public audit of our own codebase, we documented 83 occurrences of legacy CSS reset `outline: none`. An abstract automated static scanner might flag this as a critical barrier. However, live keyboard traversal confirmed that our overarching `:focus-visible` rule fully compensates for the reset, rendering a crisp 2px cyan focus indicator across all interactive flows. We intentionally publish this finding to demonstrate the vital difference between superficial source code heuristics and genuine human-centric accessibility.
Report an Accessibility Barrier
Direct Engineering LineIf you encounter any accessibility barrier on aifa.works, please submit the details below. Our technical team will review and respond within 2 business days:
Request an Alternative Accessible Format
If you require information from this website in an alternative accessible format (structured clean HTML, plain text, large print, or tabular JSON/CSV data optimized for screen reader digestion), please contact contact@codeofdigitaleternity.com. We will provide the requested asset free of charge within 2 business days.
Regulatory & Jurisdictional Information
This accessibility statement reflects the empirical technical practices of AIfa Works and does not constitute a statutory certification of legal compliance. The platform is developed by a decentralized technical team under civil contractor jurisdiction (Ecuador / International Law). Specific legal accessibility obligations vary by client jurisdiction and procurement context (e.g., US ADA Title III, Section 508, European Accessibility Act EN 301 549). Specific compliance frameworks are assessed and certified on a dedicated per-deployment basis.
Statement Revision History
| Date | Action / Modification | Status |
|---|---|---|
| 20 Sep 2026 | Upgraded target to WCAG 2.2 Level AA; published 27 August self-assessment data; added interactive barrier submission form. | Current |
| 27 Aug 2026 | Full manual keyboard traversal of 4 ecosystem sites (104 nodes on aifa.works, solid 2px outline confirmed). | Audited |
| 23 May 2026 | Initial accessibility statement publication. | Initial |