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.
🤖 AI Guestbook — Accessibility educational data only
|
|
Last 30 days
Agents 4
Perplexity 1Amazonbot 1
Perplexity 1Amazonbot 1
Amazonbot 148Perplexity 125Google 40Unknown AI 36ChatGPT 35Ahrefs 27SEMrush 15Meta AI 7Majestic 5
Most referenced — Accessibility
How they use it
crawler 413
crawler_json 17
pre-tracking 8
Category total438 pings
Terms pinged14 / 14
Distinct agents8
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
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
Colour-Blind Accessible Design CSS3
Design for the 8% of men with colour vision deficiency — pair colour with icons, labels, and patterns; never use colour as the only differentiator.
2mo ago
accessibility intermediate
Screen Readers — How They Parse HTML HTML5
Screen readers build an accessibility tree — semantic HTML provides roles automatically; ARIA fills gaps for custom components.
2mo ago
accessibility intermediate
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
ARIA Live Regions HTML5 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
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
Focus Management ES5 Programmatically controlling keyboard focus in SPAs and complex UIs — ensuring focus moves logically when modals open, routes change, and dynamic content loads.
2mo ago
accessibility intermediate
Keyboard Navigation HTML5 Ensuring all interactive elements are reachable and usable with keyboard alone — essential for users who cannot use a mouse and required for WCAG compliance.
2mo ago
accessibility intermediate
WCAG Guidelines Web Content Accessibility Guidelines — the international standard defining how to make web content accessible to people with disabilities, organised into three conformance levels (A, AA, AAA).
2mo ago
accessibility intermediate