Diagram accessibility review.

Use this pass to review architecture concept diagrams, maps, tables, cards, and flows for text equivalents, clear labels, semantic reading order, and owner review before their claims are treated as accepted.

Review Snapshot

Concept pages: 4
Image diagrams: 0
Required checks: 4
Review state: Routed

Review Scope

Architecture concept diagram-surface review
Concept page	Diagram-like surfaces	Text equivalent	Label check	Owner review
Stornamics system map	Product role map, integration path table, read-the-map flow	Product cards, table caption, row headers, visible boundaries, and ordered reading steps describe the same relationships without relying on layout.	Product names, route links, maturity labels, section headings, and table captions carry the meaning.	docs-product-lead, product SMEs, docs-qa-reviewer, docs-lead
Product mental models	Product model cards, quick map table, reading paths	Term definitions, product evidence rows, and reading-path lists explain each model without needing visual arrangement.	Product headings, route links, maturity labels, table captions, and boundary labels stay visible.	docs-product-lead, product SMEs, docs-qa-reviewer, docs-lead
Durability and evidence levels	Evidence ladder, product examples table, claim promotion flow	Level cards, required evidence copy, product examples, and ordered promotion steps state the evidence logic in text.	Evidence level names, maturity labels, captions, flow labels, and exclusion language are explicit.	docs-product-lead, product SMEs, docs-qa-reviewer, docs-lead
Tenancy and security concepts	Term map, product surface map, review flow, boundary cards	Term definitions, product surface rows, ordered review steps, and do-not-infer cards provide the text path.	Term labels, route links, maturity labels, table captions, flow labels, and risk boundaries remain visible.	docs-product-lead, security/privacy reviewers, docs-qa-reviewer

Acceptance Standard

Diagram accessibility and review checks
Requirement	Standard	Evidence to keep
Text equivalent	Any architecture relationship shown through layout, proximity, or sequence also needs adjacent prose, a table, a definition list, an ordered flow, or an evidence row.	Section copy, table captions, scoped row headers, flow labels, review records, and evidence rows.
Clear labels	Readers must not need shape, color, or position alone to understand product role, maturity, evidence level, claim boundary, or review state.	Visible headings, route links, maturity labels, table captions, row and column headers, and explicit boundary wording.
Semantic reading	Tables use captions and scoped headers, flows use ordered lists, and card groups use headings with readable body text.	Rendered JSX, shared component styles, docs validations, and Gatsby build output.
Owner review	Product, security, privacy, docs QA, or docs lead reviewers are named when a diagram surface carries sensitive architecture meaning.	Frontmatter owner, reviewer metadata, evidence owner fields, and PR review before publication.

Review Flow

Inventory The SurfaceName whether the page uses cards, tables, flows, boundary callouts, screenshots, SVG, bitmap, Mermaid, or canvas.
Check The Text PathMake product role, relationship, boundary, maturity, evidence, and exclusion meaning readable outside the visual arrangement.
Check Labels And SemanticsConfirm headings, captions, row headers, ordered steps, route links, and maturity labels carry the meaning.
Route Owner ReviewSend product-boundary, security, privacy, support, and claim-risk surfaces through product SMEs, docs QA, and docs lead review.

Do Not Infer

No Image-Only Diagrams

Architecture meaning must not live only inside pixels, color, or visual position.

No Color-Only State

Product, maturity, review, and evidence state need visible text labels near the surface.

No Ownerless Architecture Claim

A diagram can simplify a relationship, but the same evidence and reviewer rules still apply.

Evidence

DOCS-048 evidence map
Review area	Evidence	Status
Architecture concept inventory	DOCS-044, DOCS-045, DOCS-046, DOCS-047, DOCS-048	pending
Text equivalents for diagram-like concept content	Rendered concept pages, review records, table captions, row headers, and ordered flows	pending
Label and semantic structure	Rendered concept pages and shared section shell review	pending
Owner review routing	Frontmatter owners, reviewers, evidence owners, and PR review	pending

Internal review records track this accessibility model and the required text equivalents for diagram-like content.

Safe Next Steps

Available: DOCS-044
Read the system map
Use the product role map and integration lane table as the primary cross-product architecture concept.
Available: DOCS-045
Review product mental models
Check product nouns and reading paths before drawing or revising a product relationship.
Available: DOCS-046
Apply evidence levels
Keep maturity, evidence, and owner review labels near diagrams that influence claim strength.
Available: DOCS-047
Check security concepts
Route tenant, dataset, auth, token, privacy, and current-gap diagram wording through the right reviewers.