-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test 5024: improve accessibility #4099
Comments
Is this only for the react list or does it need to be improved for all lists? |
@fuzzylogic2000 I didn't check the other lists for now. But we should make the new react list accessible. And if that goes together with what is on top of the page and is easy to include, please do so. If completely different issue, just concentrate on the list. |
Note: half fixed, will do safari and focus ring in seperate pull request |
@CarolingerSeilchenspringer cannot reproduce safari issue on my current set up: mac Big Sur v11.6 Safari v 15.0 @khamui can you have a quick check of th focus rings on safari? the firefox issue is something that needs a bit of concept, we currently have 1 focus ring that denotes buttons and one that denotes links (the not very visible one) which is decided by the browser. If we want to change the link focus ring I would like to have some input from @mcastro-lqd as it will be everywhere and I don't want to add focus behaviour without a design. |
Technical Note: should research sematic standard for buttons that are essentially links |
I was checking on Safari v15.0.0 on MacOS BigSur (11.6). It turns out that Apple disables tab navigation by default. Can you check if it is working if you check the option in Safari |
@khamui thanks, that was the solution for safari! |
URL: https://github.com/liqd/a4-meinberlin/issues
user: user without mouse
expected behaviour:
behaviour:
important screensize:
device & browser:
Comment/Question:
I found several issues related to accessibility, different depending on browsers and not all of them strictly related to this story:
do we need to split this issue?
The text was updated successfully, but these errors were encountered: