Bug 33012 - Accessibility: Some navigation items in OPAC cannot be accessed by keyboard (search history, log out)
Summary: Accessibility: Some navigation items in OPAC cannot be accessed by keyboard (...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low normal (vote)
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-20 11:41 UTC by Marcel de Rooy
Modified: 2023-02-21 14:08 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: Trivial patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Bug 33012: Remove tabindex from logout button (1.64 KB, patch)
2023-02-20 11:46 UTC, Marcel de Rooy
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel de Rooy 2023-02-20 11:41:27 UTC
Trivial edit. Remove tabindex -1.
Comment 1 Marcel de Rooy 2023-02-20 11:46:56 UTC
Created attachment 146946 [details] [review]
Bug 33012: Remove tabindex from logout button

Note: This is a trivial edit. But there is another logout link
too in masthead with js-hide class and tabindex -1 which is
rather mysterious to me ;)

Test plan:
Login on OPAC.
Try to logout by tabbing to Logout button.

Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Comment 2 Marcel de Rooy 2023-02-20 11:47:19 UTC
Trivial one liner. Self SO
Comment 3 Katrin Fischer 2023-02-20 20:45:57 UTC
It looks like you can also not tab to 'search history' in the same menu as the log out link. Looking at masthead.inc we have a 'ton' of tabindex=-1. 

Another example would be the list menu, that cannot be navigated by tabbing, but you can use 'arrow down'. The same does not work for the 'Welcome...' menu.

This would unlock one option, but it seems to be a bigger issue even in the same menu.
Comment 4 Katrin Fischer 2023-02-21 08:18:09 UTC
I think in terms of accessibility we should investigate this further. I just felt not sure if your solution was the right one as it only fixed one of the items in this menu.

I'll reopen with a different description.