4 ms·
It takes the same amount of work to use an <aside> or <button> as a <div>. I have never accepted the argument that accessibility is more work. It is the same am
by bevr1337 1y ago
It takes the same amount of work to use an <aside> or <button> as a <div>. I have never accepted the argument that accessibility is more work. It is the same amount of work but done correctly. Aria attributes are only necessary when extending HTML semantics.
- zamadatix 1y agoIn the best (and thankfully pretty common) cases the work to do the accessible answer can be the same, or even less, than the work to do it otherwise. That certainly doesn't extend to all cases though and that's where it can snag. E.g. making complex charts or visualizations accessible to those using screen readers often involves creating a second version of the information only suited for that modality. A ton of other things are a bit in-between, such as prefers-reduced-motion being somewhere between "pretty easy" to "complex" depending on how you implement it in your site but, either case, adding some amount of effort.
- bevr1337 1y agoComplex cases are indeed complex! Data viz is an interesting example since visuals are often misleading and time sinks regardless of ability. It's less effort to provide an HTML table or CSV export than gluing D3 and React together (or whatever stack your team uses). I try my hardest to push back on canvas viz so we're not reinventing every wheel. SVG is easy to extend and make interactive