hi all, we are designing a prompting playbook for accessibility testing.
as part of this, the specic topics of focus include:
forms testing,
screen reader testing
IOS VoiceOver testing.

if there is any prompt related to the above topics that you have experimented and tested, if possible, kindly share.

it really helps to gather different perspectives.

Thanks for reading and support.

Has your local bank branch closed, and has it affected how you manage your money?

I'm looking to speak to people across the UK for a piece about the closure of high-street banks and the challenges this creates for people who rely on in-person banking.

I'm particularly interested in hearing from people who prefer speaking to bank staff face-to-face, those who feel completely alienated by online banking, and anyone who has seen their local bank branch close in the last few years.

All information shared will be treated sensitively.

This story will be pitched to national press across the UK, as well as relevant regional press, so the case study would ideally need to be named and, if possible, provide a headshot. 

Thank you!

[A story that needs more awareness across the country, and I need your help!]

I am looking to speak to people across the UK who are currently waiting for an accessible home through their local council, or who have experienced a lengthy wait in the past.

I would particularly like to hear about how long they waited, what challenges they faced while waiting, and how their housing situation affected their day-to-day life.

All information shared will be treated sensitively.

As this story will be pitched to national, regional and broadcast media, the case study would ideally need to be comfortable with being named and, if possible, a headshot/photo (If not wanted, that can also be fine)

We're running an independent mobility & accessibility study, and instead of guessing from an office, we'd rather sit down with the people who actually use a power wheelchair every day.

Looking for people in the U.S. who use a power wheelchair and:
🦽 are older adults whose hands make a standard joystick hard to use
🧠 live with a neurological condition (stroke, Parkinson's) affecting hand control
♿ have a disability that makes standard joystick control difficult
👴 are older adults who use a power wheelchair and want to share what matters most when choosing one

What's involved:
• A relaxed in-person chat (~45–60 min), at a time and place that suits you
• We record audio and film hands-on use only — never your face
• Totally voluntary, stop anytime
• Paid compensation (amount in DM) — no medical diagnosis, just your real experience

If this is you or someone you care for, send me a DM 🙏 Sharing is hugely appreciated.

DM me: 1) your city / state　2) your wheelchair type + how long you've used one　3) the hardest part about controlling it

#wheelchair #wheelchairlife #disability #disabilityawareness #parkinsons #strokerecovery #mobility #accessible #accessibility #aging #seniors #eldercare #powerwheelchair #assistivetechnology #paidstudy #researchstudy #US

I manage a handful of small business WordPress sites and most of the owners just want the site to work without learning new tools. With the EAA and WCAG 2.2 expectations coming up, the common gaps are still contrast, font sizing, and basic keyboard access. Anything that needs a developer to keep tweaking usually gets pushed aside. On two of the sites I added onetap because the setup was literally install and activate, then the toolbar was there with the main readability options already working. The statement generator handled the language piece for one of the bilingual sites and the whole thing stayed light enough that page speed didn’t change.

Clients can adjust the toolbar colors themselves so it doesn’t look bolted on, which has cut down on the follow-up questions. The bigger win has been not having to explain custom code every time someone asks about compliance. What tools or approaches have actually stuck for you on smaller sites where the owner isn’t going to touch the code? And how are you covering the keyboard navigation and contrast pieces without turning it into an ongoing project?

My friend was recently paralyzed in a cycling accident, and I'm helping him set up his Android phone so he can interact with the world hands-free, through both Google Gemini and Anthropic's Claude by voice. He needs both apps for different reasons. He's a developer, and most of his programming work happens in Claude, while he uses Gemini more for general interaction and researching health-related questions. So losing access to either one is a real loss of capability for him, not just a preference.

I've hit four recurring technical problems and I'm hoping someone here has solved one or more of them.

One, starting Voice Access hands-free. He's currently in a hospital room with a lot of ambient noise, and Voice Access keeps picking up background sound when left listening continuously. I know how to stop a listening session, but I haven't found a reliable way for him to start one using only his voice, with no hand or button input.

Two, handing off from Voice Access to the AI app. Once Voice Access helps him open Gemini or Claude, I need it to stop listening so his speech goes to the app's conversation mode instead of being interpreted as device commands. Right now the two seem to compete.

Three, launching Claude with a wake word. Gemini works fine as a voice-activated assistant, but Claude doesn't. Android lets me set Claude as the default digital assistant app, but there's no keyword or activation phrase that actually triggers it the way Gemini's does.

"Four, using Gemini as a bridge to launch Claude. As a workaround, I'm wondering if Gemini could be used to launch a home-screen shortcut straight into Claude's voice mode, bypassing Voice Access and the missing wake word entirely. Has anyone tried this or got it working?

Separately, if anyone can point me to a solid guide, video, or community resource on setting up Android accessibility for someone who's recently become paralyzed, generally, I'd really appreciate it. This is new territory for me and I'd rather learn from people who've done it properly than figure it out by trial and error.

Any tips, settings, or tools would mean a lot — trying to make this as frictionless as possible for him while he's dealing with so much else.

Is anyone good at submitting their photo ID for anything related to online verification? Even the SSA wants one to replace a social security card. I would, except until I get the real ID I only have the comission for the blind one they won't accept. On top of that, is the lagistics of it. Ugh. Needed to vent that and wish there were an easier way.

You see two figures quoted for what automated accessibility testing can find, and people argue about which is right. They are both right, because they use different denominators.

Deque's coverage report counts issues by volume. Of all the issues found in their audit data, 57.38% were of a kind that automated rules can detect. Counted by success criteria instead, automation could fully test 16 of the 50 WCAG 2.1 AA criteria. One answer is about how much of the pile you can clear. The other is about how much of the spec you can claim to have checked.

That matters for what a clean report means. WebAIM's Million report says it plainly: "Absence of detected errors does not indicate that a page is accessible or conformant." Their 2026 run found detected failures on 95.9% of home pages, with 56.1 errors per page, up from 51 the year before.

Lighthouse's accessibility score is built on axe-core rules (see the Chrome docs on scoring). A 100 there means the rules that ran found nothing. It does not mean a keyboard user can complete checkout, or that the alt text says anything useful.

How I would use the numbers:

1. Run automation on every pull request. It is cheap and it stops known failures from coming back.
2. Never write "compliant" from a scan result. Write "we found N issues of type X on date Y with tool Z".
3. Keep a short manual list that automation cannot see: focus order on custom widgets, meaningful alternatives, labels that disagree with visible text, a 10-minute keyboard pass before release.

What I could not settle: the exact share of real-world barriers that automation covers. I only have these published datasets, and each has its own method. Treat the 57% as one dataset, not a constant.

Method: I read the Deque coverage report, the WebAIM Million 2026 text and the Lighthouse scoring page side by side, and looked at how each defines what it counts. All three are public; search the titles.

Where do you draw the line between "automation found nothing" and "ship it"?

NV Access is very excited to launch: "Accessibility Testing with NVDA"

This new package includes:

- 'Accessibility Testing with NVDA' training module,

- Printable reference sheets

- Resources for further reading

- A WCAG reference guide

- A badge you can display on your website or in your email.

A comprehensive resource for anyone involved in accessibility testing. Available now from: https://www.nvaccess.org/product/accessibility-testing-with-nvda/

Has anyone had random squares populate in Rise360 when tabbing through a YouTube video when checking keyboard navigation? One square populates in the upper left corner of the video and others populate where the rewind and fast forward icons SHOULD be. The icons are not visible. Used the Multimedia block.

Spent hours and hours troubleshooting. Used iframe and URL…different browsers…different computers, can’t tell if it’s a YouTube issue or Rise issue.

I’m not an expert on either. Any advice?

Trying to carefully not name any names, but IYKYK: how good is the "PDF Remediation Agent" addon by the famous vendor that is the improver of sites? Any pros, cons or neutral observations would be great to hear. Org is considering it for an upcoming renewal.

Not a feedback request, looking for objective experiences from folks who've had real hands on experience with it. TIA!

I created an open website called shwarm.org where people and their AI agents can band together to accomplish lofty goals. One of these is a distributed project whose goal is to caption every video in Wikipedia's top 1000 articles.

https://shwarm.org/w/caption-vital-article-videos

Agents already gathered the videos and drafted captions for the 169 that had none. Now people are needed to watch them, fix them and upload them, and agents and people both can help translate.

Right now it's just for the top 1000 articles but if things go well, there's nothing stopping us from doing them all, or even moving on to other much loftier ideas that we as a community are interested in.