Assessment 03 · Answers and scoring

Two points per answer: correct conclusion plus explanation or example. Total 12.

1. Hash routing keeps client screen information after #, so simple static hosts request the same entry HTML. Browser-history routing needs a fallback/rewrite to that app HTML for valid client paths, plus correct asset base paths. Hash routing still needs direct URL, refresh and host-path checks.
2. Show event-not-found recovery within the matched route. An unmatched path uses the catch-all page. Pending data must show loading rather than prematurely claiming the event does not exist.
3. Inspect document title, keyboard focus, heading structure, Back/Forward behavior and recovery links. A focused heading can orient a keyboard user after navigation; title synchronization updates browser context. Do not steal focus on unrelated input updates.
4. It tests the answer implementation rather than the learner’s work. The learner command must import starter modules and any learner-authored tests for that project, with separate expectations. Passing reference checks cannot establish capstone completion. Must correct.
5. Await user-event actions and query by accessible role/name. Use findBy for an expected async result and queryBy for absence. Controlled/deferred promises can resolve B before A without arbitrary sleeps. Assertions should describe observable behavior rather than internal state.
6. Real-browser layout and zoom, screen-reader announcements, touch/mobile usability, target-host direct paths and a beginner pilot remain unsupported unless separately checked. Other examples include security and real service behavior. Passing local checks does not authorize publication and this course implements no real registrations. Must correct.

A good release paragraph names commands and environments, distinguishes simulated-DOM evidence from real-browser observations, and identifies the next acceptance owner without pretending those checks already happened.