Progressively inaccessible. I like it!
13.02.2026 09:35
👍 2
🔁 0
💬 0
📌 0
Progressively inaccessible. I like it!
No worries. That’s definitely on me reading it wrong.
This is what I’m aiming for:
“Adrian Roselli acknowledges that recent advances in computer vision and LLMs have brought some benefits to image descriptions can potentially help readers distil complex articles into understandable summaries.“
I’ll fix this up tonight in a PR.
I probably misinterpreted that a bit. Apologies.
I mistook “finally be useful” with “better” ☺️
Great job!👏
The 2025 Web Almanac by HTTP Archive has been officially released! 🚀
We would like to thank all of our contributors from around the globe who made this extensive report possible!
Check out the full report here: almanac.httparchive.org
What a ride this has been!
Fantastic work from everyone to get this out!
I've read and re-read the #accessibility chapter as we were getting it ready. Now, it's time to read the other 14!
AI is now firmly part of the accessibility story: tools generate alt text and captions, scan code (for example, GitHub’s accessibility tooling), and help triage backlogs.
But they inherit bias and accessibility issues from their training data.
- About half of images still have either empty alt attributes or alt text shorter than 10 characters
- Roughly 8.5% of alt texts are just filenames
- Use of the native main element reached about 47%
- About 66% of pages use aria-label
- Around 33% of sites now use aria-live
- 67% of sites now override or remove default browser focus outlines
- Roughly 24% of pages have a detectable skip link
- About 35% of mobile inputs are labeled
- Over half of inputs on desktop (53%) and 55% on mobile rely solely on placeholder text for naming
Some stats that might make you go "what" or "shit" or "wow"
- Only about 31% of mobile sites meet minimum WCAG color contrast requirements
- 19% of mobile sites and 21% of desktop sites still restrict zoom or scaling
- About 86% of sites correctly declare a page language
It goes on...
The tooling is there and it's good enough. The legal pressure is real as well.
So the remaining gaps are mostly about governance and the day‑to‑day decisions about what to prioritise.
Overlays are still a thing.
About 2% of desktop sites now use accessibility overlays, but only 0.2% of the top 1,000 sites do so.
The European Accessibility Act is now in effect.
But nothing really changed for the web as a result. It will probably take more time for websites to align.
Or to care.
Anyway, automated tools such as Lighthouse and axe-core are good, but they detect less than half of real-world issues.
Overall, the Lighthouse scores are up. 85/100.
But the same four issues keep showing up everywhere: poor colour contrast, unclear link naming, broken heading hierarchies and missing or meaningless alt text on images.
After going through 244 TB of open-source data provided by the HTTP Archive, we found out that the 2025 #accessibility metrics suggest stagnation where we expected incremental improvement. There's an obvious gap between what’s easy to measure and what’s easy to fix.
bogdanlazar.com/daily/the-bi...
I gotta say though. This thing rarely finds its docking station, it’s loud and it’s slow. The one purchase I regret the most in 2025.
I started renovating our new house with a strict plan. Then all sorts of shit went wrong.
Rigid plans, especially for accessibility, often fail because you can't fully know the problem until you start.
I’d rather stay nimble! You don’t know what you don’t know.
#ProjectPlanning #WebAccessibility
I've got a "don't forget to" list for shipping accessible websites.
It covers everything from heading structure and alt text to keyboard navigation, screen readers and colour contrast.
This helps me make sure everyone can use my site.
#WebAccessibility #DevTips
These are officially amazing!
Workshops need action plans to be effective.
I use "The three ones" exercise to quickly define who does what by when. Participants suggest tasks for one day, one week, one month, then take them on.
It's great for clear next steps!
#Workshops #Accessibility
bogdanlazar.com/daily/effect...
I lost 20kg by taking small consistent steps.
This approach also works for web accessibility: set a vision, break it down, prioritise, keep moving, learn, celebrate and involve everyone. Often, small consistent efforts beat big sporadic pushes.
#WebAccessibility #Consistency
Someone asked about the hardest part of my job.
It's not the tech or the WCAG or the standards. It's the daily grind. Pushing through when recommendations are ignored, explaining things repeatedly and feeling minimal progress.
That's what's truly tough for me.
#Accessibility
Super star! ⭐️ I’ll see about sharing mine
I’ve done something similar, just for VoiceOver. Yours looks much more interesting :) Mind sharing some of the shortcuts?
Some say the sound of fingers hitting the deploy buttons will be heard at 11:59 tonight.
Might break the internet.
You sure you’re in Italy and not the Netherlands?
This is always giving me the feels. I never know if I should renew or not and stresses me the hell out!
I mostly renew, so I guess they work. Damn!
Am I the fool?!
I remember showing someone the <details> element in place of the fancy, and inaccessible, accordion component with a few dependencies they installed from npm.
Blew their minds like I invented the damn thing.
That was a good day.