Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So either fix it by changing the legislation, or fix it by changing the FOSS software... or do the only thing you can actually do right now which is implement websites in a way that's most likely to consistently work well with existing a11y solutions.


Yes sir, thank you sir, I will never complain about stupid laws again, sir.

Is this how you want these discussions to go?


> complain

I guess at some point this button gets a bit worn out and I start wondering what pushing the "do something about it" button will do.


You can implement your websites with accessibility in mind while also acknowledging its ridiculous how every web developer has to spend time on that because screen readers are terrible, and responsibility somehow got shifted to every web developer ever instead of the handful of companies making screen readers.


I don't loop within loops, I free memory after I allocate it, and I add aria tags to html elements. I don't really see the big deal, just seems like a normal part of the job.


If you just do stuff without reflecting on why it's necessary that's... odd. Two of these examples have actual reasons on why they're necessary, the third is because screenreaders are crap.


I'm not trying to be difficult, but how is it any different than matching what an HTML parser (such as a web browser) expects by making sure you close your tags?


Excellent example because web browsers will render most documents just fine if you don't close your tags. Because they care about being compatible with websites that aren't perfect, and they consider it their job to render all websites that exist. Instead screen readers expect you to change your website instead of working with what's already there.


And yet we close our tags anyway, so even if screen readers are better, we wouldn't change our behavior. So I still don't get it.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: