How do you price government software testing?

Start with a free one-week proof of concept. After that, fixed-price packages start from $499, and dedicated engineers are billed monthly. We can also price against your procurement format.

How quickly can you start?

A pilot usually starts within a few working days of the first call. Dedicated testers can join your team in 3 to 5 days, subject to your onboarding and security checks.

Do you test accessibility manually?

Yes. Automated tools like axe and WAVE are the start, not the end. Testers use keyboards, NVDA, JAWS and VoiceOver, and check every issue again once it is fixed.

Can you test in English and French, or other languages?

Yes. We check every page, form and email in each required language for completeness, consistency and layout.

Do you provide audit-ready documentation?

Yes. Test plans, traceability, accessibility reports and VAPT findings are delivered in a format procurement and audit teams can file.

Can you work with our security clearance and onboarding rules?

Yes. We sign your NDA and data agreements before access, work in your environments and tools, and follow your onboarding and background-check process.

Do you work with GovTech vendors as well as agencies?

Yes. We test for public bodies directly, and for vendors whose software is used by many agencies at once.

Which tools do you use?

Azure DevOps and Jira for tracking; Playwright and Postman for automation and APIs; axe, WAVE, NVDA, JAWS and VoiceOver for accessibility; JMeter for load; OWASP ZAP, Burp Suite and SonarQube for security; BrowserStack for browsers.

Do you test for Section 508 and AODA?

Yes, we test for Section 508 and AODA, the accessibility obligations for public bodies in the US and Canada. We test WCAG 2.1 and 2.2 AA by hand with keyboards, screen readers and zoom, alongside automated scans, and hand over evidence you can use in procurement and compliance reviews.

Do you test bilingual sites?

Yes, we test bilingual sites. Every page, form and email is checked in each official language across 30+ browser and device combinations, so content, layout and notifications work the same for every citizen. We also test accessibility, security and integrations, so public services stay dependable and usable by everyone.

[ Government software testing services ]

Government software testing that serves every citizen, in every language, on every device.

QA engineers for public-sector agencies and GovTech vendors. We test accessibility, security, bilingual content and integrations, so public services are dependable, compliant and usable by everyone.

Get a free test assessment See client results

ISTQBcertified QA engineers
UpworkTop Rated Plus
100%Job Success Score
5.0 Clutch20 verified reviews
400+accessibility issues fixed on a public-sector platform

[ Industry challenges ]

What a bug costs in government software

The failures public-sector teams and GovTech vendors bring to us most often. In government, a defect is also a headline and a complaint.

Services some citizens can’t use

A form that fails with a screen reader or a keyboard shuts people out of a public service, and breaks accessibility law.

Two languages that don’t match

Missing translations, truncated labels and links to the wrong-language page undermine trust in official content.

Citizen and vendor data exposed

Public platforms are high-value targets. One vulnerability can expose personal or procurement data.

Launch-day traffic that takes the site down

Deadlines, announcements and new programmes bring spikes exactly when the public is watching.

Integrations between departments that break

Identity, payments, case management and legacy systems all have to agree, across agencies and vendors.

Audit trails with gaps

Public bodies have to show who changed what and when. Missing records turn a simple question into an inquiry.

[ What we test ]

Testing mapped to the public-service journey

Each practice is pointed at a moment in a citizen’s, vendor’s or staff member’s journey, and links to the full service.

Legal duty

Accessibility & inclusive design

WCAG 2.1 and 2.2 AA tested by hand with keyboards, screen readers and zoom, alongside automated scans, with every issue verified fixed.

Security & VAPT

Vulnerability assessment and penetration testing of portals, APIs and cloud configuration before every major release.

Forms, workflows & case management

Applications, permits, procurement and case workflows tested end to end, including approvals and notifications.

Bilingual & cross-browser

Every page, form and email in each official language, across 30+ browser and device combinations.

Performance & peak load

Deadline days, programme launches and announcements simulated before the public arrives.

Integrations & regression

Identity, payment, CRM and legacy integrations, with repeatable regression on every release.

Audit & documentation

Test plans, evidence and traceability that procurement officers and auditors can follow.

[ Test scenarios ]

The checklist behind every release

Pick an area to see the scenarios we run, and the client platform where they matter most.

Where it matters · {{ ecCur.client }} {{ ecCur.product }} {{ ecCur.proof }} About our work with {{ ecCur.client }}

[ Compliance & standards ]

Tested against the rules public services answer to

Accessibility, language, privacy and security obligations are written into law and procurement contracts. We test the controls and hand over evidence.

WCAG 2.2 · AODA · Section 508 · ADA

Accessibility obligations for public bodies in Canada and the US, tested by hand and with automated tools.

Official languages

English and French, or the languages your jurisdiction requires, checked for completeness and consistency on every screen.

Privacy · FIPPA · PIPEDA · GDPR

Personal data collection, consent, retention and access tested against the privacy rules you operate under.

Security · OWASP · SOC 2 · FedRAMP-ready

OWASP Top 10 testing, cloud configuration and audit trails, with evidence your security and procurement teams can use. We test; we don’t certify.

[ Platforms, integrations & tools ]

The stack we test public-sector software on

If your platform or integration isn’t here, we’ll say plainly where we need ramp-up time.

Products & services

On client projects

Procurement platforms

Bilingual public websites

Vendor & buyer portals

Citizen engagement

Digital government services

PWAs

Public APIs

Platforms & integrations

What we test against

Microsoft Azure

AWS GovCloud

Drupal & WordPress

Identity & SSO

Payment gateways

CRM & case management

Email & SMS notifications

Accessibility & automation

Our engineers’ stack

axe DevTools

WAVE

NVDA & JAWS

VoiceOver

Playwright

Postman

BrowserStack

Azure DevOps

Performance & security

Our engineers’ stack

JMeter

OWASP ZAP

Burp Suite

SonarQube

All testing tools we use →

[ Case studies & results ]

A provincial agency and a GovTech platform

Public-sector procurement for Ontario, and digital-government software used by public bodies across North America.

Public-sector procurement · Ontario, Canada

Supply Ontario

1,800+test cases across websites, PWA, APIs and integrations

400+accessibility issues found and verified fixed

0critical or high vulnerabilities open at release

30+browser and device combinations on BrowserStack

The challenge

The provincial Crown agency that centralises supply chain and procurement for Ontario’s public sector. Its bilingual website, buyer and vendor services and Azure integrations all have to meet accessibility law, protect procurement data and work identically in English and French.

Our approach

Four full-stack QA engineers inside Azure DevOps sprints
Manual WCAG 2.0 AA testing with screen readers, axe and WAVE
English and French parity on every page, form and email
VAPT with OWASP ZAP and SonarQube before each release
JMeter load tests ahead of major calls for vendors

Read the Supply Ontario case study

GovTech platform · North America

Granicus

Digital-government software for public bodies: websites, citizen communications, meetings and digital services. One release reaches many agencies at once, so quality has to hold for all of them.

Visit granicus.com

What we test

Accessibility of public-facing templates
Citizen sign-up and subscription flows
Multi-tenant configuration per agency
Forms, notifications and content publishing
Cross-browser and mobile layouts
Regression across shared components

[ How we work ]

Five steps, starting with a free pilot

The same process on a one-week pilot or a multi-year engagement. Only the scope changes.

01Day 1–2DiscoveryWe walk your services, users, integrations, obligations and release calendar with your team and procurement contacts.
02Week 1Test strategyA risk map ranked by public and compliance impact, the scenario checklist and a browser and assistive-tech matrix.
03Every sprintExecutionManual, accessibility, security, automation and load testing on every build, inside your tracker.
04Daily & weeklyReportingDaily progress in your tracker, a weekly report, and severity-ranked findings with steps, screenshots and video.
05OngoingContinuous supportRegression on every release, launch-readiness runs before deadlines, and evidence packs for audits.

Engagement models

Compare all six models →

Pilot · Lowest riskFree 1-week POCA risk map, first findings with evidence and a test plan you keep. No commitment. Project-basedFixed packages from $499Agreed scope and end date: an accessibility audit, a VAPT round, a launch-day load test. Dedicated team2–10 engineers, monthlyQA engineers who join your sprints, available in 3–5 days.

[ Why QAonTOP ]

Why public-sector teams pick us, and stay

Public-sector domain, from live services

A provincial procurement agency and a GovTech platform tested for real, not just listed on a slide.

Certified, in-house engineers

ISTQB-certified QA engineers employed by QAonTOP, not freelancers passed between projects.

Accessibility tested by people

Screen readers, keyboards and zoom used by testers, not just automated scanners.

Evidence procurement can file

Test plans, traceability and reports ready for audits, contracts and accessibility reports.

Public data stays protected

NDA signed before access, synthetic data by default, and every test asset stays yours.

[ Social proof ]

Team really stepped up our testing with AI-driven automation. QAonTOP has improved product quality, and earned more clients. They feel less like a vendor and more like a true growth partner.

Lior M., CEOQAonTOP client Verified client

Clutch5.020 verified reviews

Upwork5.070+ verified reviews

Google5.040+ reviews

Public-sector clients

[ Free checklist ]

Public-service launch readiness checklist

Not ready to talk yet? Take the checks we run before a public launch, a new programme or a procurement deadline, with what a pass looks like for each one.

AccessibilityWCAG AA by hand and tool
LanguageEvery string in every language
SecurityNo critical or high issues open
LoadDeadline-day traffic holds
IntegrationsIdentity and payments agree
EvidenceAudit pack ready

Check your inbox.

The checklist is on its way. When you want a second pair of eyes before a release, book a free assessment.

[ FAQ ]

Questions public-sector teams ask us first

[ Contact us ]

Get a free test assessment of your platform

✓ Free one-week POC✓ NDA before access✓ A QA lead replies the same day

Book a free consultation

Related industries

All 14 industries →