diff options
| author | Patrick H. Lauke <[email protected]> | 2013-01-15 07:16:33 +0000 |
|---|---|---|
| committer | Patrick H. Lauke <[email protected]> | 2013-01-15 07:16:33 +0000 |
| commit | 370fa45fbe4ee879a626a67bb4df0ec9495102be (patch) | |
| tree | 9aeff7c8aa52f8f20901ddf0695aa74df71fef22 /docs/extend.html | |
| parent | 4503ad7808f6602679ec4b89f00bda30c46505c1 (diff) | |
| download | bootstrap-370fa45fbe4ee879a626a67bb4df0ec9495102be.tar.xz bootstrap-370fa45fbe4ee879a626a67bb4df0ec9495102be.zip | |
Leave tabindex=-1 alone
It seems that, as misguided as I personally think it is, ARIA does
indeed want dropdown menus not to behave as regular keyboard users
expect them, killing TAB/SHIFT+TAB in favor of cursor keys. Fair
enough, the issue I have is then with ARIA, not with bootstrap. I would
sugges thought that if you really do want to follow ARIA consistently,
*any* navigation bar should also become an ARIA menu, further making it
impossible for keyboard users to use TAB/SHIFT+TAB to navigate through
it, and that these changes should be reflected in the bootstrap
examples as well...
Diffstat (limited to 'docs/extend.html')
0 files changed, 0 insertions, 0 deletions