Table of Contents
RESUABLE TEST-CASES FOR ACCESSIBILITY TESTING
TEST CASE ID |
TEST CATEGORY |
TEST OBJECTIVE |
PRE-REQUISITES |
TEST STEPS |
EXP RESULT |
TC_BBT_01 |
Content Readability |
To ensure that the application content is readable |
Content exists in the application (AUT) |
1. Launch the application (AUT) |
The application content has to be in a readable and understandable format |
TC_BBT_02 |
Content Readability |
To ensure enough comfortable time for content reading |
Content exists in the application (AUT) |
1. Launch the application (AUT) |
Each screen has to be visible for the time necessary to comfortably read all its information |
TC_BBT_03 |
Screen Repainting |
To validate the correct screen repainting |
application has multiple screens (say more than 4) |
1. Launch the application (AUT) |
1. The application screens has to be correctly repainted, including cases when edit boxes and dialog boxes are dismissed |
TC_BBT_04 |
UI Consistency |
To ensure UI consistency in the application |
application has multiple screens (say more than 4) |
1. Launch the application (AUT) |
The application UI should be consistent and understandable throughout |
TC_BBT_05 |
Ease of use |
To validate the Key layout ease of use in the application |
application should support buttons in the screen |
1. Launch the application (AUT) |
1. The buttons should be easy to use |
TC_BBT_06 |
application Speed |
To ensure good enough application speed in place across the targeted devices |
|
1. Launch the application (AUT) |
1. The application is usable on the device |
TC_BBT_07 |
Error/Warning Message |
To observe the error message displayed in the application |
application has multiple screens (say more than 4) |
1. Launch the application (AUT) |
1. Any error messages in the application must be clearly understandable |
TC_BBT_08 |
Visual Indication |
To ensure there exists a visual indication of the function under execution |
application has multiple screens (say more than 4) |
1. Launch the application (AUT) |
1. Any function selected in the application should start within 5 seconds |
TC_BBT_09 |
Acceptance Of Multiple Input Formats |
To validate the acceptance of input in multiple formats |
application should support for the device which is having multiple input formats |
1. Launch the application (AUT) |
The application has to accept all the input’s correctly in all the supported formats |
TC_BBT_10 |
Response Of The application |
To validate the response of the application to movement or change of alignment of the device |
application should support both landscape & portrait mode orientation |
1. Launch the application (AUT) |
1. The response of the application to movement or change of alignment of the device should not impair use of the application, nor be likely to confuse the user |
TC_BBT_11 |
Spelling Errors |
To ensure no spelling errors in the application |
|
1. Launch application in target language |
No spelling errors has to be present in the defined areas |
TC_BBT_12 |
Error/Warning Message |
To ensure correct and apt content in the error/warning message displayed |
|
1. Launch application in target language |
All text located in the specified areas is shown without any technical display issues that hinder legibility |
TC_BBT_13 |
Required Fields |
To ensure correct application behavior when the required fields are missing |
Data entry fields are available in the application |
1. Launch the application |
Red asterisk(*) and friendly warning message has to be displayed, indicating the missing field entries |
TC_BBT_14 |
Platform Standard |
To ensure proper look and feel as per platform standards |
application supports Android, BlackBerry, iOS, Windows Mobile |
1. Launch the application in each of the Mobile OS supported |
1. application should launch without any error |
TC_BBT_15 |
Confirmation Message |
To ensure the display of ‘save confirmation’ message for data changes |
Content save option must be present in the application |
1. Launch the application |
1. application should launch without any error |
TC_BBT_16 |
Confirmation Message |
To ensure the availability of delete confirmation message |
Content delete option must be present in the application |
1. Launch the application |
1. application should launch without any error |
TC_BBT_17 |
Consistency |
To ensure consistency in the ordering of buttons |
application should have multiple buttons in the application screens |
1. Launch the application |
1. application should launch without any error |
TC_BBT_18 |
Consistency |
To ensure consistency in buttons spacing |
application should have multiple buttons in the application screens |
1. Launch the application |
1. application has to have some consistency in spacing between the buttons |
TC_BBT_19 |
Text Boxes |
To validate the field widths for the text boxes |
Text boxes must be present in the application |
1. Launch the application |
1. application should launch without any error |
TC_BBT_20 |
Onscreen Instructions |
To validate the onscreen instructions in all the application screens |
Instructions must be present in the application |
1. Launch the application |
Onscreen instructions wording should be brief and self-explanatory to the casual user |
TC_BBT_21 |
Narrative Text |
To validate the narrative text in the application screens |
Narrative text must be present in the application |
1. Launch the application |
The narrative text should display at the same location in all the screens |
TC_BBT_22 |
Terminology |
To ensure consistent usage of terminology across the application screens |
|
1. Launch the application |
application has to be implemented with consistent terminology in all the screens |
TC_BBT_23 |
Abbreviation consistency |
To ensure consistent usage of abbreviation terminology across the application screens |
|
1. Launch the application |
The abbreviations should be consistent for all the screens in the application (e.g. Nbr for number, Amt for amount, etc) |
TC_BBT_24 |
Sorting Order |
To ensure sorting implementation in drop down list |
Drop down list option should be present in the application |
1. Launch the application |
1.Drop down list option should be indicated by an arrow mark |
TC_BBT_25 |
application Flow |
To ensure proper work flow in between the application screens |
application should support multiple pages |
1. Launch the application |
application should have the logical flow to destination(page-to-page) |
TC_BBT_26 |
Menu Options Display |
To validate the menu options display in all the screens |
|
1. Launch the application |
1.The menu options should not display in the disabled screens |
TC_BBT_27 |
Keypad Display |
To ensure proper keypad display upon selecting numeric or text fields |
Data entry fields should be present in the application |
1. Launch the application |
1. Numeric keypad has to be displayed |
TC_BBT_28 |
Visual Indication |
To ensure the display of progress bar in between navigation process |
application should support multiple screens |
1. Launch the application |
application should display the progress bar if the screen takes more than 5 seconds to render results/page |
TC_BBT_29 |
Scrolling Bar |
To ensure proper screen scrolling and content display |
application should have screen with huge content to enable scrolling |
1. Launch the application |
The scrolling should scroll the screen content and should leave the screen headers intact, while enabling the user to read/view the content |
TC_BBT_30 |
Labels |
To ensure display of label’s in the application screen’s |
application should support multiple screens |
1. Launch the application |
application should display an associated label for every field on the screen |
TC_BBT_31 |
Exit process |
To ensure proper exit process of the application |
|
1. Launch the application |
application has to have a clean and neat exit |
TC_BBT_32 |
Cursor Focus |
To validate the cursor focus on occurring the error |
|
1. Launch the application |
application should focus the cursor to field in error when the user cancels it |
TC_BBT_33 |
Clear Key |
To validate the behavior of the clear key |
|
1. Launch the application |
Clear key should navigate the user to previous screen |
TC_BBT_34 |
End Key |
To validate the behavior of the end key |
|
1. Launch the application |
End Key should navigate the user to native OEM screen |
TC_BBT_35 |
Font Type Consistency |
To ensure consistent font usage across the application screens |
|
1. Launch the application |
The text font family should match from screen to screen in the application |
TC_BBT_36 |
Font Size Consistency |
To ensure consistent font size across the application screens |
|
1. Launch the application |
The text font size should match from screen to screen in the application |
TC_BBT_37 |
Screen Color |
To ensure consistent screen colors usage across the application screens |
|
1. Launch the application |
The screen color should be consistenct in the application |
ACCESSIBILITY TESTING TOOLS-QUICK LIST
TOOLS |
COLOR BLINDNESS |
CONTRAST RATIO CHECKER |
KEYBOARD NAVIGATION CHECK |
TEXT TO SPEECH |
ACCESSIBILITY CHECK (A, AA, AAA) |
SCREEN READER |
DALTONIZE |
✔ |
|
|
|
|
|
COLOR ORACLE |
✔ |
|
|
|
|
|
✔ |
|
|
|
|
|
|
COLOR ZILLA |
|
✔ |
|
|
|
|
COLOR CONTRAST ANALYZER |
|
✔ |
|
|
|
|
WCAG COLOR CONTRAST CHECKER |
|
✔ |
|
|
|
|
|
✔ |
|
|
|
|
|
READ ALOUD |
|
|
|
✔ |
|
|
NVDA |
|
|
|
✔ |
|
|
JAWS |
|
|
|
✔ |
|
|
MERCURY READER |
|
|
|
|
|
✔ |
LIGHT HOUSE |
|
|
|
|
✔ |
|
WAVE |
|
✔ |
|
|
✔ |
|
WCAG ACCESSIBILITY AUDIT DEVELOPER UI |
|
✔ |
|
|
✔ |
|
AXE |
|
✔ |
|
|
✔ |
|
AXE ACCESSIBILITY |
|
✔ |
|
|
✔ |
|
WEB DEVELOPER |
|
✔ |
✔ |
|
✔ |
|
SITE IMPROVE ACCESSIBILITY CHECKER |
|
✔ |
|
|
✔ |
|
EQUAL WEB ACCESSIBILITY CHECKER |
|
✔ |
|
|
✔ |
|
A CHECKER HELPER |
|
|
|
|
✔ |
|
ACCESSIBILITY INSIGHTS FOR WEB |
|
✔ |
|
|
✔ |
|
ACCESSIBILITY FEEDBACK TOOL |
|
|
|
|
✔ |
|
ACCESSIBILITY DEVELOPER TOOLS |
|
✔ |
|
|
✔ |
|
TOTAL VALIDATOR |
|
|
|
|
✔ |
|