musskigginc
New Member
I have decided to try and make my websites more accessible to screen readers and other assistive technologies. At the moment I'm really focussing on my navigation. Because who wants to iterate through all the items on a menu if the item you really want is nested deep and near the end?So the website I'm working on has an entirely CSS-based dropdown menu which I am augmenting with javascript to make it keyboard accessible and adding aria attributes to help screen readers.My question isGiven that my existing menu is pure CSS, I want to know if I now need to augment my menus with javascript to update the aria-hidden attribute whenever a part of the menu becomes visible? Or is it enough to set it to aria-hidden="true" in the first instance and leave it that way just to indicate the default state to the screen reader?It just doesn't sit well with me that anything that uses pure CSS to show/hide content now needs to be augmented with javascript - it feels like it defeats the whole purpose of pure CSS display toggling.