Skip to content
Atharva Patil

Accessibility statement

What's actually done, and what honestly isn't yet.

Target: WCAG 2.1 AA. What's below is an honest self-assessment, not an unverified compliance badge.

What's implemented

  • Semantic landmarks throughout: <header>, <main>, <nav>, <footer>, <section>, <article>.
  • Skip-to-content link (first tab-stop, becomes visible on focus).
  • Visible :focus-visible ring site-wide (2px purple-bright outline).
  • All interactive elements keyboard-reachable. Command palette (⌘K) fully keyboard-driven.
  • Every image has real alt text — no decorative placeholders on meaningful images.
  • prefers-reduced-motion honored: all animations collapse to instant on request.
  • prefers-color-scheme respected on first visit; user toggle persists via localStorage.
  • Contrast ratios: WCAG AA at every text/background pairing in both light and dark themes.
  • Text remains readable and layout intact at 200% zoom.

Known gaps

  • Not independently audited yet — no external accessibility review has been performed. This is an honest self-assessment.
  • Some screenshots on case-study pages have descriptive alt text but no long-description transcript for complex visuals (e.g., the Kanvaz board view). Planned addition.
  • The theme-boot inline script runs before first paint and can't be gated by prefers-reduced-motion; the theme switch itself is instant regardless of user preference (no animation applied).

Last reviewed: v5.0-alpha migration (2026-08-09). If you find something broken — email [email protected].