Upload TestCasesforModel.csv
Browse files- TestCasesforModel.csv +22 -0
TestCasesforModel.csv
CHANGED
|
@@ -35,3 +35,25 @@
|
|
| 35 |
33,"Ensure that any auto updating content that starts automatically and is provided with other content provides a method for users to pause, stop, hide, or to control the frequency of the update.","Open the web application in the browser. Check for visual elements which update or refresh automatically without user input (i.e., auto scrolling carousels, auto play videos, chat windows which update when new messages come in). Verify that the user can stop or control update/refresh frequency with a pause button or similar control. These controls must be reachable and usable via keyboard."
|
| 36 |
34,"Do not create hardware, content, products, services, or tools that are likely to cause seizures due to UI or content that flashes at a rate greater than 3 times per second.","Open the web application with a browser. Check the web application for videos or blinking/flashing content. Verify If any such content is found, use the Photosensitive Epilepsy Analysis Tool (PEAT) to ensure visual content blinks 3 or fewer times per second."
|
| 37 |
35,"Expose visual groupings and the semantic structure of controls and content programmatically so that users can identify and navigate to, or through, them. Additionally, provide ways for users to activate, or navigate directly to, controls and content with as few interactions as possible (for example, they can bypass UI elements by using keyboard shortcuts or link to content links).",Open the web application in the browser. Identify repetitive elements on the page. Verify that user can bypass these repetitive blocks of content and controls using navigational elements.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 35 |
33,"Ensure that any auto updating content that starts automatically and is provided with other content provides a method for users to pause, stop, hide, or to control the frequency of the update.","Open the web application in the browser. Check for visual elements which update or refresh automatically without user input (i.e., auto scrolling carousels, auto play videos, chat windows which update when new messages come in). Verify that the user can stop or control update/refresh frequency with a pause button or similar control. These controls must be reachable and usable via keyboard."
|
| 36 |
34,"Do not create hardware, content, products, services, or tools that are likely to cause seizures due to UI or content that flashes at a rate greater than 3 times per second.","Open the web application with a browser. Check the web application for videos or blinking/flashing content. Verify If any such content is found, use the Photosensitive Epilepsy Analysis Tool (PEAT) to ensure visual content blinks 3 or fewer times per second."
|
| 37 |
35,"Expose visual groupings and the semantic structure of controls and content programmatically so that users can identify and navigate to, or through, them. Additionally, provide ways for users to activate, or navigate directly to, controls and content with as few interactions as possible (for example, they can bypass UI elements by using keyboard shortcuts or link to content links).",Open the web application in the browser. Identify repetitive elements on the page. Verify that user can bypass these repetitive blocks of content and controls using navigational elements.
|
| 38 |
+
36,"Provide informative, context sensitive page title values. The title of a page or document must provide information specific to the currently viewed page or document.","Open the web application in the browser. Check these tags for each page, <title>Description of the page</title> OR Check the page title in the toolbar. Ensure the title adequately informs the user to what page they are visiting. Along with Page titles we also need to verify Alert/Dialog/Windows title as well iframes should also be verified for availability of name/title attribute with relative values."
|
| 39 |
+
37,"Support a focus order that is aligned with the meaning or operation of the user interface (UI). If the navigation sequence is independent of meaning or operation, then align the focus order with the flow of the visual design.","Open the web application in the browser. Verify by pressing Tab repeatedly to move through the page interactive elements. Ensure all interactive elements (links and form fields)s receive Tab focus in a consistent, logical order (generally left to right, top to bottom). Verify non interactive elements (such as plain text) do not receive focus in this way."
|
| 40 |
+
38,"Whenever possible, provide link text that identifies the purpose of the link without needing additional context.","Open the web application in the browser. Examine each link purpose (description) in the web application. Ensure each instance of link text (alt text, in the case of graphic links with no link text) identifies the purpose of the link without needing additional context. (Avoid link text such as See All, Click Here, Buy Now or Learn More)."
|
| 41 |
+
39,Provide an opportunity to navigate in more than one manner.,"Open the web application in the browser. Verify the web application includes multiple elements which ease keyboard navigation through its pages and elements and also there are ways for users to activate, or navigate directly to, controls and content with as few interactions as possible. "
|
| 42 |
+
40,"When headings and labels are used, they must describe the topic or purpose of the element or content that they pertain to. Headings and labels must be unique unless there is sufficient context to allow users to differentiate between duplicated headings or labels. Ensure headings and labels are descriptive and unique.","Open the web application in the browser. Verify all headings contribute to a heading structure which forms a concise, hierarchical outline of the page contents. Avoid using headings to make text appear large or prominent (use CSS classes for presentational styling). Verify all headings and labels on the page are unique and accurately describe the content they pertain to."
|
| 43 |
+
41,"Provide a visual focus indicator to ensure users can orient themselves and track their navigation through a task, scenario, or content.",Verify each focused item receives a dotted outline or other high contrast visible highlight to make it obvious where browser focus is. Verify Focus indicator is distinguishable by user.
|
| 44 |
+
42,"Ensure that content developers provide information in the Web page that user agents need to present text and other linguistic content correctly. Additionally, expose the language for each passage or phrase that differs from the default language.","Open the web application in the browser. Access the web application source code. (For web properties, right-click and select Inspect Source). For web properties, ensure the opening html tag includes a lang attribute matching its desired default language."
|
| 45 |
+
43,"Ensure that user agents can correctly present content written in multiple languages. Additionally, expose the language for each passage or phrase that differs from the default language.",Open the web application in the browser. Verify if any localized language is used in web page that language element should have lang attribute with specific locale w.r.t that language.
|
| 46 |
+
44,Avoid forced focus changes that are not initiated by the user. Ensure all focus changes that occur are a result of user action and that the user expects the change.,"Open the web application in the browser. For each interactive element, Verify that user can use the keyboard to navigate into it (usually with Tab and Shift+Tab), through all its contents (Tab and Shift+Tab or arrow keys), and out of it (Tab and Shift+Tab, Esc key). Ensure the web application does not refresh or open a new window as a result of this navigation."
|
| 47 |
+
45,"Ensure that when a user enters data or information, there are predictable effects. Ensure an ATs default mode is not impacted.","Open the web application in the browser. Locate each element of the web application whose settings can be change or which can accept user input. Verify that setting changes to these elements do not automatic changes of context in the web application unless the user has been advised of the behavior before using the component in question. (i.e., the <label> element for a language selector drop-down should include the phrase Press up or down arrow to change page language)."
|
| 48 |
+
46,"Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.","Open the web application in the browser. Check the web application for navigational components which recur across numerous pages/views of the web application. (i.e., a menu bar common to all pages in a site). Verify the contents of these components occur in the same order across all pages/views of the web application."
|
| 49 |
+
47,"UI components that have the same functionality must visually appear, behave, and be identified programmatically in a consistent way within a product, service, or tool for a specific platform. Ensure consistent identification of functional components that appear repeatedly.","Open the web application in the browser. Identify each type of UI component present in the web application (i.e., links, buttons, text edit fields, combo boxes, etc.). Verify for each component, ensure all instances of that component look, function, and are programmatically identified in the same manner. (i.e., all links in a given page may be blue and have underline decoration, or all menus have the same styling and functionality.) Links, menus, menu items, buttons and plain text should all be styled to look different from one another."
|
| 50 |
+
48,"If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. Make sure users are aware that an error has occurred and can determine what is wrong.","Open the web application in the browser. Check the web application for elements which include input validation. Verify each validation error message describes the error, tells the user where the error occurred ."
|
| 51 |
+
49,"When user input is required, provide instructions or labels describing necessary input and expected data formats to prevent validation errors. Simple instructions or cues for entering input must be provided.","Open the web application in the browser. Check for elements which require user input, such as form fields. Verify that each such field/element has text beside it or a <label> tag which conveys how to interact with the element. In the case of <label> tags, ensure that a for attribute is assigned with the correct ID of the form field in question. Labels is one way of mapping input field with its label."
|
| 52 |
+
50,For all detected input errors after identifying the location where the error occurred and describing the error in text provide users with actionable suggestions for correcting it.,"Open the web application in the browser. Check the web application for elements which include input validation. Verify each validation error message describes the error, tells the user where the error occurred and offers a suggestion for fixing the error (i.e., Invalid email entered in the personal email field. Please check your email and try again)."
|
| 53 |
+
51,"In services and applications, user input that results in a legal commitment, financial transaction or modification to user-controllable data in data storage systems must be able to be reversed, verified or confirmed.","Open the web application in the browser. Check the web application for input elements which can result in a legal commitment, financial transaction or modification of user controllable data in data storage systems. Ensure each element with this potential has a method for the user to reverse, verify or confirm the change agreed to. (i.e., a checkout verification page before a purchase is made on an ecommerce site or an unto option for changes just made to personal data)."
|
| 54 |
+
52,"Ensure that user agents, including assistive technologies, can accurately interpret and parse content. For any product, service, tool or content, functionality and navigation of the content and user interface (UI) components must be programmatically exposed and operable.",Open the web application in the browser. Use a 3rd party screen reader to navigate the web application. Ensure every element on the page can be reached and parsed by the screen reader (all navigation must be possible via keyboard only).
|
| 55 |
+
53,"Ensure that Assistive Technologies (AT) can gather information about, activate (or set) and keep up to date on the status of user interface controls in the content. For any product, service, tool or content, functionality and navigation of the content and user interface (UI) components must be programmatically exposed and operable.","Open the web application in the browser. Access the web application source code. (For web properties, right-click and select Inspect Source). Verify each UI element has an accurate name and a role. For example, a Learn About WCAG link has the name Learn About WCAG and the role of link. If want to change an element role, use the role attribute. For example, if a link is used as the root of a drop-down menu, you should give it role=menu. Verify that elements which have the potential for multiple states or values have these states/values defined. For example, a checkbox can have the checked or unchecked states, and the value of a text edit box is the text inside it. Ensure there are no duplicate attributes/duplicate id values for elements."
|
| 56 |
+
54,Verify the button functionality in Shipping method page.,Launch the URL. Login as a registered user. Add an item to Cart. Click on View Full Cart. Click on Proceed to Check Out. Fill up the necessary details and click on Proceeds to Shipping Method. Enter all the required details and click on Next:Payment. Reload the Shipping method page and Click on Back to Shipping Address.
|
| 57 |
+
55,To verify the Product details in Shipping Method as Registered user.,Launch the URL. Login as a registered user. Add an item to Cart. Click on View Full Cart. Click on Proceed to Check Out. Fill up the necessary details and click on Proceeds to Shipping Method. verify the location of the Product detail Table. verify whether the section is minimized or expanded. Click on the Product Name. Click on the Manufacturer Name. Hover on the information icon in Product detail table next to Product name. Verify the Unit Price Column. Verify the Quantity column. Try to edit the quantity. Verify the sub total column in Product detail table. verify the decimal values displayed. verify the schedules column. verify the shipping To section.
|
| 58 |
+
56,To verify the User Name and Shipping Address and Account information in Shipping Method as Registered user.,Launch the URL. Login as a Registered user. Add an item to Cart. Click on View Full Cart. Click on Proceed to Check Out. Fill up the necessary details and click on Proceeds to Shipping Method. verify the User name displayed. verify the Label in the page. verify the Account Information.
|
| 59 |
+
57,To verify the fields in Subtotal Section when coupon is/not applied in Shipping Method as Registered user.,Launch the URL. Register as a Registered user. Add an item to Cart. Click on View Full Cart. Click on Proceed to Check Out. Fill up the necessary details and click on Proceeds to Shipping Method. verify the location of the Subtotal section. verify the Header Line. verify the Line item subtotal. verify the Coupon Details. verify the Cart Subtotal. verify the Currency Converter. Select a Currency from the dropdown. verify the Tax and Shipping message.
|