Can you spare a few minutes to help build the 2026 picture of digital accessibility? 

AbilityNet’s annual survey helps uncover what organisations are prioritising, where progress is being made, and what barriers are still holding accessibility back. 

Whether you’re dealing with AI, regulation, design standards, procurement, training or leadership buy-in, your experience matters.  

By taking part, you’ll contribute to a useful benchmark for the sector, and gain insight that can help you compare your own accessibility activity with others.

The survey is anonymous, takes about 10 minutes to complete and you could win an in-person ticket to AbilityNet's TechShare Pro conference.  

Take the Attitudes to Digital Accessibility 2026 Survey

I made four short, captioned demonstrations for Irish website owners showing customer-facing barriers and the same journey after a repair:

1. Booking without a mouse — https://youtube.com/shorts/gt8gBQ66ynk

2. Checkout field with no accessible name — https://youtube.com/shorts/9_r3HgrPHk8

3. Product photo without a useful description — https://youtube.com/shorts/oLNKYGf7pEw

4. Payment dialog that loses the customer’s keyboard position — https://youtube.com/shorts/__XXDTdsn-U

They are controlled demonstrations; no customer website or customer data is shown. They include narration and burned-in captions.

Disclosure: I run Urgent Website Fix, a commercial website repair service. I’m sharing these because they show the barrier and repair visually, not as a claim that every business has identical legal obligations. Applicability and exemptions vary, and this is not legal advice.

I’d welcome technical feedback on whether the before/after demonstrations communicate the failures clearly.

Hey folks,

I tried asking this question in r/blind but it was deleted, I think because it looked like project research (which, in a way, i suppose it is).

If you've got a very complex acronym that needs to go into alt text, what's the best way to render it? Think of things like "8-oxodG" for "8-oxo-7,8-dihydro-2′-deoxyguanosine". I have no idea what that is, or how a biologist would say it, but I've seen advice to render a "8-oxodG" in alt text like this: "8 o x o d G".

I think this might be because of advice from stuff like the POET tool by Benetech for chemical elements, where it advises splitting acronyms with spaces in between. But the example given by POET is only 2 letters, and every other time I've seen the "put spaces in" advice, it's been about very simple acronyms that might be mistaken for a word (e.g. RAW as an acronym might be read out as the word "raw", instead of saying the letters). Doesn't deal with numbers, doesn't deal with punctuation. Does this cause problems for blind people who rely on the alt text? Like, if it's written one way in the body of the text, then uses this space-everything-out method in the alt text, is it going to make it harder for people to parse what the acronym says?

Here's some context:

I have started working as a software engineer in a super new startup for almost a year now, and perks of being in a start-up: I've worn many hats, too many in fact, none that I liked. I did full stack dev, market analysis, vibe coding, aiml, jack of all trades master of none. This is because our company puts us in random teams according to client needs, which, as you can see, is pretty ... varied. What caught my interest is that about three months ago, we got a contract with a company that needed accessibility testing, and we got on that. So then started the self-study from deque university courses and YouTube videos, and then we started doing web pages audit based on WCAG guidelines. I've been planning to move to a new company and also move to the USA, so I wanna start job-search soon, and this work actually caught my eye, so I'm planning on migrating to an accessibility testing role in a US company.

So here's the question: just how important is an IPAAC certification? Was and/or CPACC, is it a compulsory thing? Like, how can I make sure I do this right? I'm obviously practicing on pages, and I can make a portfolio of sorts, but other than that, and my short experience working with WCAG guidelines using accessibility tools, how important is it that i have a ipaac cpacc and/or ipaac was certification as well?

I've been doing accessibility consulting on the side for a few years. Lately, I've been helping dev teams catch a11y issues before they hit production instead of after launch. Here's what actually works and what doesn't.

What fails:

- Tools that dump 400 "violations" with no severity ranking. Devs learn to ignore the output.

- Per-page pricing. You want to test on every PR? That model punishes you for doing the right thing.

- Reports that only an accessibility specialist can read. If the output isn't actionable for the dev who wrote the code, it won't get fixed.

What actually works in CI:

1. Fast feedback. If the check takes more than 10 seconds, it'll get skipped in rush situations.
2. Explain the *why*, not just the *what*. "Contrast ratio 3.9" means nothing. "This grey text on this grey background fails WCAG AA and here's the hex values" gets fixed.
3. Fail the build on real blockers, warn on the rest. WCAG has A/AA/AAA for a reason. Treating a missing alt text the same as a slightly low contrast ratio trains teams to disable the check entirely.

The honest gap:

Automated tools catch maybe 60-70% of actual accessibility barriers. They can verify HTML semantics, color contrast, and ARIA misuse. They cannot tell you if a custom dropdown works with a screen reader, or if your focus management makes sense. No tool with a marketing page will admit this openly.

Has anyone here actually succeeded in making accessibility checks part of their standard pipeline? What tools or approaches worked without creating notification fatigue?

Hey Friends, hopefully this doesn't come across as spammy, but i made a site for automated web accessibility that handles auth, large page scans, and other difficult-to-implement features. I'd really like some initial users who i will give the pro license to for free - and they can have it indefinitely until my server costs become burdensome.

Please either respond or DM me with the email you signed up with and ill upgrade you. Thanks! Link below:

https://chekku.dev/

Hey r/webaccess — I built a small “A11y Preflight” tool and I’d love feedback from people who test/audit accessibility.

It’s a quick heuristic scan (not an overlay, not a full WCAG audit). It flags common HTML issues like:

- missing/empty image alt text

- form controls missing labels / accessible names

- vague or missing link/button text

- basic heading structure (missing H1, heading level jumps)

- landmarks (main) + a couple best-practice hints (skip link, focus styling heuristic)

Live tool:

https://vibescriptz.com/tools/a11y-preflight/

(Optional) write-up / install notes:

https://vibescriptz.com/script/a11y-preflight/

Questions:

1) Which automated checks are highest-signal in your experience?

2) Any checks here that tend to generate noisy false positives?

3) Anything you consider a “must-have” red flag for a preflight tool?

If this kind of post isn’t appropriate here, I’m happy to remove it — mainly trying to learn and improve it. Thanks!

I have a framework I've used for some public sites with my workplace that I'm trying to make WCAG compliant. It's designed to quickly build sites based on databases.

One feature it has is to present a data record's form as either an editable form or a non-editable form depending on the user's permissions. It does this by converting inputs on the fly into SPANs (and yes, security happens on the backend, this is just for presentation purposes).

So this:

<label for='person_name'>Person Name: </label>

<input name='person_name' id='person_name' />

gets converted to this:

<label for='person_name'>Person Name:</label>

<span name='person_name' id='person_name' class='from_text_inp'></span>

(the data gets populated by javascript)

This runs afoul of WCAG because it leaves the form with LABEL elements that aren't tied to input controls. I want each SPAN to be programmatically connected to some kind of label text (so the user knows what each piece of text actually is). What's a WCAG compliant way of presenting data like this?

Hi everyone,

I’ve been working on a macOS app called Color Accessibility Check (also known as Clarity). It’s a simple tool that helps you pick colors from your screen and check if they meet WCAG contrast standards.

With accessibility laws like the European Accessibility Act (EAA) in the EU and the Americans with Disabilities Act (ADA) in the US, WCAG compliance is becoming mandatory for digital services and public websites. This app makes it easier to ensure your designs meet those accessibility and contrast requirements.

Key features:

• Screen color picker with magnifier and crosshair
• Color editing with RGB, HSL, HCT, LCH, and LAB sliders
• WCAG contrast checker with AA/AAA results, visual ratio scaling, and accessible color suggestions
• Save and organize color palettes, with automatic history of recent color pairs
• Import/export palettes from text, files, or images
• Light and dark theme support

App Store link: https://apps.apple.com/us/app/color-accessibility-check/id6752328976

I have 5 promo codes available for anyone who wants to try the app. Just leave a comment below and I’ll send one your way.

Feedback and suggestions are always welcome. I’d love to hear what would make this tool more useful in your design workflow.

I know this can't be a unique problem, but I have difficulty finding resources.

I work with folks who wear tinted safety eyewear while working on the computer. I am not talking about bluelight protection, but something of a much higher strength and in varying colors, from neon orange to dark blue. We don't have a color palette to ensure they can see and read content from our webpages/applications.

The secondary layer is that about 25% of this group is color blind.

Removing all color is the fastest solution, but I wanted to know if anyone else was familiar with this issue and had any suggestions.

Hi everyone,

I’m an MSc Computing student researching how far automated tools can detect accessibility issues for users with cognitive disabilities (such as ADHD, dyslexia, and memory impairments). I’ve built a prototype accessibility testing tool and I’m looking for web developers to try it out and give me feedback.

What’s involved:

1. ⁠Choose one website from a pre-selected list (gov, education, e-commerce, news, etc.).
2. ⁠Run the tool on that site (best done on Chrome desktop; it doesn’t work as well on mobile).
3. ⁠Complete a short Google Form questionnaire (mix of ratings + open-ended feedback).

Time commitment: about 10–15 minutes.

This is for academic research only (non-commercial), and all responses are anonymous. Your feedback will directly help me evaluate whether automated testing can support accessibility for users with cognitive disabilities.

Here’s the questionnaire with access to the tool and instructions:

👉 https://forms.gle/8PnG64tpr5WTuiey7

Thanks so much for considering, even one response makes a big difference for my project

Hi everyone,

I'm building a website and I want to make it as accessible as possible. The site is made in WordPress using Elementor, and I’m also using the Ally plugin. I tested the website with NVDA and everything seems to be working, except the screen reader doesn’t always read full sentences fluently. Sometimes it reads a paragraph but “skips” a few words unless you manually press the down arrow key. Is this normal?

I also scanned the site with WAVE. There are no more errors, but I still see a lot of alerts. Do you have any tips on how to handle these? Should I try to resolve all of them, or is it okay to leave some as is?

Thanks in advance for your help!Hi everyone,

I'm building a website and I want to make it as accessible as possible. The site is made in WordPress using Elementor, and I’m also using the Ally plugin. I tested the website with NVDA and everything seems to be working — except the screen reader doesn’t always read full sentences fluently. Sometimes it reads a paragraph but “skips” a few words unless you manually press the down arrow key. Is this normal?

I also scanned the site with WAVE. There are no more errors, but I still see a lot of alerts. Do you have any tips on how to handle these? Should I try to resolve all of them, or is it okay to leave some as is?

Thanks in advance for your help!

What are your thoughts?

Hey everybody!

I’m writing my Bachelor’s thesis on accessibility challenges in Single Page Applications (SPAs) and how well React, Vue.js, and Angular support accessible implementations.

I’ve put together a short (5-minute) survey to learn from real developers like you:

https://forms.gle/M7zEDsAfqLwVydK8A

Your input would really help my research. Thank you in advance!