Originally posted on www.a11ywithlindsey.com.
When I first wrote my post about JavaScript and Accessibility, I promised I would make it a series. ...
For further actions, you may consider blocking this person and/or reporting abuse
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!
True! I just never forget, but I definitely like the idea of forcing people to deal with it 😃
Great post, as always, Lindsey 🙂
Great post, thanks for sharing! I really like the code snippets that show what's changed.
Really glad it helps you!
Going things step by step to highlight what changes fixes which issues really helps me learn why I am doing the thing 😁
Great material!
Such a great post! I'm thinking of spinning up an example via a React component and seeing how it can be implemented there :)
really nice post, Is using
detailelement for accordation do any harm for accessibility or it's less used just because of low browser supportPart of accessibility is being robust. In my opinion, this means support of browsers AND assistive devices.
Highly recommend giving this a read! developer.mozilla.org/en-US/docs/W...
If I remember correctly HTML has built in support for accordions natively (without JS!) But I don't remember how, or what tags were used for it. If anyone can find it, I'd be grateful.
It's the
<details>tag. It doesn't have full support which is why I went through this, but I included the reference in the "Adding the ARIA attributes" section!Prefect