Exclude checkboxes from keyboard access
James Cobban said: The records search user interface includes a checkbox after many text input fields to specify whether the search is to be precise or loose. Placing these checkboxes immediately after the text input field clarifies their purpose but creates extra effort and unnecessary errors when entering a search by demanding that the user press the tab key TWICE after each input field. Most users are unaware of the method for altering the state of a checkbox which has the focus and if they are not paying attention will type an entire field value into the checkbox, where it is ignored. In almost every case a user is going to perform an initial loose search and only start selecting other search options, including clicking on these checkboxes, if the results are too broad. Since the checkboxes are more intuitively set using the mouse, or on a mobile device a touch, there is no need for them to also be accessible to the keyboard. Therefore all of these checkboxes should specify the attribute tabindex="-1" so the browser will skip them when the user hits a tab key.