1. Load http://www.mozilla.org/access/dhtml/button. There is a description associated with the entire groupbox, as well as a specific description associated with the button.
2. Test both tabbing forward or backward through the groupbox.
3. When any control is focused inside the groupbox, where focus was previously outside of the groupbox, the description for the entire groupbox should be read by JAWS.

Note: the description is exposed via accDescription as well as DESCRIBED_BY/DESCRIPTION_FOR relations (via accNavigate currently, will also get IAccessibleRelation support in FF3).

1. Load http://www.mozilla.org/access/dhtml/tabpanel, http://www.mozilla.org/access/dhtml/tree or http://www.mozilla.org/access/dhtml/spreadsheet
2. Tab to one of the widgets
3. Notice that Enter doesn't turn on forms mode

These are just a few examples of new ARIA controls that need to handle this. JAWS will need a different method to determine when to allow Enter = forms mode. Because of ARIA, a blacklist might work better than a whitelist (don't use Enter for links or buttons -- things that use Enter as a trigger). Alternatively, JAWS will need to support any MSAA or IA2 role in a web page. It seems that JAWS may be swallowing the Enter key in some or all cases. Perhaps it is trying to fire doDefaultAction().

From Frank on 7/5/2007:

1. Tab Panel - I do find that pressing Enter on a tab in this screen turns forms mode on. Then I am able to arrow left and right to display other tabbed pages. Then I can press the PC Cursor key to turn forms mode back off and use the virtual cursor to read the rest of the page.
2. Tree - I can focus on the tree with the JAWS virtual cursor and press Enter. Forms mode is on and the tree seems to have focus as it has a dotted line around it, but no item is highlighted, so arrowing around has no effect. I can't seem to get it to work correctly, even if I click something first. The same seems to be the case without JAWS. If I tab to the tree, nothing gets highlighted. Don't know if that's normal or not.

1. Load http://www.mozilla.org/access/dhtml/spreadsheet
2. JAWS still uses the "MozillaDocumentWindowClass" , to trigger doc reading -- JAWS needs to recognize the root MSAA role for the content window. If it's ROLE_DOCUMENT then document reading mode should be the default, otherwise forms mode should be (although watch the READONLY flag -- if it's clear that means it's an editable document).

It would be better if JAWS completely removed use of the window class usage for Firefox support. Using the role is a better way of determining that forms mode should be on by default (although document reading should still be available). This would also help with XUL-as-content (about:config is one example that seems to be hardcoded into JAWS). To find the content window, take the top level window's OBJID_CLIENT root accessible, and use accNavigate with the EMBEDS relation.

An example of AR-3 through XUL as content is available, where JAWS reads incorrect labels.

1. Load http://david.atrc.utoronto.ca/aria/errorAlert.xhtml
2. Tab to one of the entry boxes, enter invalid data (such as nothing),
3. You will notice that the error message "error: entry must be an integer value" is read twice.

1. Load http://www.mozilla.org/access/dhtml/maincontent
2. Notice that JAWS has no quick way of navigating to the roles.

Check the XHTML Role Attribute Module and the WAI-ARIA roles for a full list of navigation landmarks that may be useful for JAWS users.

This is a larger feature request that requires taking a look at the live region report and test cases, and implementation discussions with Aaron

• Do not use OSM. This requires using the IAccessible2/IAccessibleText/IAccessibleHyperText interfaces
• Caret tracking
• Font, color and emphasis support
• Deal with embedded objects such as tables and images
• Read line by line
• Other support on par with Microsoft Word

• STATE_REQUIRED = STATE_ALERT_LOW
• STATE_INVALID = STATE_ALERT_HIGH
• STATE_CHECKABLE = STATE_MARQUEED

Or, if you want to use IA2 states then wait until Firefox 3 to support those.

Example: Spreadsheet with menubar

Two problems:

1. When an ARIA menu becomes active JAWS should allow menubar navigation instead of using the arrow keys for the virtual cursor
2. Do not send an extra down arrow key when a menu item gets focused -- this is currently focusing the second menu item when the user enters a submenu.

The popup menu only speaks the label properly when Ins+Z is used to turn Virtual PC cursor mode off. It does not work in either forms mode (by pressing Enter in a textfield) or with Virtual PC mode on. Menus should work no matter what, based on the menu events having been fired.

Example: Spreadsheet with menubar

Two problems:

1. When the user traverses the spreadsheet, they should be able to change col/row header reading modes (e.g. read column header, row and col header, row or col header, row header only, nothing, etc.)
2. As the user navigates it should read the "cell" so that users know they can navigate up/down and left/right