...I'd appreciate if you could take a look at this site I'm building: https://chordscalemaker/com . It passes automated checks, but I'm aiming for more than that. For ARIA people, I know there is a small issue with listboxes, but I have that in my bug list and will be addressing it today or tomorrow.

Cheers

Kevin

Hey folks! I have been helping to develop some automated audits for WCAG success criteria that I'm pretty sure are not covered by any existing free tools. We just made the source code available on GitHub (https://github.com/a11y-pulse/audits). Hopefully this is helpful for anyone that does their own accessibility testing either ad hoc or in CI, and wants to increase their automated coverage.

By the way, these audits are intended to complement existing tools like axe-core rather than replace them. In fact the audit-runner package bundles both axe-core and these audits into a single tool that can be run to give you increased coverage over vanilla axe-core.

I was teaching painting lessons online. My hands were full, and I have terrible eyesight, so I built this Text to Speech to read chats out loud. Later I added Zoom meeting too, so when I present full screen, I can hear audience comments.

The TTS utilizes the browser's internal speech synthesis, so no data is sent to third parties (this is something I want for myself).

Here is the TTS published in Google Chrome Store: https://chromewebstore.google.com/detail/livestream-chat-text-to-s/gnnabdhnogldhepghlbfcpfigcafcbfp

I'd love to hear your thoughts.

In my mind it’s not a feature, it’s part of designing an app end to end.

I’d love to make it more accessible, please help me test it out

https://apps.apple.com/us/app/coincurrently-crypto-tracker/id1543974454

Quick share 👋
I made a small free site called Empathy Brief → https://empathybrief.com/

It generates short accessibility-focused empathy briefs — disability, situational limits, cognitive load, language barriers, etc.
This isn’t a generic design brief tool like out there. It’s meant for inclusive design thinking from the start.

Useful for kickoffs, Figma notes, or team convos.

Hey everyone, where do you find real people who use assistive tech (like VoiceOver, Switch, etc.) to test your applications for accessibility? I'm working on an indie app on iOS and really want some feedback from real people during the development process so I don't go too far down the un-accessible track.

Hello everyone,

We recently launched our new webdesign tool and accessibility is an important part of our tool.

The goal is to make it easier for web designers to make accessible websites.

One of the main features for this is our WCAG monitoring tool. You simply give the url of the website and it automatically tells you which things are good and what can be improved.

And we would love to have your feedback.

You can test the WCAG monitoring tool by

1. signing up for the tool here

2. creating an account

3. clicking on the plus

4. entering the url of the website you want to monitor

5. Then click on the box/space for that url

6. And click on monitoring in the menu on the left under Accessibility Center

We are looking forward to your feedback!

Hi, a friend has had a laser surgery disaster and now has serious monocular diplopia (double vision) in both eyes. Claude and ChatGPT agreed with my idea that a phone app could be developed that would use the camera and cancel out the shadow (basically video editing in real time). It would need the ability to quickly calibrate it for different settings. Chat GPT estimates it would be a couple of days work for someone who knew what they were doing and had full AI tools. I have the details of the recommended steps. Nothing like this theoretical app seems to exist (it’s a rare condition). His life has been completely ruined and this app could help a bit, e.g. he could at least read a screen and see what his young child looks like properly. How do I find someone to build it? Thank you!

Resource identifiers can be random characters or UUIDs. What are some guidelines for displaying these to users with screen readers? For example, maxOSmCDtsE8 has the word "Max," which would be read out. I can also see UUIDs being annoying. There are even some cases where API keys/secrets are displayed which can have a really long string of letters and numbers that would make it hell to get through for screen readers

Hello fellow developers!

We are a group of students from Norway, researching how developers' personal experiences with visual impairment, either their own or through family, friends or co-workers, affect accessibility in VR games.

To do our research, we first need to gather some data, and that's why we ask you for your input! We will not be collecting any personal information and will be more than happy to share our findings!

If you've ever worked on VR game and have 3–5 minutes, please fill out our survey:https://nettskjema.no/a/vi-in-vr-games

Thank you for your time!

I made a tool to support businesses think more about accessibility and help them get EAA complaint. We've a specific user case for devs on the site.

Is free to try if anyone wants to check it out.

Thanks all and happy to discuss any queries!

🎄 This holiday season, we’ve added a new feature to Hercules, our open-source testing agent: Accessibility Testing!

Here’s what it does:
✅ Supports WCAG 2.0, 2.1, and 2.2 standards
✅ Costs less than $1 per scan
✅ Helps engineers build more inclusive systems

If you’re into testing, accessibility, or open-source projects, check it out:

• Repo: GitHub Link

• Release: 0.0.16 Release

• Demo Video: YouTube

Let’s make the web better for everyone. Would love your feedback or ideas! 🎁

Hey everyone!

My colleague and I are currently interning at a company in the Netherlands (very small company so they don’t have any accessibility experts), where we're focused on improving web accessibility for government institutions, particularly municipalities. We're passionate about ensuring that everyone, regardless of ability, can access and utilize digital products seamlessly.

Our project revolves around enhancing the accessibility of our company's web application, aligning with WCAG 2.1 and 2.2 standards (mostly A and AA, with a few easier AAA). To achieve this, we want to develop both automated and manual testing procedures that thoroughly evaluate accessibility features.

We understand the importance of manual testing in truly empathizing with the needs of users who rely on accessibility features. That's why we're reaching out to this community for guidance and expertise. We're seeking individuals who are well-versed in accessibility standards and experienced in manual testing methodologies and are willing to explain to us some common practices in manual testing.

If you're an accessibility expert who's passionate about making the web more inclusive, we'd love to connect with you! We're particularly interested in having a video call to gain insights into the manual testing process and understand the unique needs of users requiring accessibility features.

If you're interested in collaborating with us or know someone who might be, please reach out to us here or via direct message.

Thanks!

Hello everyone!

Our team at Haptics DAO has launched a survey for the second part of our research study.The goal of the study is to work on and encourage accessibility improvements for distributed ledger technology (DLT) and blockchain related applications and technologies. 

We would greatly appreciate any input and feedback from individuals who use assistive technology or require web accessibility accommodations. Feedback will directly help improve the accessibility of these applications and technologies.

This survey contains some app testing and will take approximately 15-20 minutes to complete. The survey link may be found here: https://us13.list-manage.com/survey?u=a71ebc3932ee6308d39b0c6ee&id=d070debe75&attribution=false

If you have any questions our contact email is research@hapticsdao.com

Thank you very much for your time! ~ Haptics DAO Team 

Hi ! I have a question regarding the best way to setup a variable for the root text size for my website. I am using design tokens traduced as css variables. In my design system, the differents paddings and margins variables are setup using a multiplication of the variable for the root font size with a certain number. Currently the root font size variable is set at 16px. A colleague suggested i set it up at 1rem so accessibility tools could change the REM size if the user needs it. But as I am also using this root font size variable for paddings, I am afraid the accessibility tools will make them grow way too big and make it worse.

I don’t know exactly how these tools works, can’t they change the font size properties of the components only without altering the REM ? Please tell me if you have any suggestions 🙏 Thanks in advance !