Direct answer: 35 of the 36 article pages offer at least one way to get in touch, but only one page has a message form. Phone links are the most common path (34 pages), followed by contact-page links (27) and email links (25); QR wording appears on 16 pages and WeChat on 15.

The sample contains 21 forms, yet by HTML rules only two can be identified as site search and one as a message form; the other 18 are single text inputs whose purpose cannot be told from the markup. No page offers all four paths (message form, tel, mailto, contact link), and one page (E28) has no contact path at all.

35
pages with a path
1
message form
34
phone links
27
contact-page links
25
email links
21
forms

Method: reuse the study-45 article cache

The study parses the 36 article pages cached on 2026-11-03 08:40–08:41 (10 sites, HTTP 200, HTML ≥5 KB) with zero network requests, and clicks or submits nothing. It counts forms, fields, accessible labels, tel/mailto/contact links and QR/WeChat wording. Five E20 pages of about 1.4 KB are excluded by the size threshold.

ItemRuleBoundary
Message formForm contains a textareaPop-ups and JS-inserted forms excluded
Search formtype=search, name=q/keyword or action containing searchOtherwise unclassified
Fieldsinput/select/textarea except hidden and buttonsVisibility not judged
Accessible labelaria-label, aria-labelledby, title, placeholder, label for or wrapping labelLabel wording not judged
Contact pathtel / mailto links, href with contact/lianxi/aboutKeyword match is a lower bound
QR / WeChatText or image alt matchNo image recognition

Result: phone links dominate, message forms are rare

PathPagesShare of 36
Phone link tel:3494.4%
Contact-page link2775.0%
Email link mailto:2569.4%
QR wording1644.4%
WeChat wording1541.7%
Message form12.8%
Site search form25.6%
At least one path3597.2%

Path counts: three paths on 21 pages, two on 10, one on four, none on one; no page reaches four. In practice, getting in touch relies on phone numbers and navigation links, with almost no on-page messaging.

The only message form: six fields, zero programmatic labels

E26 embeds a product inquiry form with product name, company, contact name, phone, address and message (five text inputs plus one textarea). Each field has visible text in a preceding div, but the page contains no <label> element and these inputs have no placeholder, aria or title, so under the strict rule none of the six fields has an accessible label. It reads fine visually; a screen reader cannot tie the hint to the field.

That also explains the overall ratio: 26 of 32 fields (81.2%) carry a label, mostly placeholders or titles on single search boxes, while the only real inquiry form has none.

Most of the 21 forms are single text inputs

TypeCountNote
Message form (textarea)1E26, six fields
Identifiable search2name=keywords / key
Single text input, unclassified18Likely site search or subscribe

These inputs carry neither type="search" nor name="q", so HTML alone cannot tell search from subscribe; they are recorded as unclassified and are not counted as an inquiry path.

By site

SitePagesFormsMessage pagestel pagesmailto pagesContact pagesNo path
E035505550
E065505050
E095005550
E145005500
E163003000
E191100010
E225005550
E235805550
E261111010
E281100001

E03 and E23 have the most forms, all single text inputs; E16 has phone links only (three pages); E19 has a contact link only; E28's single form is neither search nor message, and the page offers no usable contact path. E23's five pages carry eight forms, the densest in the sample.

Compared with contact pages

MeasureContact pages (study 62)Article pages (this study)
Pages2036
Message forms151
Pages with a form1518 (mostly single inputs)
Form fieldsPhone 9/9, email 6, company 6, captcha 632 fields, 26 labelled
Privacy notice1 formNot measured

Contact pages usually carry an inquiry form (15 of 20); article pages almost never do (1 of 36). An intent formed while reading has to travel to another page, which lengthens the path.

What this means for acceptance

  1. Decide whether articles must capture inquiries. Only 1 of 36 has a message form; acceptance should state whether phone and navigation links are enough.
  2. Keep phone and email links clickable. 34 pages use tel: and 25 use mailto:, the most reliable paths today.
  3. Label forms programmatically. The only message form has visible hints but no label or aria, so screen readers cannot connect them.
  4. Name single-input forms. 18 inputs cannot be identified from HTML; add type="search" or a clear placeholder.
  5. Do not rely on QR codes alone. 16 pages mention a QR code, but scanning leaves the page and produces no trackable on-site inquiry.

Limits

  • HTML only: JS-inserted pop-ups, floating widgets and forms are invisible, so counts may be low.
  • Page level: a site-wide footer form counts for every page; body and template are not separated.
  • Keyword lower bounds: contact links match on href, and QR/WeChat on text.
  • No submission test: whether a form actually sends, has a captcha or a consent checkbox is not judged.
  • 10 sites, 36 pages: a pilot, no industry claim.

Data and reproduction

Anonymised data: equipment-article-inquiry-paths-2026.csv (36 rows × 13 columns: forms, message forms, search forms, fields, labelled fields, tel/mailto/contact links, QR and WeChat, path count). The repository keeps docs/research/2026-11-article-inquiry-paths.csv.

Parser: scripts/article_inquiry_probe.py; unit tests: scripts/test_article_inquiry_probe.py (no network). Run:

python -m unittest scripts.test_article_inquiry_probe

Related: the contact-page form pilot, the homepage form-input pilot, and the article anchor-text pilot., and the inquiry path checker, and the homepage inquiry-path pilot

Sources and definitions

  1. Article cache: 36 pages from 10 sites in study 45 (2026-11-03 08:40–08:41).
  2. Forms: input/select/textarea inside <form>, excluding hidden fields and buttons.
  3. Scan: 2026-11-05, zero network requests, no form submitted.
About the author

Lingyi Information Official (delivery team) works on requirements, proposals and acceptance for corporate websites, brand and smart-manufacturing projects. This article counts forms and contact paths in cached HTML only; it does not judge usability, submission success or conversion, and it collects no personal contact data; the 10-site, 36-page sample is a pilot.

Articles should capture inquiries too

35 of 36 pages offer contact, but only one can take a message; its six fields have no programmatic labels.

Request a recheck plan