Last updated 28 August 2026
On this page
Our commitment
This site should be usable by everyone, including people using screen readers, keyboard navigation, magnification or voice control. The keyboard test and mouse test have specific limits, noted below. That matters here more than on most sites: people often arrive because a device is misbehaving, which is exactly when a difficult interface is least welcome.
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA.
What we have done
Specific measures taken across all pages:
- Semantic structure. One
h1per page, headings in order, real landmarks, and a skip link to the main content. - Keyboard access. Every control is reachable and operable by keyboard, with a visible focus outline that is never removed.
- Contrast. Text and interface colours are chosen to meet the AA contrast ratio against their backgrounds.
- Touch targets. Buttons, links and form controls are at least 44 pixels on touch devices.
- Reflow. Pages work from 320 pixels upward with no horizontal scrolling.
- Reduced motion. Animation is disabled for anyone whose system requests it.
- No colour-only meaning. Test results are always conveyed in text as well as colour, so the status is never carried by a coloured indicator alone.
- Plain language. Guides avoid jargon where a plain word will do.
Known limitations
We would rather name these than imply the site is perfect.
| Area | Limitation |
|---|---|
| Keyboard test | Requires a physical keyboard, and the on-screen layout scrolls sideways on narrow screens. Some keys are intercepted by the operating system and never reach the page. |
| Mouse test | Requires a pointing device with separate buttons. It cannot work by keyboard or touch, and says so on the page. |
| Screen test | Rapidly changing full-screen colours. Anyone photosensitive should advance the colours manually rather than leaving a sequence running. |
| Speaker test | Relies on hearing a tone. There is no visual equivalent of the sound itself. |
| Camera preview | The live image cannot be described by a screen reader. The numeric readout beside it reports resolution, frame rate and device name in text as an alternative. |
Some limitations are inherent: a test of whether a speaker produces sound cannot be completed without hearing, and a mouse button test needs a mouse. Where that is the case we say so plainly on the page rather than leaving people to work it out.
How we assessed this
The site has been checked by internal review, including automated checks across every page at multiple screen widths, keyboard-only navigation, and inspection of contrast and touch target sizes.
It has not yet been audited by an independent third party, and it has not been formally tested with every combination of assistive technology. We do not claim more than we have verified.
Tell us about a barrier
If you cannot use part of this site, please tell us. Reports of specific barriers are the most useful thing we receive, and we treat them as bugs rather than suggestions.
Email contact@test-webcamp.com with the page, what you were trying to do, and the assistive technology and browser you were using if you know them. We aim to respond within a few working days.
If you are not satisfied with our response, you may be able to raise the matter with the equality or accessibility body in your country. In the EU, national enforcement bodies handle complaints under the European Accessibility Act; in the UK, the Equality Advisory and Support Service can advise.
Scope
This statement applies to all pages on www.test-webcamp.com. It does not cover third-party sites we link to, such as manufacturer support pages, which we do not control.
We review this statement when the site changes materially, and at least annually.