Paste HTML to check inquiry paths
Paste page HTML below. The tool counts forms, message forms, search forms, fields and accessible labels, plus tel:, mailto:, contact-page links, QR and WeChat wording, and returns a 0–4 path score. No network, no upload, no dependencies.
Not checked yet.
Definitions
| Item | Definition | Boundary |
|---|---|---|
| Message form | Form contains a textarea | JS-inserted forms excluded |
| Search form | type=search, name=q/keyword or action containing search | Otherwise unclassified |
| Fields | input/select/textarea except hidden and buttons | Visibility not judged |
| Accessible label | aria-label, aria-labelledby, title, placeholder, label for or wrapping label | Wording not judged |
| Contact link | href containing contact / lianxi / lxwm / about / feedback | Keyword lower bound |
| QR / WeChat | Text or image alt match | No image recognition |
| Path score | How many of message form, tel, mailto, contact link exist | 0–4, QR/WeChat excluded |
The tool only counts strings and structure: a form may not submit, and a QR code with empty alt can still be visible; results are for triage, not a usability or conversion verdict. It shares the rules of scripts/article_inquiry_probe.py: on the 36 cached article pages, all 11 metrics match the published CSV.
Logic: js/inquiry-check.js (no dependencies, no network); scripts/test_inquiry_check.js covers 15 assertion groups (message/search detection, hidden and buttons, four label sources, tel/mailto/contact, QR and WeChat, path score, case, CSV). Parity script: scripts/parity_inquiry_check.js. Run:
node scripts/test_inquiry_check.js
Related: the article inquiry-path pilot, the contact-page form pilot, and the homepage form-input pilot., and the homepage inquiry-path pilot