Learning all about ARIA attributes with @tolu_xyz at #AEASF! Some really interesting examples about how you’d indicate to assistive technologies about what’s visually happening on a component.
.@tolu_xyz recommends doubling up in code when using native HTML landmarks, since assistive tech reads them out inconsistently. So even if you’re using <nav> it’s a good idea to also use <div role=“navigation”> to make sure all your bases are covered! #AEASF
It’s important for UX designers to understand how ARIA works, because it’s how nonsighted users will experience the web. Otherwise you delegate that decision-making entirely to devs. @tolu_xyz #AEASF
Overdoing ARIA attributes can make the experience worse than not using ARIA at all. “A role is a promise.” @tolu_xyz recounts the line from Spider-Man: “With great power comes great responsibility.” #AEASF
If you don’t understand how an ARIA attribute works, it’s better not to use it. Always prioritize native HTML tags. Do not change native semantics unless you really have to. Make sure interactive ARIA controls are visible and usable with a keyboard. @tolu_xyz #AEASF
It’s been a long time since I’ve had to implement ARIA attributes myself, but it’s super cool that there’s ways to indicate context to nonsighted users, like “complementary” landmarks for related content! @tolu_xyz #AEASF
The attribute aria-describedby can be useful in a password text field to connect it to its help text, so the help text is read when they land on the password field instead of having to tab over. That’s part of the user’s experience! @tolu_xyz #AEASF
• • •
Missing some Tweet in this thread? You can try to
force a refresh
