Accessibility Audit

Unit 5 introduced accessibility during the build.

Now test the final generated site as a connected experience.

Audit the generated output

Test at least:

• document language;
• unique/useful page titles;
• heading hierarchy;
• landmarks/semantic regions;
• keyboard navigation;
• visible focus;
• skip navigation if implemented;
• meaningful link text;
• image alternative text;
• form controls if any;
• color contrast;
• zoom/reflow;
• reduced-motion behavior if motion exists.

Keyboard journey

Start at Home and complete this path without a mouse:

Home
→ Projects
→ one project detail
→ back/navigation
→ Journal
→ one post

Record any trap, hidden focus, or confusing order.

Template-level failures

If the same heading/focus/landmark problem appears on every page, inspect shared layout/include source.

If only one project has missing alt text, inspect that project data/content/include inputs.

Use scope as evidence.

Accessibility is not a final checkbox

The strongest final audit should find few issues because accessibility was built in earlier.

If the audit uncovers many problems, fix the source system rather than patching generated pages one at a time.

Evidence checkpoint

Create:

Include at least one issue you found and repaired, even if it is small.