Skip to content
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

Accessibility issues in site-wide search #4867

Closed
marcus-herrmann opened this issue Mar 26, 2021 · 3 comments
Closed

Accessibility issues in site-wide search #4867

marcus-herrmann opened this issue Mar 26, 2021 · 3 comments

Comments

@marcus-herrmann
Copy link
Contributor

More or less by accident (#4812) I saw that there is meant to be a general search feature, which isn't active on the basis of my audit, ocis-a11y.owncloud.works. If this would have been the case, my audit ticket regarding this would be as follows:

Issue

Without a submit button, it is not really obvious how to trigger the search form. Voice Control users can't trigger the submission, for example. Additionally, a submission of the search form causes a change of context. This SO comment describes it in a very complete way: https://ux.stackexchange.com/a/23441. On top of that, the close button is a clickable div, that has no name, no role and no keyboard accessibility.

WCAG test steps:

  • WCAG 3.2.2
  • WCAG 3.3.2
  • WCAG 4.1.2
  • WCAG 2.1.1

Remediation

Baseline

  • Add a submit button (all rules regarding button labelling apply here of course)
  • Make the close button a proper <button> (all rules regarding button labelling apply here of course)

Best practice

  • It also would not hurt to make this div a <form>:

CleanShot 2021-03-26 at 11 20 47

Tip: don't apply role="search" on a form directly, because this would change the role from form to search, and the form role would be "gone again". Think of role search as an fictional native HTML element (<search>).

@pascalwengerter
Copy link
Contributor

pascalwengerter commented Mar 26, 2021

@marcus-herrmann thanks for this!

Could you check out https://owncloud.design/#/oC%20Components/OcSearchBar and see if that already redeems some of the issues (e.g. the close div/button situation)? We'd still need to bring it to the web app, though and make it a proper <form>

As in: We've refactored the components library to a degree, but it isn't integrated into the main repo yet

@marcus-herrmann
Copy link
Contributor Author

marcus-herrmann commented Mar 26, 2021

@pascalwengerter Ah I see. It looks way better!

/edit: Sorry, that was not overly precise: It looks like a prepared remediation, as soon as it hits the app and should close this ticket

@pascalwengerter
Copy link
Contributor

Closing this since it's kinda fixed (and not within the scope of the accessibility audit) for OC10 through the ODS and search isn't implemented for oCIS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants