Assignment A10 — The Design Pass

Scenario

Your report ships to leadership next month. Before it does, it gets the pass every professional report gets: structure, hierarchy, access, speed — page by page, with a design log proving the work.

Requirements

1. Question-test every page. Rename each page tab to (a short form of) its question — no "Page 1", no "Overview". If any page fails the test, split it. Expected pages at minimum: your Briefing/answer page, Explore, Category Detail, Performance, Specialty (merge or split as your questions dictate — the test decides, not the history).
2. Hierarchy pass on the Briefing page: the answer top-left (your choice of headline, defended in the log), context cards across the top, largest visual = most important evidence, slicers at the rail.
3. Alignment: snap-to-grid on; every page's visuals share edges. (The grader can't measure beauty, but the instructor eyeballs one page against the grid.)
4. Accessibility kit, mechanically checkable:
   • Alt text on every visual, on every page — finding-first prose, not species labels (slicers may state their function: "Year filter").
   • Tab order set on Briefing and Explore to the reading path.
   • No text below the theme's ink color at body sizes (no pale-gray annotations).
5. Performance sanity: run Performance Analyzer on your heaviest page; screenshot or note the slowest visual and either fix it or defend it in the log.
6. The design log (one page, any format): the question each page answers, your Briefing headline choice defended in two sentences, the slowest visual and its disposition, and the one-in-twelve simulation result.

Checklist (what the grader checks)

Before you submit

• Tab through Briefing with the keyboard — does the traversal tell the page's story in order?
• Read every alt text aloud. Any that say "chart of data" get rewritten as findings.
• Save, close, reopen, verify.