- Courses
- Certifications
- Accessibility Testing
TestingBot Certification Program
TestingBot Accessibility Testing Certification
A resume-worthy credential for the Accessibility Testing Tutorial: WCAG 2.2 course. Prove you can do the work, not just that you read about it: pass a timed exam, then run the course suite on TestingBot. You get a certificate with a credential ID, a QR code and a public verification page.
- Exam
- 20 questions, 30 min
- Pass mark
- 80%
- Practical
- 3 passing on 2 configs
- Cost
- Free, no expiry
The exam and the practical are tied to your TestingBot account, so sign in to start. A free account is enough.
How it works
-
1
Step 1: The exam
20 questions drawn from 30, 30 minutes, pass mark 80%. Not the knowledge-check questions. Explanations after grading; retake after 24 hours, up to 3 attempts in 7 days.
-
2
Step 2: Run your accessibility suite on TestingBot
3 passing browser tests in the build
certificate-accessibility-testingon 2 different browser configurations, in the last 30 days.How to run it
Run the course's accessibility suite (or your own suite with axe scans) on the TestingBot grid in at least two browser and platform combinations, with every session in one build named
certificate-accessibility-testingand its pass or fail status reported.Playwright (TypeScript)
- Create
testingbot.tsandplaywright.testingbot.config.tsfrom Accessibility testing on TestingBot, with at least two projects, for examplechrome-windows(enginechromium) andsafari-macos(enginewebkit). - The helper sets the build through the
buildoption intb:options(documented in the Playwright options reference). Set it withexport TB_BUILD=certificate-accessibility-testing. - Keep the automatic
testingbotStatusfixture intests/axe.ts, so each session sendssetSessionStatus. Sessions without a status do not count. - Export
TB_KEYandTB_SECRETand runnpx playwright test -c playwright.testingbot.config.ts. Each project runs as its own session, so three projects give three sessions.
Selenium (Java)
Alternatively, run the JUnit class from axe-core with Selenium in Java with
TB_BUILD=certificate-accessibility-testing(it is passed asbuildintb:options, see the Selenium test options). Run it for at least two browser or platform combinations by changing theOptionsclass orplatformName, and keep thetb:test-resultcallback so every session reports passed or failed.Finally, open the
certificate-accessibility-testingbuild in the TestingBot dashboard and check that at least three sessions are marked passed across at least two configurations. Scans that are meant to fail, such as the Mars demo test, should be left out of this run. - Create
-
3
Step 3: Your certificate
Unlocks when both steps are done. Choose the name to print, then share the public link or add it to LinkedIn.
Verify a TestingBot certificate
Hiring, or checking a claim on a CV? Enter the credential ID printed on the certificate to confirm it is genuine, see what TestingBot verified and whether it is still valid.