Test plans for (manual) testing of various widgets.
Dialog
Dialog Specification
Keyboard Testing
Full keyboard support is available only in Firefox 2 (Window and Mac), and Internet Explorer 6 and 7 (Windows).
Set focus via the keyboard to a trigger which opens a dialog and press enter. Verify the following:
- The dialog opens and focus is in the dialog title
- Pressing tab key moves to the next focusable item in the dialog (if any).
- Continually pressing shift-tab (before having set focus to the last focusable item in the dialog) will move focus back to the dialog title and focus remains in the dialog title. Until focus has been given to the last item in the dialog - pressing shift-tab will not work to cycle backwards through items in the dialog. Focus should remain in the dialog title as shift-tab is pressed.
- Continually pressing the tab key will cycle focus though all of the focusable items in the dialog, back to the dialog title and then through the focusable items in the dialog again - focus remains in the dialog box.
- Once focus has been cycled forward in the dialog box via the tab key, pressing shift-tab should cycle focus backwards through all of the focusable items in the dialog, back to the dialog title and then back through the last focusable item in the dialog box. Focus remains within the dialog box.
- The close icon in the dialog title is not in the tab order.
- Pressing escape closes the dialog box
- When the dialog box is closed, focus returns to the trigger element which opened the dialog
- Focus remains in the dialog and focus cannot be given to other elements in the page via the keyboard or the mouse
Mouse Testing
Click on the trigger element which opens a dialog. Verify the following in all supported browsers:
- The dialog opens and focus is in the dialog title
- Clicking outside of the dialog does not close the dialog.
- Clicking on a focusable element outside of the dialog does not give focus to that element. Focus remains in the dialog and focus cannot be given to other elements in the page via the keyboard or the mouse.
- Any focusable elements in the dialog can be given focus via the mouse.
- Clicking on the close icon in the upper right hand corner of the dialog, closes the dialog.
- Once the dialog is closed, all focusable elements on the page can be focused / activated via the mouse.
- Whe the dialog is closed, focus returns to the trigger element which was used to open the dialog.
Visual Testing
- Verfiy that when the dialog is displayed the color of the page contents below the dialog is dimmed to indicate that it is not active.
- When the page is scrolled, the dialog scolls with the page and the entire background of the page remains dimmed.
- When the dialog is closed, verify that the page color returns to the original state.
- When the font size is increased by 200% the dialog is still usable. Note that since the contents of the dialog widget is provided by the Web author not all text content my resize correctly.
High Contrast Mode
On a Windows machine, turn on high contrast mode via Control Panel, Accessibility Options, Display. Invoke the dialog and verify the following in both Firefox 2 and Internet Explorer 6 and 7:
- The background of the dialog is solid, the information that is below the dialog is not visible. Note there there is a bug in Firefox version 2 and earlier and the information below the dialog will be visible. This should be fixed in Firefox 3.
- The character 'x' appears in place of the close icon on the right hand side of the dialog title area.
- The dialog title text is visible. Note that since the contents of the dialog widget is provided by the Web author, high contrast issues may exist within the dialog contents that are not related to the Dijit Dialog Widget.
Screen Reader Testing
Use the keyboard to navigate to the trigger element which opens the dialog and press enter. Verify the following:
- Focus goes to the dialog title and the screen reader speaks the title and announces the role as "dialog"
- All keyboard tests pass when run with the screen reader operating. Note that the responsibility for correct screen reader operation of the dialog contents lies with the Web author.