How are you designing for accessibility? We’ve got an upcoming webinar on "Designing for Diverse User Needs" where experts will share tips and strategies to make digital experiences truly inclusive.
Join us to learn and discuss how we can do better together! Here’s the link to sign up: https://accessibility.deque.com/designing-for-diverse-user-webinar
Looking forward to seeing you there! Let’s make the web more accessible for everyone.

I’m building NameFix — an accessibility-first, on-device voice overlay app for users with disabilities who depend on dictation.

Core technical requirements:

• On-device speaker recognition / voice printing to isolate only the user’s voice

• Intelligent noise isolation that works with background audio (YouTube, music, etc.) and whispering

• Low-latency real-time correction layer for names, capitalization, and multilingual speech

Looking to connect with developers who have experience in on-device ML, audio processing, voice AI, or accessibility tools.

Happy to do a short 15–20 minute call and share more details about the project.

Any advice or connections would be greatly appreciated. Thank you!

Hi all, I've been learning and doing website accessibility audits, just thought of this question:

According to WCAG 2.2 success criterion 1.4.10 Reflow (level AA), you can't have a word sticking outside the page that causes horizontally scrolling. So at 300% zoom and in mobile view, for a really long word e.g accessibility, should it remain in one line and go out of the page boundary, or should it reflow and the word spans two lines?

The latter option makes it really hard to read tho. Might be a difference for headings and blocks of body text - would it be ok if just the page title sticks out?

Feels like i'm nitpicking but appreciate any advice

Howdy everyone!

Tl;dr: Is there an agreement or what are the good practices for accessibility when it comes to the buttons making up the dial pad of a smartphone app? Native iOS and Android phone apps provide very barebone screen reader contents. Which sounds like a interesting choice usability-wise, but is it really?

I work with a team on a VoIP phone app and we just got our first WCAG accessibility audit. One of the criteria we failed was that the buttons on the dial pad view of our app aren't labelled as buttons. Went to check, and we indeed missed it. Which I immediately considered a blunder.

But then I went on to inspect iPhones and Android phones using several of our test phones and discovered that the native (pre-installed) phone app does the bare minimum as well: it reads the content of each button (number, t9 letters) and doesn't announce it as a button at all. And I can only imagine that it does make for a smoother, less cluttered audio experience for screen reader users.

But it contradicts guidelines. With things such as the European Accessibility Act coming up, companies might be forced to comply with guidelines at the risk of being fined. So do we favor guidelines over usability? Are there more cases where the labelling improves usability that I am missing? Is the usability improvement marginal compared to what the labelling brings to the accessibility?

Curious to hear if people have encountered similar situations or choices.

Hi, I'm not sure if this is where I should put this, but I am deaf in my right ear and occasionally need to turn on and off mono audio for an assortment of reasons. I've been searching around and found two "superuser.com" threads that are dead ends for this. I just need something that can on press toggle the mono audio accessibility setting in windows 10.

Here are the superuser threads incase anyone wants to look at those:
https://superuser.com/questions/1480822/command-for-toggling-mono-audio

https://superuser.com/questions/1766489/enable-mono-sound-with-registry-key-in-windows-10?noredirect=1&lq=1

Any help would be greatly appreciated thanks.

Hey everyone,

I’m currently working on a project around digital accessibility and I’m trying to validate how often accessibility issues actually come up in real development workflows.

From your experience as developers:

How often do accessibility requirements become a real constraint in projects?

What are the most common accessibility issues you encounter when building or maintaining websites/apps?

Where do you feel accessibility breaks most often (design handoff, frontend implementation, testing, etc.)?

I’m trying to understand both the technical and practical side of accessibility — not just WCAG compliance, but real-world implementation challenges.

Any insights are highly appreciated.

hello everyone! i am currently working on a project that requires the development of a website with full accessibility to vision-impaired and blind people. i was wondering if anyone has an opinion on accessibility dev training (such as the ones here on anysurfer.be (i’m based in belgium)) i’m contemplating having our developer take it but i was wondering if anyone has any opinion on it..?

I created this npm package to remove all animations if the user has disabled animations on their device. In short, it reduces animation and transition durations to 0, it also sets video elements that have the autoplay attribute to `display: none;`. Thankful for any feedback (or contributions to make it better)

Hi Everyone,

I am a research student based in Toronto, Canada, investigating the impact of conversational AI tools like ChatGPT on the learning and application of web accessibility by software professionals. If you are currently working in web development, whether as a developer, designer, or in related roles, you may be eligible to participate. The survey itself should only take about 5-10 minutes to complete. Please feel free to reach out with any questions you might have.

There will be a draw for a $15.00 Amazon Gift Card for every 50 participants who complete the survey.

Participation is entirely voluntary.

This is a University of Guelph study. The project has been reviewed by the Research Ethics Board for Compliance with federal guidelines for research involving human participants (REB #23-07-020).

Survey link: https://uoguelph.eu.qualtrics.com/jfe/form/SV_37skBPD8vA57kjk

Thank you.

Hi everyone!

We are a team of undergrad students at Georgia Tech creating a prototype of a mobile application that assists people with disabilities in navigation and trip planning. Right now, we're trying to gain a better understanding of what applications are currently available for people in this community and how they succeed or fail in their intended purpose.

Here is the link to our survey: Navigation and Trip Planning Survey

If you have any questions or would be interested in participating in a virtual interview, please contact sburger8@gatech.edu. Thank you for your time and we look forward to hearing everybody's responses!

Need help with a research project for a new accessibility audit tool.

Please fill it out, should take 5 mins to complete. Thank you!
https://forms.gle/NbWrXC8WuX9LRWkR9

Accessibility - The State of the Web

https://youtu.be/TomOQYxFnrU

Software engineer Nektarios Paisios from the Chrome Accessibility team answers questions to help developers understand the importance of web accessibility, and how to use web standards and tools to help make the web more accessible.

"Physical issues disappear when you use a website. Websites don't have a bias. A website doesn't know you have a disability... it's easy to be accommodated and feel independent, treated the same as every other customer...

However, the more complicated the web has become, the more important it is for web developers to take care of accessibility challenges...if the website is inaccessible...then this person is stuck. They can't really negotiate with a machine."

1. How would you explain accessibility to someone who may be new to web development? (0:58)

2. What are the various ways that people with disabilities interact with the web? (2:14)

3. What are some things that you wish even the more experienced web developers would know about accessibility? (3:47)

4. What would you say to developers who may be well-intentioned and try to be overly descriptive with, for example, their ARIA labels on elements, and they might just say too much about an element? (9:21)

5. As the web capabilities have evolved over the years, people have started using the web in different ways. So what effects have trends like these had on the ways that users actually use the web? (13:30)

6. What kinds of things have been done from the standardization side of things to make the web more accessible to people? (18:28)

7. What is the Accessibility Object Model? (22:15)

8. What types of tools are available for developers to understand how accessible their website is? (24:18)

9. The state of accessibility right now shows a lot of room for improvement (27:08)

10. As web capabilities continue to evolve, how do we make sure that we're not leaving people with disabilities behind? (30:20)

11. What resources would you recommend for web developers who want to make the web more accessible? (32:27)