Who it is forA developer or product owner who wants a readable record of a page's checks to review or share before a release.
The problemA terminal summary does not show which control failed or what the page looked like at that moment.
The outcomeAn HTML file that lists the checks and includes screenshots, which can be opened in a browser.
What you need first
- Python 3.10+, or uv or pipx to install the tool
- A folder containing built web page output, with index.html or another page to check
- Internet access for the first run, when Chromium may be downloaded
Steps
- Run
pip install assay-uito install the tool. - Run
assay ./my-app --report out.html, replacing ./my-app with your page folder. - Open out.html in a browser and review the flagged checks and their screenshots.
- Share or archive out.html with the team, or re-run after fixes to produce a new report.
Prompt for your agent
Use the assay-ui package to check the page folder <folder path> and write an HTML report to <report path>. Run assay <folder path> --report <report path>, then confirm the report file exists and list the flagged checks from the terminal output.
Caveat. The report only covers what Assay's rules can observe on the page, so a clean report does not prove the page meets its requirements.
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer