sarahsporck / Migration-Test-Repository

This repository is used to test the ticket migration from jira to github
0 stars 1 forks source link

IGAPP-866: Navigating with keyboard not possible #3524

Closed jira-to-github-migrator-test[bot] closed 11 months ago

jira-to-github-migrator-test[bot] commented 11 months ago

Steffen Kleinle - 8.12.2021, 16:46:25

From https://chat.tuerantuer.org/digitalfabrik/pl/fohy7zz4ebnqbcciswixwy61mr:

Kommentar: Die Texte und Links auf den Seiten mit den Informationsinhalten können nicht per Tastatur erreicht werden

Our web app should be accessible and therefore usable with screen reader/keyboard. Apparently this is currently not possible. Investigate and fix it.

Environment: - Linked issues:

jira-to-github-migrator-test[bot] commented 11 months ago

Jan Waeckers - 12.1.2022, 15:25:14

The Feeback-Bar aside, the elements of the website are accessable per keyboard (Tab). But what is {}missing is the indication{}, that the element is selected. 

Andreas Fischer - 17.1.2022, 17:09:31

I mean with nvda for me everything seems to be accessible and even telling me what role it is and which item is selected. I just found small things like forms & labels which are not working as expected

Andreas Fischer - 19.1.2022, 16:02:06

<~jan.waeckers> 

this is connected to

Prüfkriterium 2.4.7a Aktuelle Position des Fokus deutlich

https://docs.google.com/document/d/1RjbveyiOIQB0yz5gfxQEeOqxsBzEz5lIj3CeVWYi9MU

I think its getting common to just avoid borders that indicate the focus because its very ugly. We should discuss what.

Additionally i added an eslint rule that forces you to set a role & tabIndex to an interactive element that does not inherit it (f.e. div/span/img used with onClick)

Andreas Fischer - 25.1.2022, 15:32:00

<~steffen.kleinle> this issue can be closed check last paragraph of my last comment!

Already forced by linting rule. For focus/highlight there is a separate issue

Andreas Fischer - 25.1.2022, 16:05:32

already solved