Paste an address below. The checker fetches that page, validates it against the Mews DTD, reads your copy of the stylesheet and up to twenty of your images, and then lists every rule the page breaks together with the section of the spec that explains it.
Check page tells you what it found and keeps nothing. Check and list does the same and then, if the page passes, puts your site in the directory. Either way it can take up to a minute, and there is no progress bar, because a progress bar wants JavaScript and that is the one thing a Mews page can't have. Leave this page open and go and put the kettle on.
The same checks run on the command line, which is far less tedious while you are still fixing things:
uv run mewslint.py https://example.com/
It reads local files too, so you can check a page before anyone else sees it, and I run it on this site as well: the build refuses to produce mews.page at all if one of its own pages stops conforming. That seemed only fair.
One page per site, the one you hand me, and nobody reviews it: if the page passes it goes in, and that is the whole of the trust model. A listed site is checked again every week, and one whose page stops conforming comes out of the directory without being asked twice.
Fix it, submit it again, and it is back in straight away. I keep no address to warn you at, which is the trade (no account, no password to forget, and no warning either).
If the checker turns your page down over something the spec doesn't actually say, that is a bug in my validator rather than a fault in your page, and I would like to hear about it.