Elements of navigation bar like QSOs are not accessible to users of assistive technology · Issue #1572 · wavelog/wavelog · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This relates to the currently installed publically available demo version as of January 27th 2025.
When examining the Wavelog main page after having logged in with a screenreader, the elements of the main menu like QSOs or Logbook are not accessible to screen reader users in a comfortable way. This is due to the fact that the subentries open up when hovering the mouse over the toplevel items. Activating them as you do by keyboard with normal links when using screenreaders or other assistive technology doesn't work.
It would be great if the normal link destination would also reveal the subentries. This could most likely be done by adding an event handler for link activation that just does what the mounse handler already does.
With kind regards,
Stefan, DK7STJ
The text was updated successfully, but these errors were encountered:
This relates to the currently installed publically available demo version as of January 27th 2025.
When examining the Wavelog main page after having logged in with a screenreader, the elements of the main menu like QSOs or Logbook are not accessible to screen reader users in a comfortable way. This is due to the fact that the subentries open up when hovering the mouse over the toplevel items. Activating them as you do by keyboard with normal links when using screenreaders or other assistive technology doesn't work.
It would be great if the normal link destination would also reveal the subentries. This could most likely be done by adding an event handler for link activation that just does what the mounse handler already does.
With kind regards,
Stefan, DK7STJ
The text was updated successfully, but these errors were encountered: