Bug 213019

Summary: luci cluster creation gui - usability/accessibility problem with tab sequence
Product: Red Hat Enterprise Linux 5 Reporter: Len DiMaggio <ldimaggi>
Component: congaAssignee: Ryan McCabe <rmccabe>
Status: CLOSED DEFERRED QA Contact: Corey Marthaler <cmarthal>
Severity: low Docs Contact:
Priority: low    
Version: 5.0CC: cluster-maint, djansa, jlaska, kanderso, kupcevic, rmccabe
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-11 23:18:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
The tab order is displayed the numbered text - note how the 2nd set of text fields (hostname/password) is actually accessed last. none

Description Len DiMaggio 2006-10-30 16:25:42 UTC 
Description of problem:
luci cluster creation gui - usability/accessibility problem with tab sequence -
the order does not match the sequence displayed - due to how tables are used in
Javascript. This may cause usability complaints and accessibility issues.

Version-Release number of selected component (if applicable):
luci-0.8-21.el5 (RHEL5-Server-20061027.0)

How reproducible:
100%

Steps to Reproduce:
1. In the 'add a cluster' form, tabbing between text, checkbox, and radio
buttons is not in same orcer (top-down) that the fields are displayed. 
  
Actual results:
The order is confusing.

Expected results:
If a user tabs between fields, the tabbing should follow the logical order
displayed.

Additional info:

See the attachment for an illustration. The numbers to the right of the elipses
show the sequence in which the user moves through the form. When I first saw
this - it took me a moment to realize what happened and to find the currently
active field.
Comment 1 Len DiMaggio 2006-10-30 16:25:42 UTC 
Created attachment 139726 [details]
The tab order is displayed the numbered text - note how the 2nd set of text fields (hostname/password) is actually accessed last.
Comment 2 Len DiMaggio 2006-10-31 16:13:56 UTC 
FYI - notes on usability heuristics provided by duffy:

http://intranet.corp.redhat.com/ic/intranet/RedHatSoftwareDesign.html
Comment 3 Ryan McCabe 2006-10-31 21:17:08 UTC 
thanks for the link. i'll try to incorporate the suggestions, but i'm not sure
it's possible before GA.
Comment 4 Ryan McCabe 2006-12-11 23:18:14 UTC 
I looked at this a little bit today, and it turns out the problem is with the
XHTML spec and browser implementation. The spec tells you to use the order
<thead><tfoot><tbody>, but the browser (I think all of them) computes the tab
indices top-down, in the order it parses the input.

At this point, I don't want to go mucking around with that stuff, trying to work
around the browser/spec bug and risk breaking deploy/manager cluster functionality.