• Resolved simplesteps

    (@simplesteps)


    Hi the plugin is great but some options on it lack accessibility, I am referring to the “live search feature”, first issue is the focus order when a user types in the search input field, it popout the suggested link or drop downs, when the user presses the tab key the focus jumps to the list of links that are been suggested, this breaks the Success Criterion 2.4.3 (Focus Order) since most search has the submit or search button next to the field the focus should go directly to the object next to the input search field, a fix would be to keep the focus order correct when usign the tab key or do not focus inside the suggested box by tab instead by arrow keys.

    The other issue I see is that this dropdown should be announced to screen readers so I suggest an aria-live=”polite” for this 4.1.3: Status Messages

    Hope this helps

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Ajay

    (@ajay)

    @simplesteps

    Thank you for flagging this. I’ve filed a report in GitHub where I track issues.

    https://github.com/WebberZone/better-search/issues/119

    I’ll need to research this a bit more to see how I can implement this. I think the second issue of the dropdown should be straightforward as I’m creating it but need to figure out how I can overwrite the search box as that is generic.

    Please can you monitor the issue above but I’ll prioritise this for the next release.

    Thread Starter simplesteps

    (@simplesteps)

    I’ve added myself as a watcher to the GitHub repo. I forgot to mention that when a user tabs out of the search form, the suggestion box should close, but it stays open. Having it close would help make it more accessible.

    Also awesome you take serious improving accessibility of your plugin, that speaks great about you.

    Plugin Author Ajay

    (@ajay)

    Thank you for the feedback. I’m quite keen to ensure that the plugin is fully accessible, although I will admit that I am not even scratching the surface of this. Hence, I am not only open to feedback on this, but my aim is to prioritise accessibility.

    I’ll mark this forum topic resolved, given the issue out there. Would you be in a position to test a beta release whenever I get that sorted? I tend to release beta versions in GitHub directly.

    Thread Starter simplesteps

    (@simplesteps)

    Yes, sure would be glad to help testing it for accessibility.

    Plugin Author Ajay

    (@ajay)

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.