Our accessibility guy was doing a review of a site that's near launch and noticed a problem with the soft limit functionality. This was actually on a D7 site with the Facet API module, but the same problem applies to Facets. I figured we should discuss and solve it here first.
The problem is that when using tab navigation to get around the site, the focus stays on the soft limit link. Thus, the focus stays down at the bottom of the list. His initial thought was that the focus should change to what would have been the next item in the list - in other words the first item that was revealed by the expanded div.
I didn't really like that idea very much either. I searched for a best practice and couldn't find one. So I visited a bunch of other sites to test their searches and couldn't find any consensus at all. I found a couple of retail websites that do the same thing Facets does. I found one website that does what he suggested. One retail site had behavior that I sort of liked, where focus was changed to the facet heading. It seemed like it could be another "WTF?" but at least then screen reader users would have an indication of where they ended up. Amazon avoids the problem by opening another page with the full list. A Blacklight CMS site that I checked pops open the full list in a modal window, which is another interesting idea. For the record, the majority of sites I checked didn't have soft limits.
Does anyone else have thoughts about this? Until an official solution can be developed I'm going to add some JS to the site theme that will shift focus back up to the facet heading. My accessibility guy thought that sounded like a decent solution.
Fixed
1.0
User interface
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Created a new patch for this, heavily based on #12 's fixes, with the addition of a `role="button"` within the element (per our accessibility testing). I had issues applying the previous patch as well, so hoping this one gets applied correctly through composer.