Accessibility Testing for Mobile

By -
Accessibility Testing for Mobile


SrNo. Test Scenario/Principle Test case Expected Behavior
1 Perceivable  Verify that all the touch controls available within the app are easily identify to reduce the need of zoom in and zoom out  User should be able to read the content and touch control text without using zoom.
2 Verify that the all form fileds are below the label and must contain appropriate label (Portrait view only) Field textbox should be positioned below the associated field label.(Portrait view only)
3 Verify that user is able to magnify the screen through Accessibilty settings. 1. Magnification should be applied on the sceen after triple-tap by user.
2.User should be able to pan vertically and horizontally with 2 or more  fingers (in magnification mode)
4 Verify atleast one of the following is pass
1. Support for changing text size from Accessibility Settings
2. Provide on-page controls to change the text size		 User should be able to change the text size using Accessibility settings or On page controls.
5 Verify the application behaviour after applying - 1.Color Reversion / Color Invert (ios)
2.Grayscale
3.Reduce white point
4.Transperancy
5.Darken Color		 User should be able to use the application properly (display, functionality) after applying said changes.
6 Verify that the  alt or title attributes are available for the content such as a logo or brand name. Brand name or logo should be read aloud with TalkBack (for android) or VoiceOver (for iOS).
7   Verify activating elements via the mouseup or touchend event. Element's associated action should not be triggered
8 Verify that all the buttons/links  are easily accessible by a single hand when the application is viewed in landscape or portrait mode All the buttons should be easily accessible by a single hand when the application is viewed in landscape or portrait mode
9 Understandable Verify that the navigation through the application is structured and arranged consistently. Navigation should be consistant and same function elements should be consistent throughout the application.
10 Verify that all the important information is visible on the page without the need of scrolling All the important information should be visible on the page without the need of scrolling
11 Check Conventional shape: Button shape (rounded corners, drop shadows), checkbox, select rectangle with arrow pointing downwards All shapes should be conventional
12 Check the Iconography: conventional visual icons (question mark, home icon, burger icon for menu, floppy disk for save, back arrow, etc) All icons should be conventional
13 Check the hyperlinks available in the application. All the links text should be underlined and should use different color than that of other text on the page (typically blue color).
14 Check the Conventional positioning: Commonly used position such as a top left position for back button (iOS), position of menu items within left-aligned lists in drop-down menus for navigation The position of the menu items/Back button should be in the left aligned list in drop down menus
15 Verify that instructions (e.g. overlays, tooltips, tutorials, etc.) is provided to explain what gestures can be used to control a given interface and whether there are alternatives.  Instructions (e.g. overlays, tooltips, tutorials, etc.) should be provided to explain what gestures can be used to control a given interface and whether there are alternatives. 
16 Robust Verify that different keyboards are shown automatically when users are entering in information into that field according to the settings Different keyboard should be shown automatically to user when users enter information into that field according to the settings
17 Verify Users can enter information on mobile devices in multiple ways such as on-screen keyboard, Bluetooth keyboard and speech User should be able to enter information on mobile devices in multiple ways such as on-screen keyboard, Bluetooth keyboard and speech
18 Verify that minimum amount of  text entry is required. Select menus, radio buttons, check boxes should be provided wherever possible. Automatically entering known information (e.g. date, time, location) should be provided to reduce the amount of text entry needed

Comments

Post a Comment

Popular posts from this blog

Handling Dynamic Web Tables Using Selenium WebDriver

By -
Image
There are two types of HTML tables published on the web- Static tables : Data is static i.e. Number of rows and columns are fixed. Dynamic tables : Data is dynamic i.e. Number of rows and columns are NOT fixed.Handling static table is easy, but dynamic table is a little bit difficult as rows and columns are not constant. Using X-Path to Locate Web Table Elements Before we locate web element, first let's understands- What is a web element? Web elements are nothing but HTML elements like textbox, dropdowns radio buttons, submit buttons, etc. These HTML elements are written with  start  tag and ends with an  end  tag. For Example, <p>  My First HTML Document </p>. Steps for getting X-path of web element that we want to locate. Step 1)  In Chrome, Go to  http://money.rediff.com/gainers/bsc/daily/groupa Step 2)  Right click on web element whose x-path is to be fetched. In our case, right click on "Company" Se...
Read more

Verify Specific Position of an Element

By -
Verify Specific Position of an Element Selenium IDE indicates the position of an element by measuring (in pixels) how far it is from the left or top edge of the browser window. ·          verifyElementPositionLeft   - verifies if the specified number of pixels match the distance of the element from the left edge of the page. This will return FALSE if the value specified does not match the distance from the left edge. ·          verifyElementPositionTop   - verifies if the specified number of pixels match the distance of the element from the top edge of the page. This will return FALSE if the value specified does not match the distance from the top edge.
Read more

Read it out for TESTNG before going for an iterview

By -
How to run a group of test cases using TestNG? TestNG allows you to perform sophisticated groupings of test methods. Not only can you declare that methods belong to groups, but you can also specify groups that contain other groups. Then TestNG can be invoked and asked to include a certain set of groups (or regular expressions) while excluding another set.  This gives you maximum flexibility in how you partition your tests and doesn’t require you to recompile anything if you want to run two different sets of tests back to back. Groups are specified in your testng.xml file and can be found either under the <test> or <suite> tag. Groups specified in the <suite> tag apply to all the <test> tags underneath. @Test (groups = { "smokeTest", "functionalTest" }) public void loginTest(){ System.out.println("Logged in successfully"); }   How to create Group of Groups in TestNG? Groups can also inc...
Read more