Help Us Improve Web Accessibility!

Hey Reddit community

We’re developing a new accessibility audit platform to make it easier for businesses and developers to identify and fix website accessibility issues. Your feedback will help us create a tool that truly meets user needs.

This short questionnaire covers:
✔️ The biggest challenges in web accessibility
✔️ Features that would make audits easier
✔️ Your experience with existing tools

It only takes 2 minutes to complete. Your insights are invaluable in making the web more inclusive for everyone.

Take the survey here: https://forms.gle/qx6FKbj5BfGbKhdn9

Hey all! I think you'll find this website super useful. It lets you check the contrast ratio of text/image and background colors on your website, and make sure it follows WCAG: https://venngage.com/tools/color-contrast-checker

Hello!

We are Flippingbook. We develop a web publishing solution and now we are trying to make it more accesible.

It proved to be hard to test it without the help of people who use accessibility software such as screen readers on a daily basis.

I don’t really know where else to find someone, so I decided to ask here if anyone is interested to help.

Our software takes a PDF file and generates an interactive HTML5 publication that resembles a book or a broshure. Since we only provide converting but not the editing functions, we solely rely on the content provided by user, and thus we can’t guarantee that it can be converted to accessible and screen-readable format. Our current approach is to offer an accessibility-enabled PDF for download.

So the main goal for now is to ensure that this PDF can be easily downloaded and used both on desktop and mobile devices using only keyboard navigation and a screen reader.

http://kirillmurashov.com/publication/

UPD: To clarify what we need:

We do not intend to make PDF accessible ourselves – PDFs is what our clients provide and it's their responsibility.

For now we would like to check if this accessible PDF is easy to access for end-user.

So, there is a link to the publication, it has a button that allows to download the accessible PDF. The question is, how easy it is to do that and if there are any obstacles.

Hi! I'm doing a study for my AP Research course about the web accessibility of a group of popular fast fashion websites and would really appreciate it if you guys filled out my survey!! The study is only targeted for those who identify themselves with being differently abled (or having a disability). The survey should only take 5-15 minutes and the presentation of my results will be kept anonymous. Also, it is preferable if you could sign your full name for the consent form as I require some type of identification that the participant consents to be in the study. However, no one besides you, me, and my advisor will be seeing the direct responses from the survey. Please let me know if you have any questions. Also, if you could send this to anyone you know with a disability, that would be greatly appreciated!! Thank you so much! 

Link to Survey: https://forms.gle/6raefFzcYjJ19i9F8

For the next month, I'm working with a small group of developers to build a project for our portfolios, and we'd like to make something impactful. We are considering building some sort of chrome extension that could transform pages you view to be more accessible. What sorts of tools would be most helpful? Are there tools that you wish existed, or exist but could use improvement?

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 folks, I'm facing a problem on all the pages of our website. The IDs of the mobile menu and the desktop menu are the same. Can it be challenged if one of them is display:none or it's not compliant at all?