WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessibility of separate button on search suggestions flyout with Keyboard

for

From: glen walker
Date: Mar 14, 2023 12:40PM

>
> > if there was another way to view all results besides
> > clicking on the "view all" button and that other way supported the
> > keyboard, then technically the "view all" button does not have to be
> > keyboard accessible
>
> Yes, it is possible:
>
> 1. You need to go back to the input search field with the Tab Key or the up
> Arrow Key.
> 2. Then, you need to press the Enter key in the input box to submit the
> form. Pressing Enter Key will send the search form, and the "All Search
> Results Page" will appear.
>

Now it starts getting messy. Is the "functionality" available for keyboard
users? I can see arguments on both sides. Perhaps the functionality is
there but it might not be easily discoverable. If the user doesn't know
how to get the same functionality, then does the functionality really
exist? (Kind of a philosophical question.)

At that point, it seems to be a nit-pick argument one way or the other.
Personally, I would report it as a failure (if the functionality is not
easily discoverable) and let the client decide if they agree or not. In the
end, it's their decision. If they're treating WCAG as a minimal checklist
that they're trying to cover for legal reasons, then they'll probably
decide it's not a failure. I try to avoid clients like that but sometimes
it's not obvious when you sign the contract.



> I would like to point out that technically, making the "View all results"
> button accessible should not be too difficult. However, its accessibility
> will affect the usability of the website.
>

Perhaps I don't know all the details of your actual situation but I don't
see how making the "view all" button keyboard accessible as being a
detriment to the usability of the website.