Test the component download, not only the live demo

The library application may provide global fonts, reset styles, variables, icons, and helper scripts that make a component look complete. If the exported ZIP omits one of those assumptions, the downloaded page can lose spacing, colors, interaction, or accessible names even though the catalog preview remains perfect.

Open the exported index file from its own directory and inspect the network and console. The component should reference only files included in the package or intentionally documented external resources. A disconnected test is valuable because it immediately reveals hidden CDN fonts, icon scripts, and modules that were never included in the handoff.

Automated checks can inspect each archive for expected HTML, CSS, JavaScript, README, and license files. They should reject absolute local paths, missing imports, and filenames that disagree with the documentation. When customization changes a token, the generated CSS must contain the selected value rather than the default from the catalog record.

The README should identify the component, explain its public tokens, list accessibility expectations, and describe any script behavior. The package becomes easier to trust when a developer can understand its contract before opening every file. A clear license also prevents a technically sound download from becoming unusable during legal review.

• Extract every ZIP into a fresh temporary directory before testing.
• Verify relative file references and reject missing assets.
• Run the standalone page at multiple widths and color schemes.
• Check that the README and license travel with the source.

Clicking the obvious control is not enough. Tab through every focusable element, activate buttons with Enter and Space, operate composite widgets with their documented keys, and inspect focus after menus or dialogs close. Touch targets and narrow layouts need their own run because pointer accuracy and viewport constraints change the experience.

Automated accessibility scans catch useful structural problems, but they cannot decide whether focus returns to the right place or an announcement is understandable. Pair them with targeted interaction tests. Capture console errors and failed requests during the same run so a visual success cannot mask an exception that breaks later interactions.

A component should become published only when its source, preview, metadata, download, keyboard path, and accessibility scan agree. Generate the public catalog index after those checks, not before them. This ordering prevents stale downloads and metadata from remaining live when a source component changes.

Run a final link check over the built site and request a selection of public ZIP URLs after deployment. That last step verifies that hosting includes ignored or generated binary assets. The strongest demo is not an animation; it is a package that behaves the same after it leaves the library.