Why people are not replicating the screen reader experience of native elements in their uselessly custom JS widgets is beyond me. ANyway, just spotted this lovely chatty fake box in the wild. "option <Option_name> focused, 1 of 12. 12 results available. Use Up and Down to choose options, press Enter to select the currently focused option, press Escape to exit the menu, press Tab to select the option and exit the menu." Obviously all of this gets announced for every press in the list of options.
=> More informations about this toot | More toots from jakobrosin@universeodon.com
@jakobrosin I’ve seen this a few times, pretty sure it must be some very popular widget a lot of sites use. Gets even better when it’s implemented incorrectly and the accessibility just says “object object is selected” so you have no idea what you’re doing.
=> More informations about this toot | More toots from pitermach@dragonscave.space
@pitermach Yep, looks like it came from some library to me as well. Its an estonian site, and all the announcement stuff is obviously not translated.
=> More informations about this toot | More toots from jakobrosin@universeodon.com
@jakobrosin Oh, and all of this is going through a live region so if you’re using braille or try to have NVDA/VO/Whatever speak where the focus is it won’t work either.
=> More informations about this toot | More toots from pitermach@dragonscave.space
@pitermach exactly
=> More informations about this toot | More toots from jakobrosin@universeodon.com
@pitermach @jakobrosin Oh, good old React-select. That component has caused trouble for literally hundreds if not thousands of users over the years and should be banned from any and all new projects.
=> More informations about this toot | More toots from tuukkao@dragonscave.space This content has been proxied by September (ba2dc).Proxy Information
text/gemini