Skip to content

Accessibility improvements when using a screen reader

Albert Vaca Cintora requested to merge work/accessibility-findings into master

Fixes based on the report: HAN_Report_KDE_Connect_Android.pdf

By issue number in the report:

    1. Added a content description to the KeyListenerView.
    1. Marked all headings as headings except in the toolbar, which is a standard AndroidX component and behaves like this in all apps. I opened an issue upstream for this to be fixed there.
  • 3, 6 and 12. Added content descriptions to ImageButtons in the mousepad and presenter plugins. The buttons can be used instead of gestures in the mousepad plugin, which is simpler and faster than using the pass-through mode (issue 12) to temporarily disable the screen reader gestures.
    1. [Unfixed] The colors used come from the device theme, so the contrast is not something we control.
    1. [Unfixed] The screen reader should already provide a way to close popup menus. We could add an extra "close" entry that is not shown unless using a screen reader, but this is not what any app does. Using the back button also closes any open menu.
  • 7 and 11. Added the Button role where missing, except in the sidebar which is a standard component and behaves like this in all apps.
    1. Removed the content description on some cosmetic images.
    1. Added accessible feedback when pairing is requested and after the pairing is accepted, which didn't have any before.
    1. [Postponed] We can make the pairing timeout adjustable but it requires coordination between all the clients (the value is hardcoded), so it requires a bigger effort.

Merge request reports