User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
8mo
So today I needed an interface with a few intentional accessibility errors that I wanted to show for a demo. It didn't need to actually work, I just needed to briefly record the effect of a particular issue. So I used to vibe code it for me. It was perfect! Within fifteen minutes I had an inaccessible interface that didn't work right! Exactly what I wanted! No, but on a more serious note, it was impressive that it did manage to build in exactly the flaws I asked it for (and some bonus other flaws), and it was full fledged enough that I could show the issue I wanted to demonstrate without writing any code myself. I do find it somewhat ironic, though, that this is easily going to become the way I most frequently use AI at work, and it's going to save me a ton of time and effort.
2
9
8
0
User avatar
Pratik Patel @ppatel@mstdn.social
8mo
@fastfinge What tool are you using?
1
0
0
0
User avatar
🇨🇦Samuel Proulx🇨🇦 @fastfinge@interfree.ca
8mo
@ppatel In this case I used lovable.dev. But all the tools have accessibility issues, so I flip between copilot, lovable, and replit.
1
0
0
0

User avatar
Pratik Patel @ppatel@mstdn.social
8mo
@fastfinge I'm considering subscribing to copilot and using it with VSCode to do this kind of thing.
0
0
0
0