
Accessibility is often treated as an add-on — something you bolt on at the end when there’s budget left over. That’s not only wrong, it’s expensive. Retrofitting accessibility fixes costs a multiple of getting it right from the start.
WCAG 2.1 AA as the baseline
The Web Content Accessibility Guidelines define four principles: Perceivable, Operable, Understandable, Robust. Level AA is the recognized minimum standard for professional websites. In ABSTRAKT it isn’t optional — it’s the foundation of every component.
Semantic HTML
The most important tool for accessibility is also the simplest: correct HTML. A <button> instead of a <div onclick>. A <nav> instead of a <div class="navigation">. An <h2> in the right hierarchy.
Semantic HTML gives screen readers context, keyboards a focus order, and search engines structure. Three birds with one stone.
Contrast that works
WCAG requires 4.5:1 for regular text and 3:1 for large text (18px bold or 24px regular and above). ABSTRAKT maintains stricter internal standards:
--foregroundon--background: at least 15:1--muted-foregroundon--background: at least 5:1--muted-foregroundon--muted: at least 4.5:1
These values apply in both Light and Dark Mode. No compromises.
Keyboard navigation
Every interactive component must be reachable and operable via keyboard:
- Tab moves focus forward
- Shift+Tab moves focus backward
- Enter/Space activates buttons and links
- Escape closes modals and dropdowns
- Arrow keys navigate within components (tabs, accordion)
Focus styles are visible and consistent: outline: 2px solid var(--ring) with outline-offset: 2px. Never outline: none without a visible alternative.
Using ARIA correctly
ARIA is a powerful tool — and a dangerous one. The first rule of ARIA: don’t use ARIA when a native HTML element exists. The second rule: if you do use ARIA, test it with a screen reader.
In ABSTRAKT we use ARIA deliberately:
aria-labelfor icon buttons with no visible textaria-expandedfor dropdowns and accordionsaria-hidden="true"for decorative elementsrole="alert"for error messagesaria-live="polite"for dynamic content
Skip links
Every page has a skip link as its first focusable element: “Skip to content.” It becomes visible on focus and bypasses the header and navigation.
Testing
Automated tools catch roughly 30% of accessibility issues. The rest requires manual testing:
- Keyboard-only: navigate the entire page without a mouse
- Screen reader: VoiceOver (Mac), NVDA (Windows), TalkBack (Android)
- Zoom: 200% and 400% — does the layout break?
- Reduced motion: does the page respect
prefers-reduced-motion?
Conclusion
Accessibility is not a feature you switch on. It’s a quality characteristic that is built in from the start — or it’s absent. In ABSTRAKT every component is accessible from the first commit. Not perfect, but intentional and continuously improved.