The tabindex attribute is used on mockup1 to impose a tab order through the content. This is not advisable because it makes things awkward for sighted keyboard users, and also more difficult to maintain the code.
For example, the search field is currently multiple tab stops away from the search button. The skip link (intended to help sighted keyboard users bypass header content and move directly to the main content of the page) is so far down in the tab order I gave up trying to get to it using the tab key.
Recommend removing the tabindex attribute, and leaving the tab sequence to be determined by the DOM order of interactive elements in the content.
The tabindex attribute is used on mockup1 to impose a tab order through the content. This is not advisable because it makes things awkward for sighted keyboard users, and also more difficult to maintain the code.
For example, the search field is currently multiple tab stops away from the search button. The skip link (intended to help sighted keyboard users bypass header content and move directly to the main content of the page) is so far down in the tab order I gave up trying to get to it using the tab key.
Recommend removing the tabindex attribute, and leaving the tab sequence to be determined by the DOM order of interactive elements in the content.