Service Tracking - Interface Accessibility

There are some features intended to improve the accessibility of the WWW user interface. They may be helpful in satisfying WCAG (Web Content Accessibility Guidelines). They're mostly generally useful for anyone.

Titles

Almost all menus and buttons have a "title" attribute, which (usually) causes an explanatory phrase to appear if the mouse cursor hovers over the menu/button.

Tabbing

In the item update page, the tab key can be used to sequence through the page in the following order:

1. the comment input box at the bottom
2. the summary input box just before the transactions
3. the "Update" button
4. any input box or menu that hasn't been set (to other than its default value)
5. whatever is left that the browser selects, typically the remaining input boxes, and possibly the remaining menus, and even links to other pages.

The order is intended to reflect the most common actions. E.g. the first choice not only facilitates adding comments, it's a handy way of getting to the end of the transaction list even if you don't intend to add a comment just yet.

Access Keys

An "access key" is a single key that will navigate to a specific item on a page, however it generally requires additional keys to be activated. Using an access key is browser and architecture specific, e.g. for (recent) Firefox:

These access keys are active in the create and update pages:

It's usually the case that after navigating to a button it can be activated by the "Enter" key.

Labels

Various <input>'s are now referenced by <label>s. This wasn't done (or more precisely, done, then undone) for the RunOn Sentence, which is essentially self-labeled. <label>'s may be overrated, given the performance of at least one screen reader emulator. The "title" attribute seems more useful.