This week I've been reading up on a11y a lot. I've learnt that auto focus is (generally) bad as it can be very confusing to a screen reader user when your focus is yanked away. Also, over 97% of screen reader users have javascript enabled.
In non a11y news thanks to the post on here I now know you can style your console.log output. Mind blown
I am a fullstack developer specialized in frontend technologies like reactjs. I also love programmimg in go. Currently im working on https://stormkit.io to make developers lives easier.
The part that bugs me is the use of a11y itself. It spells ally, which is cool, but screen readers cannot interpret it. So we created a shorthand for accessibility that isn't accessible.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This week I've been reading up on a11y a lot. I've learnt that auto focus is (generally) bad as it can be very confusing to a screen reader user when your focus is yanked away. Also, over 97% of screen reader users have javascript enabled.
In non a11y news thanks to the post on here I now know you can style your console.log output. Mind blown
That's very nice! React testing library is pretty cool to implement a11y. They force you to write accessible code.
The part that bugs me is the use of a11y itself. It spells ally, which is cool, but screen readers cannot interpret it. So we created a shorthand for accessibility that isn't accessible.