I'm a self-taught Front End & JS Dev and professional learner with accessibility expertise. I'm passionate about breaking down concepts into relatable concepts, making it more approachable.
However, it is my personal preference using classes for styling and not attributes.
One of the wins of using ARIA attributes to style interactive components like this is that the component will never work without the ARIA changes baked in. This may not matter in very small teams or teams where there is across-the-board knowledge about accessibility, but for all other cases, I would highly recommend using the ARIA attributes in the CSS, too.
This was a great post, btw!
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.
I actually got the idea from! They had a very good point!
One of the wins of using ARIA attributes to style interactive components like this is that the component will never work without the ARIA changes baked in. This may not matter in very small teams or teams where there is across-the-board knowledge about accessibility, but for all other cases, I would highly recommend using the ARIA attributes in the CSS, too.
This was a great post, btw!