I recently developed an accessibility scanner called ClearA11y (cleara11y.net) and I'm debating whether I'm addressing a legitimate need or just adding unnecessary features.
It has two main features I'm focusing on:
1. **AI-Generated Code Fixes**: Instead of just flagging issues like "this button lacks accessible text," it analyzes your HTML and offers direct code fixes. For example, it suggests changing:
```html
```
I'm curious—do developers actually utilize these suggestions or do they tend to ignore scanner outputs like this?
2. **Blockchain-Certified Audit Trail**: Every scan is logged on Hedera with a timestamp, offering solid proof that an accessibility check occurred. Is this important for compliance or legal teams? I'm considering scenarios like ADA lawsuits; am I overthinking it?
I'm looking for thoughts from developers working in accessibility or professionals in the field—am I addressing a real concern or just creating features that are unnecessary? There's a free tier available for anyone interested in testing it out: cleara11y.net
1 Answer
How do you know the code updates you propose are actually valid? Do you have expertise in accessibility? The button fix you mentioned isn't the best practice; it could create its own issues. Just curious if you've considered this.
Not an expert myself. That's where AI comes in, suggesting fixes—though I know it has its limitations and doesn’t replace the need for manual checks.