Final exam

Apply what you learned across the complete course in 15 new scenarios.

Estimated time: 15-20 minutes
Questions: 15 new scenarios
Passing score: 12 of 15

The final exam is free. Passing completes the course and gives you the option to purchase a verified certificate. A certificate purchase is not required.

Choose one answer for each question. This exam is open-book, unproctored, and has no time limit. You need 12 correct answers to pass and can try again.

Question 1 of 15A mobile banking app exposes every transaction title but gives no way to filter, review details, or operate transfer controls. What is the central problem?

Speech is too brief.The alternative interface exposes text but not enough structure and interaction.The app needs captions.The account artwork needs longer descriptions.

Question 2 of 15A quantity selector looks correct, but its plus and minus controls are absent from the accessibility tree. What is the first useful repair?

Add larger icons.Use operable buttons with clear names and expose the changed quantity.Move the selector above the product.Announce the entire page after each change.

Question 3 of 15A mobile app has a visual card grid, but swipe order jumps from the first card to a footer action before nearby content. What should the team define?

A predictable accessibility order with meaningful neighbouring destinationsA faster speaking voiceA browser landmark for each tileA new colour palette

Question 4 of 15A native app opens checkout in a WebView, loses focus after payment, and returns users to the top of the app. Which review is most relevant?

Only the HTML heading hierarchyContext transition, focus return, state preservation, and recoverySearch metadataPointer hover behavior

Question 5 of 15A team supports Windows web, Android, and iOS but tests only VoiceOver on Mac. What is the strongest correction?

Keep the same test because all screen readers use identical APIs.Choose representative combinations for each supported environment using audience and risk evidence.Replace manual testing with automated checks.Test only the oldest supported browser.

Question 6 of 15NVDA with Chrome completes a payment flow successfully. Which release statement is defensible?

The product is certified accessible.No barrier was found in the tested payment flow with the recorded NVDA and Chrome combination.Every Windows user can complete payment.Other supported combinations no longer need testing.

Question 7 of 15A screen-reader profile lists commands but no versions, task context, sources, or review owner. What is its main weakness?

It is too short to be useful.It cannot be maintained or connected reliably to product testing decisions.It should contain exact speech transcripts instead.It needs more screenshots.

Question 8 of 15A tester assumes VoiceOver behaves the same on iPhone and Mac because both use the same product name. What should they account for?

Different interaction models, input methods, and platform contextsOnly the different default voiceThe absence of speech on MacThe same commands with different spelling

Question 9 of 15A page uses large bold text for section titles, but heading navigation finds only the page title. What should change?

Increase the font weight.Represent the section hierarchy with real headings and verify its order.Add a tooltip to each title.Put every section in a dialog.

Question 10 of 15After form submission, five fields turn red and an error banner says only “Try again.” What is the best redesign?

Clear all values.Identify each error in text, associate it with its field, and provide a navigable summary.Move focus through every field automatically.Announce the word error five times.

Question 11 of 15A background save succeeds while a user is typing. Which response usually communicates success with the least disruption?

Move focus to the status message.Use an appropriate status announcement while leaving focus in the field.Reload the page.Open a modal confirmation.

Question 12 of 15A custom tab interface responds to clicks but not arrow keys and never exposes which tab is active. What is missing?

Only a visual underlineThe expected keyboard model, selected state, and tab-to-panel relationshipsA live region around the entire interfaceA separate page for each tab

Question 13 of 15A sortable data table changes row order, but the screen reader receives no indication of the active direction. What should the header expose?

Its pixel widthIts button operation and current ascending or descending stateThe total number of clicksA modal after every sort

Question 14 of 15A team finds no issues in one scripted flow and declares the product accessible. Which activity is still needed to understand efficiency and real-world usability?

More colour-contrast automation onlyResearch and testing with experienced screen-reader usersA larger screenshot setRemoving version information from the report

Question 15 of 15Accessibility defects repeatedly appear just before release. Which process change is most likely to prevent them?

Give structure, content, semantics, focus, testing, and evidence responsibilities to relevant roles from planning onward.Ask one tester to work faster.Delay all screen-reader testing until release day.Make the certificate harder to obtain.

Final exam

Your results

Topics to review

Completion summary

Topics covered

Suggested next steps

Certificate unlocked

Continue with hands-on practice