Explore how to effectively implement the "section" HTML element with aria-label for enhanced navigation and landmark roles, ensuring your content is accessible to all users.
That’s good and all but man is that person a big fan of aria properties.
To be clear, they’re not bad, but they’re a little brute-forcey. There’s often a way to achieve the same purpose without them.
For instance, instead of aria-pressed with buttons, you can just use radio buttons and labels. And your can just put heading elements in your sections instead of naming them with aria properties.
That’s good and all but man is that person a big fan of aria properties.
To be clear, they’re not bad, but they’re a little brute-forcey. There’s often a way to achieve the same purpose without them.
For instance, instead of
aria-pressedwith buttons, you can just use radio buttons and labels. And your can just put heading elements in your sections instead of naming them with aria properties.Yeah. aria-properties are fine for things the framework does but would be a huge undertaking doing yourself. But they do make webapps more brittle.