Tabindex on Auto-Nav for accessibility
Permalink
Is there anyway of putting tabindex numbers on the Auto-Nav links?
I've searched in this forum and have done a Google search but can't find anything.
Hoping there will be an answer for this, thanks.
Peter
I've searched in this forum and have done a Google search but can't find anything.
Hoping there will be an answer for this, thanks.
Peter
Hi,
Old post?
Like mine on access keys, but never answered?
The RNIB in the UK do not like tabindex without massive design consideration.
Ready for the quote -
"A prime suspect in the crime of allowing "too much accessibility" has to be the TABINDEX attribute. How many web authors realise that if you give the TABINDEX attribute to just a few form fields or links on a web page, you could ruin the logical tab order for the entire page? I'm afraid the answer is: far too few. To be frank, I've rarely seen the TABINDEX attribute applied without it creating more problems than it solves.
Without the application of any TABINDEX attributes, pressing the tab key takes users from one link or form field to the next, in the order that they appear in the code. In reality this will probably also be the most logical order, as the code usually involves grouping links and field controls into logical divisions.
But, who would use their keyboard tab key to navigate around a web page?
Screen reader users, who may be unable to see the screen clearly enough to recognise anything on it, including the mouse pointer, but whose screen reader will read aloud each link or form control label when it has focus.
Mobility impaired people, may be unable to use a mouse, but they can reach every link and form field on the page using the tab key.
Screen magnification users, who may only be able to see a credit card sized portion of the page, but whose magnified view-port follows the focus, around active regions, as they tab to them.
Technology impaired people, who may have a broken mouse, or perhaps don't have one at all"
Think carefully or access keys
Hey, we all need to think more about accessibility.
Old post?
Like mine on access keys, but never answered?
The RNIB in the UK do not like tabindex without massive design consideration.
Ready for the quote -
"A prime suspect in the crime of allowing "too much accessibility" has to be the TABINDEX attribute. How many web authors realise that if you give the TABINDEX attribute to just a few form fields or links on a web page, you could ruin the logical tab order for the entire page? I'm afraid the answer is: far too few. To be frank, I've rarely seen the TABINDEX attribute applied without it creating more problems than it solves.
Without the application of any TABINDEX attributes, pressing the tab key takes users from one link or form field to the next, in the order that they appear in the code. In reality this will probably also be the most logical order, as the code usually involves grouping links and field controls into logical divisions.
But, who would use their keyboard tab key to navigate around a web page?
Screen reader users, who may be unable to see the screen clearly enough to recognise anything on it, including the mouse pointer, but whose screen reader will read aloud each link or form control label when it has focus.
Mobility impaired people, may be unable to use a mouse, but they can reach every link and form field on the page using the tab key.
Screen magnification users, who may only be able to see a credit card sized portion of the page, but whose magnified view-port follows the focus, around active regions, as they tab to them.
Technology impaired people, who may have a broken mouse, or perhaps don't have one at all"
Think carefully or access keys
Hey, we all need to think more about accessibility.
It would be good for it to have the facility to be able to start from any number and incrementally increase, so for example the top menu would start with tabindex 1 and another menu at the bottom of the page could start at, say tabindex 10, or whatever,
how does that sound?
From Peter