Audit operations
Build an Inventory of Page Templates and Components
Published by whatisADA / Grow Wild Agency · Updated
Purpose and preparation
Create a map of the structures that generate the site before choosing audit pages. Group pages by meaningful differences in layout, interaction and content. Keep the inventory connected to real URLs and owners.
A practical example
A site has thousands of product URLs but only a few product templates, plus a separate checkout, support portal and document archive.
How to check it
- List domains, authenticated areas, templates, reusable components and important content types. Record a representative URL and owner for each.
- Identify variants such as mobile navigation, empty results, validation, localized content and third-party widgets. Add states that change behavior even when the URL stays the same.
- Compare the inventory with the sitemap and product journeys. Resolve missing areas and use the completed map to plan representative testing.
What can be missed
Counting URLs alone overstates repeated templates and understates interactive states. A single URL can contain several materially different views.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.