(Filing this for Jookia in #pagure as that person was unable to create a FAS account)

Keyboard navigation and screen-reading of Pagure does not consistently work. At the minimum, elements in the UI cannot be navigated by tabbing through and using arrow keys or enter key to manipulate the UI.

A few things reported:

• The drop downs are not populated correctly for keyboard navigation (sort menu, open PR menu, etc.)
• Some of the elements of the UI are not tabbable for create issue and PR (preview/edit element, attach file field)
• Some of the repo settings panels are inaccessible via keyboard navigation (priorities, roadmap, close status, custom issue fields, tags, quick replies, block users)

It was suggested that the reason for this is that there are poor implementations in the custom widgets to expose them properly for navigation, as well as lacking proper implementation of ARIA properties for browsers and screen readers to take advantage of.