The SDLC isn't a timeline. It's a deck of cards. Beth DeConinck reframes how we think about building software, and where accessibility fits in.

bethdeconinck.com/20...

#Accessibility #ProductDevelopment #SDLC #DigitalAccessibility #ThoughtLeadership #A11y

Why you shouldn’t trust the people who built your inaccessible site to fix it You commissioned a website. The agency delivered.

Letting the vendor who built your inaccessible site also fix it funds both ends of a broken cycle. Get an independent audit. Hold them accountable. Build it right next time.

www.linkedin.com/pul...

#DigitalAccessibility #DigitalInclusion #WCAG #A11y #InclusiveDesign

Weekly Reading List April 20 2026 - TPGi — a Vispero company A weekly roundup of links to digital accessibility industry news, posted every Monday. Compiled by Ricky Onsman.

Accessibility is a moving target.

This week’s reading list by Ricky Onsman highlights key signals shaping inclusive design and digital risk. Stay informed, stay accountable.

www.tpgi.com/weekly-...

#Accessibility #A11y #InclusiveDesign #DigitalAccessibility #WCAG #UX #Leadership

Inaccessible PDFs quietly break user journeys and invite legal risk. In 2026, document accessibility is a business strategy, not a checkbox.

www.thedrum.com/indu...

#DigitalAccessibility #InclusiveDesign #DocumentAccessibility #UX #Leadership #A11y #PDF

Accessibility is the Foundation How accessibility shaped every decision in this site rebuild — focus indicators, skip navigation, semantic HTML, ARIA patterns, reduced motion, and dark mode.

Accessibility is not a checkbox. It is a foundation. Julia Solórzano wrote about building it in from the start.

juliasolorzano.com/b...

#DigitalAccessibility #WebDevelopment #InclusiveDesign #A11y #ThoughtLeadership

Same app, different barriers. Android and iOS can fail users in completely different ways. Cross-platform build tools don't guarantee equal accessibility. Test both. Always.

bitvtest.de/en/blog/...

#DigitalAccessibility #MobileTesting #A11y #DigitalInclusion #EAA #Mobile

Keyboard operability – why is it important? (part 3) Mobile apps should also be operable using a keyboard. This third part of our blog series on mobile testing explains why this is important and what role the keyboard plays in accessibility and app testing.

Touch is not the only way people use mobile apps. Keyboard operability matters for accessibility, and most apps still fail at it. Detlev Fischer explains why this cannot be an afterthought.

bitvtest.de/en/blog/...

#DigitalAccessibility #A11y #MobileTesting #InclusiveDesign #WCAG #Mobile

Testing mobile apps – what differs from web testing? (part 1) In the first part of a series of blog posts about mobile accessibility testing, we look at the main differences between testing common web content and testing native mobile apps.

Testing mobile apps for accessibility? It is not web testing with a smaller screen. No DOM, fewer tools, and screen readers rule. Detlev Fischer explains what really changes.

bitvtest.de/en/blog/...

#DigitalAccessibility #MobileTesting #A11y #WCAG #InclusiveDesign #Mobile

Accessibility Snapshot Testing in iOS Snapshot testing is a popular type of regression testing that a lot of development teams are unaware...

Accessibility regressions are subtle and costly. Snapshot testing your a11y hierarchy catches them before users do.

dev.to/steady5063/ac...

#Accessibility #iOSDev #MobileTesting #A11y #InclusiveDesign

Firefox is quietly becoming a game-changer for screen reader users accessing PDFs. But 80% of PDFs online are still untagged. The browser can only do so much. Great read by Andrew Downie.

ozewai.org/blog/tech...

#DigitalAccessibility #DigitalInclusion #PDFs #ScreenReaders #A11y

Building the most inaccessible site possible with a perfect Lighthouse score - Manuel Matuzovic An experiment that proves that automatic accessibility testing is only a first step and that manual testing is vital.

A perfect Lighthouse score ≠ an accessible site. Automated tools catch a fraction of real barriers. Manual testing is non-negotiable.

www.matuzo.at/blog/b...

#Accessibility #WebDev #A11y #UX #FrontendDevelopment #DigitalAccessibility

Sorry to hear this, Billy. Get well soon.

A Beginner’s Guide to Manual Accessibility Testing with Keyboard Navigation Learn the 5 essential keyboard commands — Tab, Shift+Tab, Enter, Spacebar, and Arrow Keys — that developers and designers need to manually test website accessibility for screen reader users.

Automated accessibility tools miss more than you think. Manual keyboard testing closes that gap. Great beginner's guide by Ilknur Eren on SitePoint.

www.sitepoint.com/ac...

#WebAccessibility #A11y #KeyboardNavigation #InclusiveDesign #FrontendDevelopment #WebDev

Strong (likely unpopular among #a11y practitioners) opinion:

In accessibility discussions, stating just the number of a WCAG success criterion (SC) without stating the title (at least once) is as annoying as abbreviations without expanded forms are. Sure, it's not exactly the same; but assuming 1/2

Great call out, and while I tend to lean on using the titles of success criteria, I have on ocassion gone all digits. A great reminder.

A11y 101: 2.5.4 Motion Actuation Shake It Off? Why Motion Controls Need a Backup Plan

Cool motion controls are only cool if everyone can use them. WCAG 2.5.4 says: always offer a UI alternative. Innovation without inclusion is just exclusion.

tarnoff.info/2026/03...

#DigitalAccessibility #A11y #WCAG #InclusiveDesign #UX

Don't Waste Money on an Accessibility Audit - Dennis Deacon Most organizations waste half their accessibility audit investment. Learn why acting on audit findings matters as much as the VPAT itself.

Spending $50K on an accessibility audit but ignoring the remediation guidance? You're wasting half your investment. The VPAT isn't the finish line. The real work starts after.

www.dennisdeacon.com...

#Accessibility #DigitalAccessibility #VPAT #InclusiveDesign #A11y #ProductStrategy #UX

Two SDNY Decisions in One Week Show Courts Are Done Messing around with Questionable Accessibility Litigation Courts in SDNY have been showing their impatience with repetitive, cookie-cutter accessibility lawsuits for years. Two decisions from the Southern District of New York were issued last week.

SDNY just rewarded orgs that do real accessibility work and warned overlay vendors hiding behind fine print. Courts are done with shortcuts. Document everything.

www.linkedin.com/pul...

#DigitalAccessibility #ADA #WebAccessibility #A11y #LegalRisk #Compliance

Accessibility failures aren't a design problem. Designers do the work. Engineering ships something broken. Front-end is a specialism, not a layer. We need to stop pretending otherwise.

gbbns.co/journal/acc...

#DigitalAccessibility #WebAccessibility #InclusiveDesign #WCAG #A11y #WebDev

Accessibility isn't just physical. Cognitive barriers are real. Clear, predictable, low-effort design helps everyone think less and do more.

www.last-child.com/d...

#CognitiveAccessibility #InclusiveDesign #A11y #UXDesign #Neurodiversity #Cognitive #DigitalAccessibility

A11y 101: 2.5.3 Label in Name We all navigate the internet and computers in different ways. Some use screen readers, others keyboard, and some people by voice. Success Criterion 2.5.3 was created to support these diverse method…

If your button says "Submit" but your code says something else, voice control users are lost. WCAG 2.5.3 is about making the map match the territory. Great breakdown by Nat Tarnoff.

tarnoff.info/2026/03...

#DigitalAccessibility #A11y #WCAG #InclusiveDesign #WebDevelopment #WebDev

Compliance is the floor, not the ceiling. Real inclusive design starts with people, not guidelines. Build accessibility in from day one.

tetralogical.com/blo...

#InclusiveDesign #Accessibility #UX #A11y #DesignLeadership

Put aria-hidden=true on decorative SVGs - Manuel Matuzovic I'm a frontend developer in Graz, specialized in HTML, accessibility, and CSS layout and architecture.

One attribute. Huge accessibility win. Always add aria-hidden="true" to decorative SVGs or screen readers will announce them as "Image" or "Graphic." Don't create noise for assistive tech users.

www.matuzo.at/blog/2...

#WebAccessibility #A11y #InclusiveDesign #DigitalAccessibility #WebDev

Why is AI so bad at reading PDFs? One of the most ubiquitous file formats is stumping the major models

AI can write software. It still fumbles reading a PDF.

PDFs weren't built for machines. Fixing that now requires multiple specialized models working in concert.

www.theverge.com/ai-...

#AI #MachineLearning #DocumentAI #AILimitations #TechLeadership

What I Like About WCAG 3.0 - AFixt The W3C published an updated Working Draft of WCAG 3.0 on September 4, 2025, and I’ve spent considerable time pulling it apart. The accessibility community has been tracking this specification since the first public working draft dropped in January 2021, and after years of watching the sausage get made this latest draft finally feels like […]

WCAG 3.0 isn't finished, but the thinking behind it is the best the accessibility world has seen. Outcome-based. Process-aware. Graduated conformance. The future looks right.

afixt.com/what-i-lik...

#DigitalAccessibility #WCAG3 #DigitalInclusion #A11y #WebStandards #WCAG

Everything you never wanted to know about visually-hidden The one where I attempt to answer a question

Is .visually-hidden still pulling its weight in 2026? David Bushell went full rabbit hole on this accessibility staple. Spoiler: it depends. A must-read for every frontend dev.

dbushell.com/2026/02...

#DigitalAccessibility #CSS #WebDevelopment #FrontEnd #A11y

Accessibility isn't a checkbox. It's civil rights in code. Beth DeConinck's article is essential reading for anyone who builds for the web.

bethdeconinck.com/20...

#DigitalAccessibility #A11y #DigitalInclusion #UX #WebAccessibility

Accessible flowcharts aren't optional, they're inclusive design in action. UC Berkeley's guidance is clear: use accessible color pairings, never rely on color alone & always provide a long text description.

dap.berkeley.edu/get...

#DigitalAccessibility #InclusiveDesign #A11y

Getting Developers to Care about Accessibility: Carrots and Sticks Most developers aren't intentionally hostile to accessibility. They just weren’t taught about its importance. Plus, change is hard. Successful change requires understanding what actually motivates people, and applying the right pressure in the right places.

Pleading won't make devs care about accessibility. Strategy will. Incentives + real consequences = culture change. Great read from Sheri Byrne-Haber.

buff.ly/niCqwLu

#DigitalAccessibility #InclusiveDesign #A11y #SoftwareDevelopment #TechLeadership #DigitalInclusion #WebDev #MobileDev

The Enforced Accessibility of the Geolocation Element It's a strange situation where some CSS is disallowed, some is allowed but breaks the button, and some is capped.

The HTML <geolocation> element enforces accessibility and security in new ways, shaping how we handle location permissions and styling in web apps.

frontendmasters.com/blog/the-enf...

#WebAccessibility #HTML #UX #FrontendDevelopment #InclusiveDesign #A11y #DigitalAccessibility