Accessibility Test: Flex 3 Components

Test

Open in Own Window | View Source

Preliminary Results

The following results are based on testing with JAWS only. Accessibility is judged based on whether the control can be successfully operated using standard commands and/or instructions provided.

Note that while Window-Eyes 7.1 reads most of the sample in Browse Mode, it does not appear to read anything with Browse Mode off, making it impossible to interact with the interface elements.

Component	Accessible	Issues
Basic Controls
Panel	No	Panel Title not read in Virtual or Forms Mode.
Text	Yes
Image	Yes	Alternate text must be entered in toolTip.
Form	Yes	The Form Heading is read before every label (like an HTML fieldset legend).
TextInput	Yes
TextArea	Yes
CheckBox	Yes
RadioButton	Yes
ComboBox	Yes
List	Yes*	No instructions given; JAWS screen sensitive help (Ins + F1) says "JAWS may not recognize this control".
Tree	Yes*	No instructions given; JAWS screen sensitive help (Ins + F1) says "JAWS may not recognize this control".
Slider	Problematic	Sometimes not recognized at all in Forms Mode; Position sometimes reported to 16 digits (e.g. "7.000000000000001%").
DateField & DateChooser	Problematic	Identified as a ComboBox, but Up/Down Arrow do not work to change selection unless opened; No indication given when calendar is opened or closed; Inadequate instruction given for navigating calendar, changing months, etc.
ColorPicker	Problematic	Identified as a ComboBox, but Up/Down Arrow do not work to change selection unless opened; No indication given when picker is opened or closed.
Button	Yes
Link Button	Yes
Alert	Yes
Navigation Controls
MenuBar & Menu	No	Using Right/Left Arrow to select a menu or open a sub menu causes all content on page to be read.
TabNavigator	Problematic	Tabs read after content in Virtual Mode.
Accordion	No	Accordion labels read after content in Virtual Mode. First accordion label not read in Forms Mode.
Data Grids
DataGrid	Problematic	Identified and reads as List (entire row at a time).
AdvancedDataGrid (Flat)	No	Identified as List. No indication that there are multiple columns or that Right/Left Arrow can be used to move between columns in singleCell selectionMode. Up Arrow from first data row to header row or Right/Left Arrow between column headers causes all content on page to be read.
AdvancedDataGrid (Tree)	No	Identified as Tree View. No indication that there are multiple columns or that Right/Left Arrow can be used to move between columns in singleCell selectionMode. First Down Arrow reads "Column 2 closed"; must Left Arrow to get to Column 1; expanding branch node reads as if focus moved to column 2. Up Arrow from first data row to header row or Right/Left Arrow between column headers says only "No item selected".

Conclusions

• The rudimentary controls (text, image, text field, text area, checkbox, radio button, combo box, button) appear to work as needed, however all the more advanced controls appear to have significant issues.
• While not noted above, the lack of ability to identify/navigate by section headings was a substantial obstacle -- moving between sections of the form during testing required excessive arrowing/tabbing. Similarly, the lack of ability to identify table structure and use table reading commands made it virtually impossible to understand and use the standard DataGrids.
• The are additional serious problems when the Flash Player controls scrolling (i.e., using the "Open in Own Window" link above with the browser sized to be shorter than the Flash object). See Accessibility Test: Flex 3 Scrolling for demonstration.
• The lack of support by Window-Eyes (and other screen readers?) may limit the use of Flex 3 to applications with controlled audiences.