Accessibility Statement
Swapps builds software for a living, so an inaccessible website of our own is not a small irony. This page says what we are aiming for, what we actually measured, what we know is still wrong, and how to tell us when we have got in your way.
What we are aiming for
swapps.com is built to conform to WCAG 2.2 Level AA, the level public bodies and most private organisations in the United States are held to in practice under the ADA and Section 508.
Today swapps.com is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the site meets the standard and some parts do not yet, or have not been checked. We are not claiming full conformance, because the checks behind it have not all been done.
- We target Level AA, not Level AAA. AAA is not expected to be met in full across an entire site, and saying otherwise would be a claim we could not keep.
- We treat accessibility as part of building a page, not as a pass at the end of a project.
What we actually measured
On 2026-11-15 we ran an automated WCAG audit over 7 key pages of this site, each in English and Spanish, and each at a desktop width of 1280x800 and a mobile width of 390x844. That is 28 separate runs, using axe-core 4.14.0 in a headless browser against the rule sets for WCAG 2.0, 2.1 and 2.2 at levels A and AA.
The pages covered were the home page, the services index, the case studies index, the Platform page, the contact page, the privacy policy and this statement itself, in both languages.
The run found one blocking problem, and it is fixed: on narrow screens, the client logos on the home page were links with no readable name, because the images they contain had not loaded yet. A person using a screen reader or tabbing through the page reached five links that announced nothing. Repeating the audit after the fix reports no remaining violations of critical or serious impact on the pages listed above.
- Audited: home, services, case studies, Platform, contact, privacy and this page, in English and Spanish, at 1280x800 and 390x844.
- Result after fixes: no critical or serious violations reported by axe-core 4.14.0 on those pages.
- Still open: 31 elements the engine declined to decide on, listed below, which need a person to look at them.
What we know is still missing
This is the part of an accessibility statement that is usually left out. These are the gaps we know about on the day above.
- Embedded third-party components
- The site loads components we do not write: the chat widget, Google reCAPTCHA, and tags delivered through Google Tag Manager. We cannot rewrite their markup, and they did not load in the audited environment, so they were not measured. If one of them blocks you, tell us and we will find another way to offer you whatever it was doing.
- Pages we did not audit
- The audit covered 7 pages in each language. Blog articles, individual case studies, the glossary, the lab, the jobs page and the style guide were not included in this round. Blog content comes from a separate publishing system, so its accessibility depends partly on how each article was written.
- An automated audit is not the whole picture
- Automated tools reliably catch only a portion of the WCAG criteria. Things like whether a heading actually describes its section, whether alternative text is meaningful rather than merely present, or whether a flow can be completed end to end with a screen reader, need a person. We have not yet done a manual audit or testing with people who use assistive technology.
- Colour contrast that an automated tool cannot judge
- Across the audited pages the engine returned 31 elements it declined to rule on rather than guess. Almost all are text drawn over a gradient or a photograph, where there is no single background colour to measure against: hero headings and subtitles, call-to-action blocks, the consent notice and several buttons. One more is the link to the cookie policy inside a paragraph of the privacy policy, where the tool cannot tell whether the link is distinguished from the text around it by more than its colour. Each one is listed in the audit report and needs a person to judge it; until that happens we are not claiming they pass.
Tell us if something blocks you
If any part of this site stops you from doing what you came to do, we want to hear about it, and you should not have to phrase it as a bug report. Write to results@swapps.com and tell us what you were trying to do and where it went wrong.
It helps if you can tell us the page address, what you were using to browse it, and what happened instead of what you expected. It is fine if you cannot; tell us anyway.
We aim to reply within five working days. If what you needed is on a part of the site that is failing you, we will get you the information another way while we fix the page.
- Email: results@swapps.com
- We also answer through the contact page and the support centre, linked below.