audit

Use audit to check whether an interface holds up in use: can people navigate with a keyboard, read it in dark mode, and complete the task on a phone? Impeccable examines the implementation and returns a report ordered by severity. It leaves the code unchanged.

Try it

/impeccable audit the checkout flow

Name a page, component, or flow. Run it before release, after a substantial change, or when you suspect a quality problem.

How it works

For web projects, the report covers five areas:

• Accessibility: labels, contrast, semantics, and keyboard access.
• Performance: loading, rendering, animation, and unnecessary work.
• Theming: consistent tokens and support for the project’s themes.
• Responsive behavior: layout, touch targets, and usability across screen sizes.
• Implementation integrity: repeated inconsistencies and verified anti-pattern findings.

Each finding explains where the problem occurs, how it affects someone using the page, and how to fix it. For example:

P1 · Payment button has no visible keyboard focus

Tabbing reaches the button, but nothing shows that it is selected. Add a visible focus state and check it through the full payment flow.

This is an illustrative finding, not output from a recorded audit.

Fix the most serious problems first

Priority	What it means	When to fix it
P0 · Blocking	Someone cannot complete the task	Immediately
P1 · Major	Significant difficulty or an accessibility failure	Before release
P2 · Minor	A problem with a workable alternative	In the next improvement pass
P3 · Polish	A small issue with little effect on use	After higher priorities

Ask Impeccable to address the findings, or follow its suggested commands. Harden handles missing states and edge cases, optimize addresses performance, and polish refines the existing experience. Re-run audit to check the fixes.

How scoring works

Each web area scores from 0 to 4, for a total out of 20. The total summarizes the assessment; individual findings tell you what needs attention. A strong total can still contain a blocking issue.

Auditing an iOS or Android app

When the project context identifies a native app, audit uses platform-specific checks, including screen readers, text scaling, touch targets, and platform conventions. The web detector does not run on native interfaces.

For feedback on the design’s clarity, hierarchy, or character, use critique.