-
Notifications
You must be signed in to change notification settings - Fork 378
✨(frontend) improve accessibility of search modal for screen readers #1275
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
base: main
Are you sure you want to change the base?
Conversation
000bd17
to
de5958f
Compare
0da1580
to
391261c
Compare
added clearer sr-only translations and aria-hidden for non-essential content Signed-off-by: Cyril <[email protected]>
391261c
to
81f3997
Compare
@@ -180,7 +182,7 @@ export const DocVisibility = ({ doc }: DocVisibilityProps) => { | |||
) | |||
: undefined | |||
} | |||
label={t('Visibility mode')} | |||
label={t('Document access mode')} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why switch from visibility to access ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It was for better clarity, as we’re switching from “edition” to “read-only” it’s essentially an access mode.
I’m open to other suggestions if this wording isn’t ideal :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I approved this PR already, I just had this question: #1275 (comment)
Yes I answer to it just below :D
Sorry the comment was in pending since 4 days.. |
Purpose
Enhance the accessibility of the search modal for screen reader users by using clearer and more explicit translation strings and adding proper ARIA attributes.
improve e2e tests by adding data-testid
issue 966
Proposal