DQ – Module 13: Web Accessibility Testing: Basic Methods and Tools The Scope of the Test Fee: Free Practice Tests (based on WAS Guide https://www.accessibilityassociation.org/ ) Passing score: 95% Time limit: 15 minutes Number of questions: 17 Format: Multiple Choice, Multi Answer and True/False Difficulty: Advance 1 Created on January 02, 2023 DQ - Module 13: Web Accessibility Testing: Basic Methods and Tools The Scope of the Test DQ - Module 13: Web Accessibility Testing: Basic Methods and Tools The Scope of the Test 1 / 17 The more developers incorporate automated accessibility testing into the build/creation phase, the more confident they will be in addressing accessibility issues. True False 2 / 17 Testing to uncover any new errors introduced by the remediation process is called: Regression testing Unit testing Beta testing Integration testing 3 / 17 Testing all of the pages of a web site may not be easy or practical, but it has to be done to ensure an adequately compliant site. False True 4 / 17 The first step to conducting web accessibility testing is: Conduct manual testing Conduct regression testing Run automated tests Plan for remediation of accessibility issues Define the scope of the test 5 / 17 Remediation for all accessibility issues should be: Performed by contractors Completed before the application is released Made top priority for all staff until the issues are resolved Prioritized according to factors such as impact, severity, frequency, etc. 6 / 17 Automated testing should only be conducted during the testing phase of the development lifecycle. False True 7 / 17 If error messages used in form validation are conveyed through a screen reader, then they do not need to be visible. False True 8 / 17 To be compliant, captions for videos must include all of the following EXCEPT: Narration and dialog Important sound effects Identity of multiple speakers Description of visual content 9 / 17 Analyzing specific page content like images, forms, tables, and widgets should be included in the scope of the evaluation. False True 10 / 17 About a third of accessibility problems can be found through automated testing. False True 11 / 17 Which type of testing allows developers to evaluate small chunks of code for accessibility issues wiout any dependencies? Unit testing Manual testing Regression testing Integration testing 12 / 17 Screen readers can help you identify issues with which of the following? Custom widgets Color used to convey meaning Alternative text Keyboard functionality Video only presentations Form labels and instructions Visual focus indicator Headings Touch target size Media players 13 / 17 If a bug report includes a title, description, and steps to reproduce the issue, what should it also include to make it more effective? (Select all that apply) Recommendations for how to fix the issue Severity of the issue All of the options Expected behavior and/or results 14 / 17 An effective bug report should be written for which of the following recipients? Developers and designers who have extensive knowledge in accessibility The core accessibility team Other testers who can validate the issue Stakeholders who may not be well-informed about accessibility 15 / 17 The purpose of links must always be conveyed through the link text itself. True False 16 / 17 All of the following are things to consider when determining the scope of the accessibility tests, EXCEPT: Which pages have the most diversified and representative content, structure, and semantics types? Are there any important transactional or multi-step processes? How many users can access an interface element at one time without crashing it? What templates are in use on the site? 17 / 17 When beginning the actual testing process, what should testers do first? Test for form validation accessibility Conduct keyboard accessibility testing Run an automated test Check if color is used to convey meaning Your score is The average score is 0% LinkedIn Facebook Twitter 0% Restart quiz