ACCESSIBILITY
The baseline is usable before it is spectacular.
PliegoCSS treats accessibility as an output invariant: semantic HTML, keyboard operation, stable focus, reduced motion, explicit language, and progressive enhancement.
Useful HTML first
Every page ships meaningful server-rendered HTML before client motion or laboratory hydration. Core navigation and documentation remain links, headings, lists, forms, and text.
Keyboard and focus
Interactive controls use native buttons, inputs, and dialogs; visible focus is preserved; the skip link reaches main content; and command search supports keyboard navigation.
Reduced motion
The site follows prefers-reduced-motion, disables smooth scrolling and WebGL decoration, and keeps content visible without scroll-triggered movement.
Language and structure
English and Spanish pages declare their language, provide equivalent URLs, preserve heading hierarchy, and keep the same product and legal scope.
Report a barrier
Email hello@pliegocss.dev with the route, browser or assistive technology, expected behavior, and the barrier encountered. Accessibility feedback is handled as product evidence.