Contact WebTech1223411

This is where you get in touch with the people behind WebTech1223411. We keep the process simple on purpose: a single address for everything to do with our front-end, back-end, browsers, dev tools and accessibility coverage, and a few notes below on how to make a message easy to reply to.

Where to write

[email protected]

Everything arrives in the same inbox and is read by somebody whose name appears on the articles.

Telling us we made an error

Found a mistake? Name the page and the exact wording, and tell us what the truth is. Blunt is fine. How we log and mark a fix is written up in the editorial policy.

What we cannot do

What lands outside our reach: personal advice, disputes with other companies, and anything tied to an account we have no part in. WebTech1223411 deals in general guidance about front-end, back-end, browsers, dev tools and accessibility, as the legal notice sets out.

How quickly we answer

A working day or two is typical. Silence past a week almost always means the message never landed, so resend it before assuming you were brushed off.

Before you send it

Tell us exactly what you are after and you will hear back sooner. Broad messages sit longer only because they take more unpicking.

1. Request first, story second. We act on the request and read the story for context.
2. The URL, not a summary of it. Pasting the link is faster for both of us than describing the page.
3. Symptom and expectation. What the page did and what you thought it would do, side by side.

Who reads this

Messages are read by the same small group who write for WebTech1223411. There is no outsourced desk and no intern filtering the inbox before a decision maker sees it.