A/B Testing Tenders

Two routes. Search the portals for what is already advertised, or get in earlier by tracking the buyers who commission this work on a cycle. Stotles pulls notices from 100+ portals into one search, so an accessibility audit posted on a Welsh or Irish portal shows up beside the Contracts Finder ones. Platform-wide, 2,140 notices are open right now across every topic.

Two carry most of it: 79212000 (Auditing services) and 72800000 (Computer audit and testing services). Run alongside this page's keyword filter, 79212000 returns 32 notices and 72800000 returns 26.

Neither is stored as a filter here. The site AND-combines stored codes with the keywords, which would cut this page from 604 notices to 147, so the keywords do the work on their own.

No. Accessibility testing checks whether a service works for disabled users and meets the WCAG standard, and for public sector websites it is a legal requirement rather than a choice. A/B testing compares two versions of a page to see which one performs better.

This page covers both because buyers tend to buy them from the same sort of supplier, and because in notices A/B work is almost never called A/B testing. It appears as conversion rate optimisation, or as a split testing tool.

604 notices match this page's filter across every stage, and 315 of those are awarded contracts rather than live opportunities. Another 19 sit at pre-tender, which is where the early signal is: a buyer describing an accessibility audit before any tender exists.

Open tenders are the smallest slice by a wide margin. Waiting for one to appear is a poor strategy on this topic.

Central government agencies, councils, universities, NHS bodies and arms length public bodies all turn up in the 50 notices sampled for this page. The work is usually small and specific: one audit of one website, or a rate card for repeat audits across a portfolio of sites and apps. Training for in house accessibility auditors comes up as its own contract too.