How reviews work

Evidence from HTML.
Context from you.

Design Doctor fetches the public HTML of the HTTPS page you save. Its rules run in Google Apps Script. The service retains your page name, URL, goal and reports so you can compare reviews.

Accessibility

Checks include document language, titles, headings, image alternatives, link and button names, form labels, ARIA references, table structure and mobile configuration. Findings reference WCAG 2.2 where applicable. They are signals for review, not certification.

UX informed by public research

Form checks use publicly available Baymard Institute articles. Design Doctor is independent of Baymard and does not use its Premium catalog or provide an official Baymard benchmark. Shopping journeys require contextual review beyond one page.

AI readiness

Checks consider readable text, semantic landmarks and controls, declared structured data and indexing signals. They do not run an AI agent, measure task success, or produce an Is Agentic score. APIs, MCP, robots.txt and sitemaps are not fetched in this version.

What remains manual

JavaScript rendering, contrast, keyboard navigation, focus, screen readers, responsive layouts and complete journeys require browser testing. An absent HTML signal does not prove that a page works correctly.

Comparisons

The first review establishes a baseline. Later reviews show new, persistent, changed and no longer detected signals. Engine or report-language changes are identified to avoid treating new rules or translations as website changes.