A List Apart: Articles: Accessible Web 2.0 Applications with ...
Popularity Report
 |
|||
|
|||
|
|||
|
|||
|
|||
|
Rank
URL Tag Cloud
Bookmark History
Saved by 5 people (3 private), first by anonymouse user on 2007-04-22
- Lucychili on 2008-02-19 - Tags accessibility , ajax
- Jonathanb on 2007-09-14 - Tags 2007 , accessibility , ajax , application , applications , article , articles , company , css , for:jordiventurafabra , for:pflores , for:shacker , for:winston_1984 , usability , w3c , web2.0 , xhtml
- Jollyrogers on 2007-06-18 - Tags 15_06_07
- Missiontobe on 2007-04-22 - Tags quickd
- Willbolton on 2007-04-10 - Tags accessibility , html , to_read , w3c , web_standards
Public Sticky notes
For example, currently the only way to give focus to a flickr text input is by clicking on it with a mouse. With tabindex="0", it would become keyboard accessible. Moreover, the tabindex value can be negative. Elements with a negative tabindex can receive focus via scripting, but are excluded from tab order. This feature was introduced by Microsoft in Internet Explorer 5.01 and has been implemented in Firefox from version 1.5 on.
As a reminder, here is a table with the values and behavior of tabindex:
| Can get focus | Tab navigable | |
|---|---|---|
no tabindex |
default (only form elements and links) | default |
tabindex="-1" |
yes | no, authors have to program element.focus() in the event of onkeydown for arrow or other keys |
tabindex="0" |
yes | yes, in the order as elements appear in the source code |
positive, e.g. tabindex="100" |
yes | yes, the tabindex specifies the tab order of elements. These elements get focus before any elements with tabindex="0" or without tabindex. |
Highlighted by missiontobe
Public Comment