Ticket #3 (closed defect: fixed)

Opened 12 years ago

Last modified 12 years ago

Assigning non default custom class poorly accessible

Reported by: avneesh-singh Owned by: somebody
Priority: major Milestone: Obi Beta 2 candidate
Component: Application Version:
Keywords: Accessibility Cc:
Blocked By: Blocking:
Time planned: 1d Time remaining: 1d
Time spent: 1d Estimated Number of Hours:
Add Hours to Ticket: Billable?:
Total Hours:


Assigning custom class with non default name has poor accessibility for keyboard user.


  1. In a project move focus to an audio block.
  2. Activate Blocks menu and open assign role submenu.
  3. Move down to last menu item i.e. assign custom class in this submenu

with keyboard.

Result: Arrow keys of Keyboard is stuck in textbox provided to enter custom class name. One can jump ahead only by using tab key.

comment: Testbox should not lie in drop down menu as it makes keyboard navigation difficult.

Change History

comment:1 Changed 12 years ago by avneesh-singh

  • Status changed from new to closed
  • Resolution set to fixed

Fixed through phrase properties dialog

Note: See TracTickets for help on using tickets.