Operational Tests - tab down instead of across (tab ordering ALL forms)

[BrianaParrBaker]

In both HVAC and Water Heat Operational Tests, tabbing moves across the row instead of down the column. A data set follows a column instead of a row, so it would be more use friendly to tab down instead of across.

[fishbaugher]

All forms need to be reviewed for tab ordering. I believe it would be a good idea to follow the tab ordering from v8.x Access forms just because that is the most familiar to users.

[fishbaugher]

In work orders, using the up and down arrows changes the amount in the selected field instead of moving to another field like it did in old WA. I think this will cause some headaches in the transition and we at MVAC would prefer the arrows to move to the next field instead of changing the field

Biana/MVAC

[eckmanwe]

Please provide a clear recommendation. The above appears to request Tab-based navigation on some forms and Scroll/arrow-based navigation on others. Please refine and provide clear and detailed recommendation.

[BrianaParrBaker]

I see these are two separate issues.

For HVAC and Water Heat Operational Tests, a data set follows a column, but tabbing currently moves across the row instead of down the column. Therefore, it alternates between the audit and QCI data set. It would make more sense for tabbing to move down the column instead of across the row in HVAC and Water Heat Operational Tests.

In work orders, using the up and down arrows in old WA would move to the cell above or below. In WAweb, using the up or down arrow changes the value of the current cell. This isn't necessarily wrong, but I do forsee frustration and data entry errors based on the change in functionality. I would prefer the up and down arrows to move to the cell above or below instead of changing the value of the cell.

[fishbaugher]

Perhaps what is needed here is a wider examination of the underlying issue of effective keyboard navigation and data entry. I've changed the name of the issue accordingly.

In v8.x it is possible (and preferable for experienced users) to use the keyboard for data entry on forms. v8.x did require some mouse clicks to search and get to the form, but once focus was on a form, experienced auditors could complete the form just with the keyboard. This includes:

1) Tab navigation field to field: In this case, the tab ordering in v8.x forms should be the guide since much thought and effort was put into the exact navigation ordering.

2) Combo-Box selection: When the focus was on a selector, a key entry would often get you to the exact option desired. In v8.x some thought and effort was put into the spelling of selections just to optimize this type-ahead selection. Again, the v8.x combo box behavior should be the guide.

A side by side comparison example will illustrate: In this case we are trying to select the window type (skylight) and frame type (wood) for a window. Comparing v8 to v10 we have (from focus on window code):

v8.x Tab, sk, Tab, w, Tab (six keystrokes, no mouse usage)

v10

• unavailable on 3/31* I will fill this in when the website is available again.