- This topic has 2 replies, 2 voices, and was last updated 3 years, 9 months ago by
.
-
Posts
-
Hey, I hope you are well.
The search field has a secondary input field used for autocomplete. It’s normally not used, but accessible with keyboard navigation, giving some unwanted results.
Luckily, it’s easily fixed by adding the tabindex attribute to the element.
Quick demonstration screencast at https://www.loom.com/share/6432a3f752664194b1163297f791af5a
From MDN:
A negative value (usually tabindex=”-1″) means that the element is not reachable via sequential keyboard navigation, but could be focused with JavaScript or visually by clicking with the mouse. It’s mostly useful to create accessible widgets with JavaScript.
Note: the demo was made in the Lite edition, but I suppose it’s the same thing in Pro.
Thoughts?
Bjarne
Hey. I made the little addition to the php file, works perfectly. Obviously it will get overwritten at the next update. But as a proof of conecpt?
Bjarne
- You must be logged in to reply to this topic.