Opened 14 years ago

Closed 14 years ago

#4428 closed defect (fixed)

Disabled buttons on a toolbar should not be in the navigation order

Reported by: simonjb Owned by: simonjb
Priority: high Milestone: 1.0
Component: Accessibility Version: 0.9
Keywords: Cc: Becky Gibson
Blocked By: Blocking:


Disabled buttons are removed from the tab order on HTML pages. To be consistent, disabled buttons should be removed from the navigation order on a toolbar. We will need to handle buttons that change their enabled/disabled state after the toolbar has been initialised. For example, the undo button on the editor toolbar becomes enabled when there are changes to be undone and it becomes disabled when there are not.

Attachments (2)

DisabledToolbarButtons_UNFINISHED_2.diff (9.0 KB) - added by simonjb 14 years ago.
DisabledToolbarButtons_UNFINISHED_3.diff (7.8 KB) - added by simonjb 14 years ago.

Download all attachments as: .zip

Change History (5)

comment:1 Changed 14 years ago by simonjb

Status: newassigned

comment:2 Changed 14 years ago by simonjb

Discussed on #dojo-meeting 2007-09-17. We will not focus any disabled widgets (including disabled menu items).

Changed 14 years ago by simonjb

Changed 14 years ago by simonjb

comment:3 Changed 14 years ago by simonjb

Resolution: fixed
Status: assignedclosed

(In [10538]) Do not focus disabled widgets. Changed the management of tabIndex: focus is now handled by the container which then passes focus on to its first focusable child. I also took the opportunity of switching to some more compact code syntax: dojo.forEach, this.connect (thanks Bill!) Fixes #4428.

Note: See TracTickets for help on using tickets.