Samuel Price, Editor and Writer at Qaveridia

What Samuel writes

Samuel writes and maintains the guides in the resources section, the service descriptions, the tool instructions and the site's policy pages. The subjects are practical: how to plan testing, how to write bug reports and test cases, which browsers to test, how to check forms, security settings and search metadata before launch, and what testing costs.

Why a pen name

The site is published under the Qaveridia name, and the writing appears under one consistent byline so readers know the same editorial standards apply across every page. With a pen name, attention stays on what each guide says and where its facts come from, not on a personal biography. It does not reduce accountability: every page states when it was last updated, every factual claim is sourced, and corrections are handled as the editorial policy describes.

What Samuel does not claim

Samuel Price is not presented as a certified tester, a lawyer, an accessibility auditor or a security specialist, and the guides do not rely on claimed credentials. Where a guide discusses standards or rules, such as WCAG 2.2, the European Accessibility Act, the GDPR or the OWASP Top 10, it quotes or links the primary source so you can check it yourself, and it labels secondary and commercial sources as such.

How the guides are checked

Each guide is checked against its sources before publication and again when a cited source changes. Claims about laws and standards follow the wording of the source rather than a summary of a summary. Nothing is described as tested or measured unless it was. Examples are labelled as illustrative when they are invented.

How a guide gets made

Each guide starts from a question someone running a website would ask, such as which browsers to test or why enquiries stopped arriving. Samuel drafts the answer first, in a few sentences, then works out what the reader needs in order to act on it: the steps, the checks, the limits. Every factual claim is traced to a source before the guide goes live, and the source list at the foot of the page records which documents were read and when.

Drafts are checked against the site's own rules: no invented figures or clients, no claims of testing that did not happen, no sweeping statements without evidence, and plain Irish and British English throughout. Examples that are made up to show a format, such as the fictional bakery on the sample reports page, are labelled as illustrative wherever they appear.

What Samuel will not write about

The guides stay within website testing. Samuel does not write legal opinions, security research, product reviews or rankings of testing companies, and does not accept requests to mention a product in return for anything. Where a guide reaches the edge of its subject, for example the point where a configuration check would need to become a penetration test, it says so and suggests what kind of specialist to look for instead.

Guides by Samuel

Contact the editor

Corrections, questions and suggestions for new guides are welcome. Write to hello@qaveridia.online or use the contact page, and mention the page you are writing about.

Samuel Price