I build websites and visual systems for clients. Before a handoff, I need more than a list of things that might be wrong: I need to show the source of a problem and prove what changed after a fix. That is why I built SiteCheck. SiteCheck is a small, local review loop for freelancers, designers and independent developers. It checks three static patterns: images without an alt attribute, form fields without a supported accessible name, and relative links whose destinations are absent from the supplied files. Each finding carries a rule ID, location, evidence and a suggested correction. The Python tool exports JSON and a self-contained HTML report; the live browser version accepts pasted HTML or a project folder and exports JSON without uploading the files. The demo is deliberately concrete. Three issues become two after I add a form label: one verified correction, two remaining findings and zero new regressions. A reproduction command generates fresh evidence and asserts those counts. The updated comparison tracks individual occurrences, so fixing one of two images does not hide the other. The September 26 review passes 71 Python tests, including 29 new regression cases, plus 17 browser verification scenarios covering six languages, local file handling, inert HTML parsing and mobile/desktop layouts. The original narrated video records the earlier 42-test state; the updated video adds current browser execution and the presentation carries the latest results. SiteCheck runs without a paid runtime API. It does not crawl websites, verify external HTTP links, interpret server routes or replace a complete accessibility audit. I have not claimed a measured productivity speedup. Its value is a focused handoff: understandable evidence, an explicit human decision and a repeatable recheck. The editorial design makes that evidence readable instead of burying it in a dashboard.
Category tags: