Some comments on format: It would be best if screenshots could be directly attached via the "Attach Screenshot" link at the left side of the page when editing issues. Also, attaching the runnable test-application directly to the JIRA is required for future reference and verification purposes.

Also note that this issue may be resolved by recent work done on ICE-4642, which adds improved keyboard navigation support to the ice:panelTabSet component.

Renderer of this component was was changed. Aria-attributes and keyboard navigation was added. It shoud be compatible with previous versions.

Accessibility for screen readers is only with usage attributes label and icon:
<ice:panelTab label="First card" icon="images/email_mini.png" >

If facets are used for label and icon, accessibilty for screen readers dosn't work. It is not possible to guarantee.

Keyboard navigation:
TAB - only active tab is in tab order.
Left/Up arrow - with focus on a tab, pressing the left/up arrow will move focus to the previous tab in the tab list and activate that tab
Right/down arrow - with focus on a tab, pressing the right/down arrow will move focus to the next tab in the tab list and activate that tab.
Home - with focus on a tab, pressing the Home will move focus to the first tab in the tab list and activate that tab
End - with focus on a tab, pressing the Home will move focus to the last tab in the tab list and activate that tab

The diff file is maked to the actual development trunk.

Review for P02.

Since we are targeting W3C ARIA support for the new ICEfaces Advanced Components in ICEfaces 2.0, we will not be investing further in accessibilty improvements on the existing Components. The new TabSet component will support ARIA roles and keyboard shortcuts:
http://wiki.icefaces.org/display/ICE/TabSet