About Qaveridia

Why Qaveridia exists

Websites launch with defects that nobody looked for. A contact form sends to an old inbox. A checkout fails on one phone. A staging rule keeps the whole site out of search. None of these are hard to find; they are just easy to miss when the people checking are the people who built the site and know where not to click.

Qaveridia exists to be the second look. The name nods to verification, and the tagline says what we do: test, improve, launch.

Testing kept separate from building

We test websites built by anyone: agencies, freelancers, in-house teams or owners who built their own. We do not fix the defects we find, and a QA review never depends on buying a build. That separation keeps the findings neutral: a report describes what is broken, and whoever built the site decides how to repair it.

The commercial-interest note in the footer of every page explains the one connection a reader should know about.

How we work

• Scope in writing. Every engagement starts with a written list of what will and will not be tested.
• Evidence on everything. Each defect carries the page, the environment, the steps and a screenshot or recording.
• Fixes confirmed. A defect stays open until the fix has been seen working on the agreed browsers and devices.
• Plain language. Reports are written for the person deciding, with technical detail underneath for the person fixing.
• Honest limits. Reports say what was not tested. A clean result is never presented as more than it is.

The process page goes into each stage in detail.

Three commitments

We will not claim tests we did not run. If screen reader testing, a device, or a browser was not part of the work, the report says so.

We will not inflate findings to look busy, or play them down to please anyone. Severity follows impact, and we explain our reasoning.

We will not pretend to be something we are not. We are not penetration testers, accessibility auditors issuing conformance statements, or a law firm. When you need one of those, we say so.

Who we work with

Charities, membership bodies, professional practices and other small or medium organisations, plus the agencies and freelancers building their sites, in Ireland and elsewhere in the EU. Work is done remotely and in English.

A new practice

Qaveridia is new. We have no case studies, client logos or testimonials to show, and we will not invent any. The sample reports page shows our report format with a fictional project, clearly labelled. Judge us on the scope, the questions we ask, and the first report.

What a first engagement looks like

If you have never worked with an outside tester, the first engagement can feel unfamiliar, so here is what to expect. You send a short brief. A free reply by email, without obligation, says whether and how we could help, and asks anything we need to know. If you go ahead, we send a written scope and a fixed quote. Before testing starts, you see the test cases for the main flows and can correct anything we have misunderstood about your business. During testing, defects appear in a shared list as they are found, each with evidence, so your developers can start fixing straight away. We go through the list with you, agree what blocks launch, retest fixes in the rounds the quote sets, check the live site after go-live if that is quoted, and hand over a short summary you can keep.

At no point do we need access to your hosting control panel, your code repository or your live payment account. Where a flow needs an account, we ask for a test login created for the purpose.

Where we draw lines

A testing practice is only useful if its findings can be trusted, so some boundaries are fixed:

• We do not accept payment from platforms, tool vendors or agencies for recommending them.
• We do not soften a finding because a client's developer or agency would prefer it softer.
• We do not mark a defect as fixed until we have seen the fix work.
• We do not keep testing data longer than the engagement needs; test accounts and test messages are listed for removal at the end.

If any of those lines ever has to bend for a specific reason, the report will say so.

Who writes here

The guides and pages on this site are written by Samuel Price, a pen name used by the site's editor. The author page explains why a pen name is used and how to reach the editor. Our editorial policy sets out how claims are checked and sources labelled.

The free tools

The four browser tools cost nothing and run in your browser. They exist because good testing habits are useful whether or not you ever hire a tester, and because a site owner who writes clear bug reports gets fixes faster from anyone.

Languages and location

Qaveridia works in English, remotely, with organisations in Ireland and across the EU. Testing is carried out on real browsers and devices and, where helpful, cloud device services. Reports use Irish and British spelling and euro pricing. If your site serves visitors in other languages, we can test the language versions for layout, links and form behaviour, though we do not review the translated text itself.

Contact

The quickest way to reach us is the contact page, or email hello@qaveridia.online.