What fresh hell is THIS now? - Patrick Lauke
[jakecross] I am currently trying to hide an element that is a visual "spotlight" on the page so when navigating with the keyboard, the user is not read out "spot light"... I have tried aria-hidden and role=presentation and neither of them seem to be working.
Is it down to the screen reader to respect the attributes or am I doing something wrong?
_<
[kylegach] Hi all, I’m new here. I have a question about the nifty “show/hide password” button you sometimes see on a sign in form. Typically, a form is constructed such that you can focus the username field, tab to the password field, then tab to the submit button and hit space/enter. But if the password field has one of those show/hide buttons, how should that be handled in the tab order? I considered just removing it from the tab order entirely, since non-sighted users won’t benefit from that functionality, but that excludes keyboard-only users (and probably others).
I ask because we’re building a form with one of those buttons, and my teammate just accidentally revealed his password to the conference room when his muscle memory and our tab order led him to focus and activate the show/hide toggle rather than the submit button like he expected.