Hi! Sharing a product after many iterations on its UX (with more rule coverage coming soon).
I stumbled upon this problem when the company I was at faced an accessibility lawsuit and needed engineers to fix them. Though there were accessibility champions, I fell into the category of average engineer who had very little experience with correcting/testing these tickets.
With jargony documentation of accessibility guidelines and bad descriptions from audit, it was very frustrating to work with. I could not easily fix them without seeking help.
My friend Michael and I started working on this problem and are excited to launch:
TestParty’s first product is a VSCode extension called Pregame. It scans your code inside the IDE and provides code suggestions for accessibility violations. In your side bar, you will see why it fails/passes guidelines and gives you some accessibility training in-context. The link below is the direct link to the VSCode Extension:
I know most scanning tools take this route, but I personally only enjoy using scanners that auto-fix my mistakes.
In your example of an image not having an alt text, instead of blocking me from shipping, I'd prefer it if used an ML auto-captioning tool to suggest a caption (and even offer translations) so I can move on with my commit.
Great suggestion! We will include ML-based corrections for individual developer mode very soon. For others, even a sign post is helpful. The translation point is a great one that we are also excited to work on.
This looks nice! I've heard of companies getting sued for accessibility violations. Pricing seems reasonable compared to a lawsuit.
Seems like there are 3 rules you guys are checking for right now. What's next? Also would be cool to see something like AI generated img alt text for user-uploaded images.
We will have AI-suggested corrections in the near future! There are a lot of applications for AI here around structure and understandability of an app for the accessible user. We also plan to increase rule coverage to as many WCAG rules (78 total) as possible, starting with the most common offenders.
7 comments
[ 4.2 ms ] story [ 29.6 ms ] threadI stumbled upon this problem when the company I was at faced an accessibility lawsuit and needed engineers to fix them. Though there were accessibility champions, I fell into the category of average engineer who had very little experience with correcting/testing these tickets.
With jargony documentation of accessibility guidelines and bad descriptions from audit, it was very frustrating to work with. I could not easily fix them without seeking help.
My friend Michael and I started working on this problem and are excited to launch:
https://www.testparty.co
TestParty’s first product is a VSCode extension called Pregame. It scans your code inside the IDE and provides code suggestions for accessibility violations. In your side bar, you will see why it fails/passes guidelines and gives you some accessibility training in-context. The link below is the direct link to the VSCode Extension:
https://marketplace.visualstudio.com/items?itemName=TestPart...
Would love for you to try it out and provide feedback. If you would like to chat, my email is jasonzhetan116@gmail.com
In your example of an image not having an alt text, instead of blocking me from shipping, I'd prefer it if used an ML auto-captioning tool to suggest a caption (and even offer translations) so I can move on with my commit.
Seems like there are 3 rules you guys are checking for right now. What's next? Also would be cool to see something like AI generated img alt text for user-uploaded images.