4 ms·
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 ac
by jztan 3y ago
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:
https://www.testparty.co 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=TestParty.pregame 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
- itake 3y agoI 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.
- jztan 3y agoGreat 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.