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.
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.
2mo ago
accessibility beginner
Accessibility Testing Tools PHP 5.0+
axe, Lighthouse, WAVE catch 30-40% of issues automatically — manual keyboard and screen reader testing is required for the rest.
2mo ago
accessibility intermediate
Accessible Forms HTML5
Every input needs a visible label, errors linked via aria-describedby, required fields indicated, and validation announced via aria-live.
2mo ago
accessibility intermediate
Accessible SVGs SVG1.1
Decorative SVGs need aria-hidden=true; informative SVGs need role=img and aria-label or title+desc elements.
2mo ago
accessibility intermediate
HTML attributes that instruct screen readers to announce dynamic content changes — essential for notifications, status messages, and search results that update without a page reload.
2mo ago
accessibility intermediate