If your website or app has ever made a customer squint, pinch-zoom, or give up on a form field they couldn’t quite read, you’ve already met the problem this post is about. For years, accessibility sat in the “nice to have, get to it eventually” pile for a lot of growing businesses. Three separate stories that surfaced in the first three weeks of September 2026 suggest that pile is shrinking fast — because accessibility is now a standards conversation, a design conversation, and a legal conversation happening at the same time.

None of these stories made front-page headlines. But taken together, they’re a useful signal for any business owner deciding what to prioritize in their next website refresh or app update.

Apple’s own design system is under scrutiny

In mid-September, Apple released updated design kits for iOS, iPadOS, and macOS 27, giving designers refreshed Figma and Sketch files built around “Liquid Glass” — the translucent, layered look Apple introduced across its operating systems. It’s a routine update on paper: new component states, naming that matches the underlying code, better resizing behavior.

What makes it notable is the backdrop. Since Liquid Glass first shipped, usability researchers have been flagging real problems with it. The Nielsen Norman Group’s review of the design language found that translucent surfaces reduced text contrast enough to hurt legibility, especially in bright light or for users with low vision, and that some interface elements became genuinely harder to locate against busy backgrounds. Apple has walked back some of the transparency in subsequent updates and added toggles to let users flatten the effect. The lesson isn’t “don’t use trendy visual styles” — it’s that even a company with Apple’s design resources can ship something beautiful that quietly fails a chunk of its users, and that the fix usually comes after the complaints, not before.

The accessibility bar is about to move

On September 10, the World Wide Web Consortium published its latest working draft of WCAG 3.0, the next generation of the guidelines that most accessibility audits, vendor contracts, and legal complaints are measured against. It’s still years from being final, and WCAG 2.2 remains the standard businesses should be meeting today. But the direction of travel is worth noting: the new draft moves several requirements that used to be “nice to have” (such as full transcripts for video and plain-language explanations of abbreviations) into the mandatory core tier, and it proposes a simpler single conformance level instead of today’s A/AA/AAA ladder.

Standards documents rarely feel urgent when they’re published. But they tend to show up two or three years later as the baseline that procurement teams, government contracts, and plaintiffs’ attorneys expect you to already meet.

And the lawsuits are climbing, not leveling off

The most concrete data point came from a mid-year litigation report published September 9: federal ADA Title III lawsuit filings hit 5,006 in the first half of 2026, the highest first-half count since 2021 and well above the four-year average. Website and app accessibility cases have been a growing share of that total, with 2025 alone seeing a 27% jump in website-specific suits over the year before. California continues to generate the largest share of filings, but the pattern isn’t limited to one state or one industry — retailers, healthcare providers, and financial services firms all show up regularly in these suits.

This isn’t a scare story about ambulance-chasing; it’s a straightforward observation that the legal exposure for an inaccessible website has been rising steadily for several years, and 2026 is on pace to continue that trend.

What this means if you’re planning a website or app project

1. Ask your design partner how accessibility gets tested, not just whether it’s “considered.” “We follow best practices” is not an answer. A credible partner can tell you which WCAG level they build to, what automated and manual testing they run, and how they handle screen readers, keyboard navigation, and color contrast specifically.

2. Ask what happens when a trendy visual style and legibility conflict. Liquid Glass is a good case study precisely because it came from a company with enormous design resources and still needed real-world correction. Before you approve a slick new look for your site or app, ask your partner to show you how it performs under bright light, at larger text sizes, and with a screen reader — not just in the polished mockup.

3. Ask where your current site actually stands today. A short accessibility audit is inexpensive compared to a lawsuit, and it gives you a prioritized list instead of a vague sense of risk. If nobody has run one on your site in the last year or two, that’s the first conversation to have.

The takeaway

None of this requires an overnight overhaul. Accessibility work is incremental by nature — better contrast, proper labels on form fields, keyboard-navigable menus, captions on video — and most of it pays for itself in a better experience for every user, not just the ones the law is specifically protecting. What’s changed is the cost of ignoring it: the standards are getting more demanding, even the biggest design teams are getting caught by legibility problems, and the legal system is paying closer attention than it was two years ago.

If you’d like a second set of eyes on where your website or app stands, or you’re weighing a redesign and want accessibility built in from the start rather than bolted on later, email us at info@kodevox.com or reach out through our contact page.

Sources and further reading:

• Apple Developer News — Design kits for iOS, iPadOS, and macOS 27 are here (September 2026)
• Nielsen Norman Group — Liquid Glass Is Cracked, and Usability Suffers in iOS 26
• W3C Web Accessibility Initiative — For Review: WCAG 3 Working Draft – September 2026 (10 September 2026)
• Mondaq / Seyfarth Shaw — 2026 Mid-Year Report: ADA Title III Federal Lawsuit Numbers Are Climbing (9 September 2026)
• ADA Title III (Seyfarth Shaw) — Disability Law for Businesses

— The Kode Vox Team