How is non-functional testing different from functional testing?

Functional testing asks “does this feature do what it should?” Non-functional testing asks “how well does it do it, for whom, and where?” A checkout can pass every functional test and still fail a screen reader user, break in German or freeze on an older Android phone. Most products need both.

Which non-functional testing services do you offer?

Usability, accessibility, localization, compatibility, internationalization and regulatory compliance testing. Performance and security testing are also non-functional, and each has its own dedicated service page.

Which accessibility standard do you test against?

WCAG 2.2 level AA as the baseline. Depending on where you sell, we also map results to Section 508 and the ADA in the US, EN 301 549 in Europe and AODA in Ontario.

Do you test with real screen readers?

Yes. We test with NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android, because each one announces content differently and users notice.

Can automated tools find all accessibility issues?

No. Tools such as axe and WAVE are fast and catch issues like missing labels or poor contrast, but they can’t judge whether alt text makes sense, whether focus order is logical or whether a screen reader user can complete a task. That needs a person.

What is the difference between localization and internationalization testing?

Internationalization testing checks that your code can support other languages and regions at all: text stored outside the code, Unicode, right-to-left layouts and locale-aware formats. Localization testing checks each translated version: that the words are right, fit the layout and suit the market.

Which languages can you test?

We test English and French as standard and bring in native speakers for other languages, agreed with you per project. We can also work alongside your own translators or translation agency.

How do you decide which browsers and devices to test?

We start from your analytics, so the matrix reflects the browsers, operating systems and devices your users really have, then add any versions you have promised to support. Everything else is covered with sampling on a device cloud.

Can you make us GDPR, HIPAA or PCI DSS compliant?

We test the controls that these regulations require and give you clear evidence of what passed and what didn’t. We are not an auditor and don’t issue certificates, but our evidence makes your audit faster.

Do you run usability testing with real users?

Yes. We recruit people who match your users, give them real tasks and record where they succeed or struggle. We combine this with an expert review so you get both evidence and recommendations.

When should non-functional testing happen?

As early as you can. Internationalization and accessibility are much cheaper to fix while a feature is being built. Usability, compatibility and compliance checks then belong before every major release.

What do we receive at the end?

A findings report ranked by impact, mapped to the relevant standard, with screenshots or recordings for each issue. After fixes we retest and provide a clean evidence record, which you can use for audits, bids or your accessibility statement.

How do we get started?

Book a call or send the form on this page. We start with a free one-week proof of concept on one key journey, so you can see the depth of our findings before you commit.

Non-Functional Testing Services

Q: What is non-functional testing?

Non-functional testing checks how well your software works rather than whether a feature works. It covers qualities such as how easy it is to use, whether people with disabilities can use it, how it behaves in other languages and regions, whether it works on your users’ browsers and devices, and whether it meets the regulations you operate under.

Your features work. Now make sure everyone can use them: on any device, in any language, with any ability, and within the rules of every market you sell in.

We test the qualities users feel before they ever report a bug: how easy your product is to use, whether people with disabilities can use it, how it reads in another language, whether it works on their browser and device, and whether it holds up to the regulations you operate under.

Get in touch Check your readiness

6 non-functional testing types
WCAG 2.2 AA, Section 508, EN 301 549
Real screen readers and devices
Free one-week POC

Jump to a testing type

Usability TestingReal users Accessibility TestingWCAG 2.2 AA Localization TestingEach market Compatibility TestingBrowsers & devices Internationalization TestingReady for any locale Regulatory Compliance TestingEvidence for audits

Also non-functional: Performance · Security

[ Why non-functional testing ]

Working isn’t the same as working well

A feature can pass every functional test and still let users down. The sign-up form works, but a screen reader can’t find the submit button. The price is right, but shows the wrong currency format in Germany. The page loads, but the layout breaks on the phone half your customers own. Non-functional testing finds these gaps.

Functional testing asksDoes it work?

Can a user sign up?
Is the total correct?
Does the order go through?

Non-functional testing asksHow well, for whom, and where?

Can every user sign up, easily?
Is the total shown right in every locale?
Does it work on their device?

Fewer users lost to friction

People rarely report confusing screens. They just leave. Usability testing shows you where and why.

Open to every customer

Around one in four adults lives with a disability. Accessible products reach them and lower your legal exposure.

Ready for new markets

Find layout breaks, wrong formats and awkward translations before your new customers do.

Evidence buyers trust

Enterprise and public-sector buyers ask for accessibility and compliance proof. You’ll have it ready.

[ 6 non-functional testing types ]

Six ways we test how well your product works

Each type answers a different question about quality. Here is what each one covers, when you need it and what you receive.

Usability Testing

Real users

View service

We watch real people try to complete real tasks in your product, and note where they hesitate, get lost or give up.

What we check

Task success and time on task for key journeys
Navigation, labels and how information is laid out
Onboarding and the first-use experience
An expert review against proven usability principles

When you need it

Before a redesign, when conversion drops, or when support tickets start with “I can’t find…”.

You getFindings ranked by severitySession clips and recommendations

Accessibility Testing

WCAG 2.2 AA

View service

Your product checked against WCAG 2.2 AA with automated scans, careful manual review and the screen readers your users rely on.

What we check

Keyboard-only use and visible focus
NVDA, JAWS, VoiceOver and TalkBack
Colour contrast, text resizing and zoom
Forms, error messages, images and media

When you need it

Before a public launch or procurement bid, or when a customer asks for an accessibility statement.

You getWCAG audit mapped to each criterionRetest report after fixes

Localization Testing

Each market

View service

Translated screens checked in context, so text fits, reads naturally and feels local to the people using it.

What we check

Translation accuracy, tone and terminology
Text that overflows, truncates or overlaps
Dates, times, numbers, currency and addresses
Images, symbols and content that suit the culture

When you need it

Before entering a new market or releasing a new language.

You getLocalization defect log per languageScreenshots of every issue in context

Compatibility Testing

Browsers & devices

View service

Ensuring the compatibility of your software with different devices, operating systems, and browsers.

What we check

A browser matrix based on your real traffic
iOS and Android versions, screen sizes and OEM skins
Windows, macOS and Linux for desktop apps
Older versions and low-end devices you still support

When you need it

Before every major release, and whenever a browser or OS update ships.

You getCompatibility matrix, pass or fail per combinationDevice-specific bug reports

Build your browser coverage matrix →

Internationalization Testing

Ready for any locale

View service

Checks that your code is ready for other languages and regions before translation starts, when fixes are still cheap.

What we check

Hard-coded text outside resource files
Unicode, special characters and right-to-left layouts
Locale-aware dates, numbers, sorting and time zones
Pseudo-localized builds that expose layout breaks early

When you need it

Before you plan a second language or region, ideally while the feature is being built.

You getInternationalization readiness reportPseudo-localization findings

Regulatory Compliance Testing

Evidence for audits

View service

The controls your customers and auditors ask about, tested release by release, with the evidence to show it.

What we check

Accessibility law: ADA, Section 508, EN 301 549, AODA
Privacy: GDPR consent, data access and deletion
Health and payments: HIPAA and PCI DSS controls
Security frameworks: SOC 2 and ISO 27001 controls

When you need it

Before an audit, a regulated launch or an enterprise security review.

You getCompliance test evidence packGap list with priorities

The rules your product is measured by

Buyers, regulators and courts don’t ask whether your product feels accessible or secure. They ask which standard it meets. We map every finding to the standard behind it.

Accessibility

WCAG 2.2 AAThe international benchmark for accessible web and mobile content.
Section 508US federal accessibility requirement for ICT.
ADAUS law that courts apply to websites and apps.
EN 301 549The European accessibility standard for ICT products.
AODAOntario’s accessibility law for public and private organisations.

Privacy & health data

GDPRConsent, data access, correction and deletion for EU users.
HIPAASafeguards for protected health information in the US.

Payments & security

PCI DSSControls for systems that store, process or send card data.
SOC 2Security, availability and confidentiality controls buyers ask for.
ISO 27001Controls within an information security management system.

We test the controls and hand over evidence. We are not an auditor and don’t issue certificates.

[ How we work ]

Six steps from scope to evidence

You always know what we’re checking, why it matters and what you’ll receive. Every report, recording and evidence file belongs to you.

Step 1 of 6
Scope & standards

We agree the journeys, markets, devices and standards that matter, and what “good” looks like for each.

You getTest scope and standards list
Step 2 of 6
Baseline & personas

We map who your users are, the languages they read and the browsers and devices they actually use.

You getUser personasDevice & browser matrix
Step 3 of 6
Audit & sessions

Automated scans, manual expert review, screen reader passes and user sessions, run against the agreed scope.

You getSession recordingsRaw findings log
Step 4 of 6
Report & prioritise

Each finding explained in plain words, mapped to its standard and ranked by impact on users.

You getPrioritised findings report
Step 5 of 6
Fix support & retest

We help your developers understand each fix, then retest until it passes.

You getRetest report
Step 6 of 6
Evidence & sign-off

A clean record of what was tested, what passed and what is still open.

You getEvidence packInput for your accessibility statement

Free one-week POCWe audit one key journey so you can judge the depth of our findings first.
Findings developers can act onEach issue comes with where it is, why it matters and how to fix it.
NDA before accessWe sign your NDA first and use test accounts and synthetic data by default.

[ Tools ]

The tools behind our non-functional testing

28 tools across six jobs. Tools find the obvious issues quickly; our testers find the rest. We’re happy to work with the tools your team already uses.