[{"id":"webaccessibilityintermediate-001","courseId":"web-accessibility-intermediate","domain":"semantic-html","topic":"Labeled navigation landmarks","prompt":"A page has two <nav> elements: one for the main site menu and one for the footer links. Both are navigation landmarks. What should the developer do?","hint":"Count the navigation regions first, then think about what a user needs to tell them apart.","explain":"Assistive technology lets users jump between a page's regions and announces a name for each. Think about what a user can rely on when two regions of the same kind share no distinguishing name.","source":"https://www.w3.org/WAI/ARIA/apg/patterns/landmarks/examples/navigation.html","interaction":{"type":"single"},"options":[{"id":"a","text":"Give each nav its own unique accessible name, such as an aria-labelledby pointing to its own heading.","why":"When a page has more than one navigation landmark, each needs a unique label so users can tell them apart."},{"id":"b","text":"Leave both unlabeled, because the nav element already announces itself as navigation.","whyNot":"The element supplies the role, but a label is optional only when there is a single navigation landmark."},{"id":"c","text":"Give both the same label, 'Navigation', so the screen reader groups them together.","whyNot":"Identical labels are for navs that hold an identical set of links; these two hold different links."},{"id":"d","text":"Change the footer nav to a div with role='navigation' so it stops counting as a landmark.","whyNot":"role='navigation' defines a navigation landmark just as the nav element does, so the landmark remains."}],"answer":"a","explanation":"When a page has more than one navigation landmark, each needs a unique label so users can tell them apart; a label is optional when there is only one.","concept":"When a page has more than one navigation landmark, each needs a unique label so users can tell them apart; a label is optional when there is only one.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["Two or more nav landmarks on one page each need a unique label."]},{"id":"webaccessibilityintermediate-002","courseId":"web-accessibility-intermediate","domain":"semantic-html","topic":"Placeholder as label","prompt":"On a short, obvious form field, placeholder text can stand in for a visible label without harming accessibility.","hint":"Ask what stays visible, and what a screen reader announces, once the user has typed into the field.","explain":"A control's name has to remain available to everyone for the whole time someone uses the field. Think about what stays on screen, and what a screen reader announces, once a value has been typed in.","source":"https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes/placeholder","interaction":{"type":"true-false"},"options":[{"id":"a","text":"True","whyNot":"Placeholder text disappears once typing starts and is not announced by default, so it cannot replace a label."},{"id":"b","text":"False","why":"A visible label stays on screen and is announced, so placeholder text must not be used in its place, even on a short field."}],"answer":"b","explanation":"Placeholder text is a hint shown only while a control is empty; it is not announced by default and is not a substitute for a label.","concept":"Placeholder text is a hint shown only while a control is empty; it is not announced by default and is not a substitute for a label.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["Placeholder text is not a label; keep a visible label on every field."]},{"id":"webaccessibilityintermediate-003","courseId":"web-accessibility-intermediate","domain":"semantic-html","topic":"Error identification","prompt":"A form uses native HTML validation and has two invalid required fields. The user submits the form once. What does the user get from the browser's validation?","hint":"Consider whether the browser reports every problem at once or works through them in turn.","explain":"Native validation checks a form before it is sent and reports what it finds. Think about how much of that report a browser can present at a single moment.","source":"https://www.w3.org/WAI/WCAG22/Understanding/error-identification.html","interaction":{"type":"single"},"options":[{"id":"a","text":"Only the first error message is exposed; the next one appears only after the user fixes it and resends the form.","why":"Native validation exposes the first error message only; the next error is exposed once a conforming input is entered and the form is resubmitted."},{"id":"b","text":"Both error messages are exposed at once, so the user can fix both fields in one pass.","whyNot":"Native validation exposes only the first message, so the second must wait for a corrected resubmission."},{"id":"c","text":"The browser sends the form anyway and marks both fields as errors on the server.","whyNot":"Native validation prevents the submission of incomplete or invalid forms rather than sending them."},{"id":"d","text":"The browser shows one summary of all problems at the top, and the page does not move.","whyNot":"The user agent generally sets focus to the first field in error and scrolls the page to show it."}],"answer":"a","explanation":"Native HTML validation blocks an invalid submission, moves attention to the first field in error, and exposes only the first error message until the user corrects it and resubmits.","concept":"Native HTML validation blocks an invalid submission, moves attention to the first field in error, and exposes only the first error message until the user corrects it and resubmits.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["With native validation, users see one error at a time, so expect repeated resubmissions."]},{"id":"webaccessibilityintermediate-004","courseId":"web-accessibility-intermediate","domain":"semantic-html","topic":"Input purpose tokens","prompt":"A checkout asks shoppers for their own birthday, and the team needs the field's purpose to meet the Identify Input Purpose criterion. Which change does that?","hint":"Ask whether the purpose is written in the markup or only guessed by the browser.","explain":"This criterion is about the page telling software what a field is for, not about the words a sighted user reads. Consider how a browser could know that a field asks for a person's own details without guessing.","source":"https://www.w3.org/WAI/WCAG22/Understanding/identify-input-purpose.html","interaction":{"type":"single"},"options":[{"id":"a","text":"Add autocomplete='bday' to the birthday input, so the purpose is exposed in the code.","why":"The autocomplete attribute with a purpose token such as bday exposes the input's purpose programmatically."},{"id":"b","text":"Rely on the browser guessing the purpose from the label text, which counts as exposing it.","whyNot":"Browser heuristics can autofill, but they do not meet the criterion; the purpose must be programmatically exposed."},{"id":"c","text":"Add autocomplete='off' to the form, which removes any need to state the purpose.","whyNot":"Turning autofill off does not remove the requirement; input purposes must still be programmatically determinable."},{"id":"d","text":"Add a visible 'Birthday' label beside the input, since a visible label identifies its purpose.","whyNot":"A visible label helps people, but the purpose itself must be exposed, for example with an autocomplete token."}],"answer":"a","explanation":"Input purpose must be exposed in the code, typically with an autocomplete token such as bday; browser heuristics and turning off autofill do not satisfy it.","concept":"Input purpose must be exposed in the code, typically with an autocomplete token such as bday; browser heuristics and turning off autofill do not satisfy it.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["Autofill guesses don't count; expose input purpose with an autocomplete token."]},{"id":"webaccessibilityintermediate-005","courseId":"web-accessibility-intermediate","domain":"semantic-html","topic":"Redundant entry","prompt":"A multi-step checkout asks for the same address twice. Which TWO statements about the Redundant Entry criterion are correct?","hint":"Think about what the website itself must do, not what the browser does.","explain":"This criterion targets the mental effort of remembering or retyping information within one process. Think about how a site can avoid asking twice, and when asking again is still acceptable.","source":"https://www.w3.org/WAI/WCAG22/Understanding/redundant-entry.html","interaction":{"type":"multiple","tellCount":true},"options":[{"id":"a","text":"The site should offer the earlier address to select, or a tick box that copies it, rather than a blank form.","why":"The criterion counts selecting, copying or ticking a box to reuse earlier values as making information available to select."},{"id":"b","text":"Browser autocomplete alone meets the criterion, because the browser remembers the earlier value.","whyNot":"The criterion says browser autocomplete is not sufficient, because the website must supply the earlier entry."},{"id":"c","text":"If an earlier answer is no longer valid, the site may ask the user to enter it again.","why":"The criterion lets a site request information again when the previously entered information is no longer valid."},{"id":"d","text":"The site must keep entered details between visits, so a returning user never retypes them.","whyNot":"The criterion adds no requirement to store information between sessions."},{"id":"e","text":"A password confirmation field that asks for the new password again must be removed.","whyNot":"Having the user re-enter a newly created password that is not displayed is an allowed exception."},{"id":"f","text":"A payment step on another domain is out of scope, since the process does not stay on one site.","whyNot":"A process can run across domains, so a third-party payment provider inside a checkout is in scope."}],"answer":"ac","explanation":"The website must make earlier answers available within a process, by selection or copying, since browser autofill is not sufficient; re-asking is allowed when data is no longer valid, and some security cases are exempt.","concept":"The website must make earlier answers available within a process, by selection or copying, since browser autofill is not sufficient; re-asking is allowed when data is no longer valid, and some security cases are exempt.","rev":1,"updatedAt":"2026-10-26","kind":"scenario","takeaways":["Redundant entry is the website's job: offer earlier answers in a process, not just browser autofill."]}]