Accessibility terms
Great software works for everyone, not just the majority
Accessibility is not a feature to add at the end — it is a quality dimension that affects every design and implementation decision. This category covers WCAG guidelines, ARIA attributes, keyboard navigation, screen reader compatibility, colour contrast, and the testing approaches that ensure your software genuinely works for users with disabilities. Accessible code is almost always better code.
HTML lang Attribute
The lang attribute on <html> declares the page's primary language — required for screen readers to select the correct voice profile and pronunciation rules, and for WCAG 2.1 compliance.
1mo ago
accessibility beginner
Accessible Data Tables
HTML tables marked up with correct semantic elements and ARIA roles so screen readers can announce cell context — column header, row header, and position — to the user.
1mo ago
accessibility beginner
prefers-reduced-motion — Accessible Animations
A CSS media query and JavaScript API that detects when a user has requested reduced motion in their OS settings, allowing you to disable or simplify animations that can trigger vestibular disorders.
1mo ago
accessibility beginner
Skip Links & Bypass Blocks HTML5
Hidden links at page top letting keyboard users jump past navigation to main content — a WCAG 2.4.1 requirement.
2mo ago
accessibility beginner
Colour Contrast CSS3 The ratio between foreground and background colours — WCAG requires 4.5:1 for normal text and 3:1 for large text at AA level, ensuring readability for low-vision users.
2mo ago
accessibility beginner