Project QA Plan — Riverbend Cafe Website Build

Project: Riverbend Cafe marketing website (build and launch) Sponsor / client: Riverbend Cafe (owner: M. Alvarez) Author: T. Okafor, Delivery Lead Date: 5 June 2026 Reviewers: S. Hughes (Design), R. Patel (Client liaison) Status: Approved

---

1. Project and scope

This project delivers a five-page marketing website for Riverbend Cafe — home, menu, about, events, and contact — plus a content-managed blog. This QA plan covers all design, content, build, and accessibility deliverables. Hosting platform uptime is out of scope, as it is covered by the host's own service agreement.

2. Quality objectives and acceptance criteria

Deliverable	Acceptance criteria (specific, checkable)	Standard / reference	Accepted by
Visual design (Figma)	Matches approved brand palette and type scale; covers all 5 page types and mobile + desktop	Riverbend brand guide v2	Client (M. Alvarez)
Page content	No spelling errors; every menu price matches the supplied price list; contact details correct	Supplied copy deck	Client liaison (R. Patel)
Built pages	Pixel match to design within tolerance; works in Chrome, Safari, Firefox; no console errors	Design (Figma)	Delivery Lead
Accessibility	All pages pass automated checks at WCAG 2.1 AA; keyboard navigable; images have alt text	WCAG 2.1 AA	Design reviewer
Performance	Home page Largest Contentful Paint under 2.5s on a mid-range mobile profile	Web vitals target	Delivery Lead

3. Review and approval gates

Gate	Applies to	Entry condition	Exit condition (passed when)	Decider
Author self-check	All	Draft complete	Self-check checklist passed	Author
Peer review	Design, content, build	Self-check passed	Comments resolved; criteria met	S. Hughes / T. Okafor
Accessibility review	Built pages	Build peer review passed	WCAG 2.1 AA checks pass	S. Hughes
Client sign-off	Design, content, final site	Internal gates passed	Client accepts by email	M. Alvarez

4. Roles and responsibilities (RACI)

Activity	Responsible (R)	Accountable (A)	Consulted (C)	Informed (I)
Maintain this QA plan	T. Okafor	T. Okafor	S. Hughes	Team
Review design deliverables	S. Hughes	T. Okafor	R. Patel	M. Alvarez
Review content	R. Patel	T. Okafor	M. Alvarez	S. Hughes
Accessibility review	S. Hughes	S. Hughes	T. Okafor	Team
Client sign-off	R. Patel	M. Alvarez	T. Okafor	Team
Triage and track defects	T. Okafor	T. Okafor	S. Hughes	Team

5. Defect / issue process

• Raising an issue: Logged in the shared issue tracker with a screenshot, the page, and steps to reproduce.
• Severity scale:
  • Critical — broken page, wrong price, or blocked checkout/contact path.
  • Major — feature works incorrectly with no clean workaround.
  • Minor — cosmetic spacing, copy nit, or low-impact visual difference.
• Triage: T. Okafor reviews new issues each weekday morning and assigns severity and owner.
• Resolution rule at sign-off: No open Critical or Major defects at client sign-off; agreed Minor issues move to a launch-week backlog recorded in the tracker.
• Tracking: All issues live in the tracker; closure requires the reviewer to confirm the fix.

6. Quality metrics

Metric	How measured	Target / threshold	Owner
Open defects by severity	Count from tracker	0 Critical / 0 Major at sign-off	T. Okafor
First-time review pass rate	Deliverables passed / reviewed	At least 75%	S. Hughes
Post-launch escapes	Issues raised in week 1 after launch	Fewer than 3	T. Okafor

7. Audit / review schedule

Activity	When / frequency	Performed by	Output
Design QA checkpoint	End of design phase	S. Hughes	Findings + actions
Pre-launch accessibility audit	Before client sign-off	S. Hughes	Audit note
QA plan review	Start of each phase	T. Okafor	Updated plan