Open evaluation framework · 2026 edition
HTML Artifact Collaboration Checklist
Fifteen reproducible checks for deciding whether a live HTML artifact is merely shareable—or ready for review, revision, automation, and responsible discovery.
Methodology
Test the workflow, not the feature list.
- 1. Use one representative artifact. Include headings, a table, a link, an image with alternative text, and one browser interaction.
- 2. Test three roles. Repeat the workflow as publisher, signed-out reviewer, and API, CLI, or MCP client.
- 3. Save evidence. Record the tested URL, date, screenshot or response, and documentation link for every result.
- 4. Score conservatively. Award 2 for a reproducible pass, 1 for a documented workaround, and 0 when the capability is missing or unverified.
The checklist
Fifteen checks. Thirty possible points.
Apply the same evidence threshold to every platform. A polished demo is not a pass unless the behavior can be reproduced.
Stable HTTPS URL
Pass signal: The artifact opens at one durable HTTPS URL after revisions.
Evidence: Save the URL, publish a revision, and confirm the original URL still resolves.
Explicit access mode
Pass signal: Public, unlisted, and restricted states are distinguishable before sharing.
Evidence: Record the selected state and test it in a signed-out browser.
Rendered browser view
Pass signal: A reviewer can use the artifact without downloading or running local files.
Evidence: Open the link on a second device and test its primary interaction.
Contextual feedback
Pass signal: Feedback can point to a section, element, or selected passage.
Evidence: Leave a comment on one specific part and confirm its context survives reload.
Resolvable discussion
Pass signal: Comments support replies and an explicit resolved or reopened state.
Evidence: Reply, resolve the thread, reload, and reopen it.
Version recovery
Pass signal: Prior versions are identifiable and can be inspected or restored.
Evidence: Make two changes, identify both versions, and restore the first.
Machine-readable state
Pass signal: A documented interface can read the artifact and its review state.
Evidence: Save one successful API, CLI, or MCP response and its documentation URL.
Scoped updates
Pass signal: Automation can update a defined region without republishing unrelated content.
Evidence: Change one region and confirm an unrelated region is byte-for-byte unchanged.
Durable identifiers
Pass signal: The document and editable regions keep stable identifiers across revisions.
Evidence: Compare identifiers before and after an update and record any remapping.
Concurrent update safety
Pass signal: Parallel edits merge safely or a stale write is rejected before it overwrites newer work.
Evidence: Open two clients at the same revision, save independent edits, then attempt one stale write and confirm the system preserves both accepted changes or surfaces an explicit conflict.
RFC 9110 conditional requestsAuthorship and revision provenance
Pass signal: Each tested revision records a stable identifier, generation time, and responsible human or software agent.
Evidence: Publish one change, then save the revision identifier, timestamp, and attributable actor or agent from the UI or machine-readable history.
W3C PROV-OIndexing intent
Pass signal: Canonical URL and index or noindex intent are visible and consistent.
Evidence: Inspect the canonical link and robots directive on the rendered page.
Google canonical guidanceShare preview metadata
Pass signal: Title, description, image, and canonical page URL are declared for sharing.
Evidence: Inspect the Open Graph properties and validate the image URL.
Open Graph protocolAccessible reading path
Pass signal: Headings, landmarks, keyboard use, contrast, and text alternatives are tested.
Evidence: Run keyboard and automated checks, then record remaining manual findings.
WCAG 2.2Active content boundary
Pass signal: Scripts and embedded resources run inside a documented security boundary.
Evidence: Record the content policy or isolation model and test one blocked resource.
OWASP CSP guidanceStandards and source notes
The collaboration checks are workflow tests. The discovery, accessibility, and security checks are anchored to the primary standards and official guidance below.
- Google Search: canonical URLs
Canonical selection and duplicate URL handling.
- Google Search: robots meta tags
Explicit index and noindex controls.
- Open Graph protocol
Minimum metadata for link previews.
- W3C Web Content Accessibility Guidelines 2.2
Accessibility success criteria and conformance.
- W3C PROV-O: The PROV Ontology
Interoperable attribution of entities and revisions to human or software agents.
- IETF RFC 9110: Conditional Requests
Preconditions and validators that prevent one client from overwriting another client’s parallel update.
- OWASP Content Security Policy Cheat Sheet
Security boundaries for active HTML content.
Citation
Reuse the framework with attribution.
The checklist, data files, and audit template may be quoted, adapted, or used in evaluations. Link to this page so readers can inspect the current method and source notes.
Naidu, Raunaq. “HTML Artifact Collaboration Checklist 2026.” HTML Docs, 4 Aug. 2026, https://www.html-docs.com/guides/html-artifact-collaboration-checklist.Markdown attribution
[HTML Artifact Collaboration Checklist 2026](https://www.html-docs.com/guides/html-artifact-collaboration-checklist) — Raunaq Naidu, HTML Docs.HTML attribution
<cite><a href="https://www.html-docs.com/guides/html-artifact-collaboration-checklist">HTML Artifact Collaboration Checklist 2026</a></cite> — Raunaq Naidu, HTML Docs.Run the checklist on a real artifact.
Publish a representative page, then keep the evidence beside the downloaded CSV.