Análisis técnicos en profundidad, guías de cumplimiento y tutoriales prácticos del equipo que desarrolla AccessiSight.
Guides on WCAG 2.2, ADA, EAA, and Section 508 compliance, CI/CD and screen reader testing, and cognitive accessibility, written by the team building AccessiSight's accessibility checker.
Filter by topic
The European accessibility standard now adopts WCAG 2.2 and adds six requirements. Until the EU cites it in the Official Journal, v3.2.1 (WCAG 2.1 AA) stays the reference. What changed, what didn't, and the six criteria to check first.
In June 2026 a French court ordered Carrefour to make its site and app fully accessible within six months. What the court said, what happened to the other retailers, and what EU regulators are doing.
For the first time in six years, home pages got worse: 95.9% had detected WCAG failures and errors per page rose 10%. The six most common errors, and how to fix each.
WebAIM's 11th screen reader survey found 91.8% of respondents use AI in some way, often to describe images that sites left undescribed. What the numbers say about headings, alt text and the year ahead.
US website accessibility lawsuits rose 27% in 2025 and are on a record pace in 2026. About one in five sued companies had an accessibility widget installed. The figures, their sources, and what they mean for you.
AI coding tools are adding ARIA that breaks pages, and AI agents now navigate the web the way screen readers do. Why the accessibility tree has become your interface for both, and what to check.
W3C published new WCAG 3 working drafts on 10 September 2026 with a reworked conformance model. W3C's own advice: WCAG 3 is years away, WCAG 2 won't be deprecated soon, and the way to prepare is to meet WCAG 2.2 now.
Draft amendments to India's RPwD Rules, published for comment in July 2026, would require websites, apps and documents to meet IS 17802 and publish an Accessibility Conformance Report. What the draft says, the court cases behind it, and what is still unknown.
A scanner can prove that a page fails some WCAG checks. It cannot prove that a page is accessible. Where that line sits, and how to read a report without over- or under-trusting it.
Decorative, informative, functional, text, complex: most alt text problems come from treating every image the same way. A practical way to decide, with code.
Removing focus outlines is still one of the most common keyboard accessibility failures. How to design a focus style that looks intentional, survives sticky headers and works in forced-colours mode.
WCAG 2.2 added a minimum target size of 24 by 24 CSS pixels, with five exceptions that matter in practice. How the spacing test really works, with numbers you can apply.
Red borders and a toast that disappears after three seconds are not error handling. A pattern for identifying errors, suggesting fixes and announcing them, mapped to WCAG 3.3.1, 3.3.3 and 4.1.3.
The DOJ rule requires WCAG 2.1 AA for state and local government websites and apps. In April 2026 the compliance dates moved. The current dates, who they apply to and the five exceptions.
Most dialog bugs come down to focus: where it goes when the dialog opens, where it can go while it is open, and where it lands when it closes. How to get all three right with the native <dialog> element.
Success criterion 4.1.1 Parsing is "obsolete and removed" in WCAG 2.2, and the W3C now says to treat it as always satisfied for HTML in 2.0 and 2.1. What changed, and which of the old failures still matter.
A PDF can look perfect and still be unusable with a screen reader. The structure that makes PDFs accessible, what PDF/UA requires, and the parts that still need a person to check.
WCAG 2.2 says a login step cannot depend on a memory or puzzle test unless there is an alternative or help. What that means for passwords, paste blocking, one-time codes and CAPTCHAs.
The 9 new success criteria in the Web Content Accessibility Guidelines (WCAG) 2.2, what each one asks for, and how to test for them.
A step-by-step checklist for meeting ADA Title III requirements on your website, lowering lawsuit risk and improving the experience for every user.
The EAA deadline has passed: enforcement began on June 28, 2025. What the European Accessibility Act requires, who it applies to, and how to catch up now.
What Section 508 of the Rehabilitation Act requires of federal agencies and the contractors who sell to them, and how to show your product conforms.
Automated scanners, browser extensions, screen readers and full platforms each find different problems. What each kind is good at, and how to combine them.
Understand the WCAG color contrast requirements (1.4.3 and 1.4.11). Learn how to check contrast ratios and design accessible color palettes.
How WAI-ARIA accessible names work, and when to use aria-label, aria-labelledby, or aria-describedby, with code examples.
How to test keyboard accessibility by hand and with automated tools, so your website works without a mouse and meets WCAG 2.1.1.
A practical guide to testing web accessibility with screen readers like NVDA, JAWS, and VoiceOver. Learn basic commands and testing strategies.
What a VPAT (Voluntary Product Accessibility Template) is, why buyers ask for one during procurement, and how to create an ACR (Accessibility Conformance Report).
Understand the relationship between the Americans with Disabilities Act (ADA) and the Web Content Accessibility Guidelines (WCAG).
A breakdown of web accessibility audit pricing. Compare the costs of automated testing, manual audits, and comprehensive enterprise platforms.
Learn how to build accessible React applications. A guide to managing focus, handling dynamic content, and using ARIA in React components.
Ensure your mobile apps and responsive websites are accessible. Key WCAG considerations for touch targets, gestures, and mobile screen readers.
Learn about cognitive accessibility. How to design websites that support users with ADHD, autism, dyslexia, and learning disabilities.
Run a free scan and see exactly which of these issues show up on your own site.
Run a Free Accessibility Scan