Talk:Accessibility guide for developers

Hi there, good work on summarizing things for developers. A developers knows best what a fellow needs to works efficiently, so I'll leave the summarizing to you.

There is advice I would like to add about keyboard navigation. I'll write the full explanation here, and let you shorten it as needed. Cheers, Dodoïste (talk) 23:59, 31 July 2012 (UTC)

Keyboard navigation
Ensure that every interaction can be used by both the keyboard and the mouse. This is especially relevant for JavaScript and AJAX events. To test keyboard navigation, use the TAB key to access the interaction, and ENTER to use it.

Mouse event handlers should be accompanied by redundant keyboard event handlers. Only "Onclick" is universal.

TABINDEX should not be used, as it is difficult to use correctly and is annoying to update. The tabulation order should be natural, following the order in the HTML. The search box might be an exception where we want a TABINDEX set to 1.

Note: This issue is found in the Vector skin left navigation menu. TABINDEX is not used correctly: interaction menus come first, and the links they contain are a the bottom of the page.

References:
 * G90: Providing keyboard-triggered event handlers
 * SCR2: Using redundant keyboard and mouse event handlers
 * SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons
 * SCR20: Using both keyboard and other device-specific functions