A municipal website accessibility sweep must cover page-level issues and sitewide navigation. Which pattern should the agent follow?
Select an answer to reveal the explanation.
Short Explanation
Accessibility is local and global. Check pages one by one, then take a separate pass at cross-page navigation—homepage vibes alone do not clear the whole city site.
Full Explanation
A municipal website accessibility sweep should run per-page analysis, then a separate cross-page navigation integration pass. Accessibility defects appear both locally (contrast, labels, headings on a page) and globally (skip links, menus, focus order across templates); sequencing those concerns preserves attention and coverage.
Checking only one homepage widget and declaring the site compliant fails because a single component sample cannot certify district- or city-wide accessibility. Mixing every page and navigation concern into one overloaded prompt fails conceptually by diluting attention and producing shallow, unsorted findings. Skipping navigation analysis because page color contrast implies full accessibility fails because contrast on a page does not prove keyboard navigation, landmarks, or cross-page consistency.
Exam caveat: per-page then navigation still may miss third-party widgets and PDF attachments that need their own scoped passes under the same program. Operational check: maintain a page inventory, run page-scoped checks to a findings store, then run a navigation/integration pass across templates; block “compliant” status until both passes report clean or explicitly waived items.