Closed indigoxela closed 8 months ago
So the arrow key might still works for screen reader users. It's a form and it's declared as "application", with an aria-described-by.
Unfortunately I have no idea, how screen readers behave with that combo. Read quite some different infos, now I'm even more confused.
I belief, putting the keyboard navigation help in a visible details element (makes info also available for the sighted), things are slightly clearer. But I'm prepared to revisit this all, if someone familiar with NVDA or JAWS chimes in and helps me to understand.
Currently the builder form uses arrow keys for reordering.
While this works fine for sighted (without mouse), it's hard for people using screen readers, as the arrow keys seem to have a reserved purpose - to navigate on the page.
Think this over for better accessibility.
And the help text for keyboard handling currently isn't visible, which might also be a problem for sighted, who prefer keyboard handling and also for translators.