What we are aiming for, what we know is broken, and what we have not tested yet. This page is deliberately specific: a statement that claims more than we have measured is worse than none.
Our target is WCAG 2.1 Level AA.
Current status: does not conform. BGPScout does not currently meet WCAG 2.1 AA. The barriers listed below are known and unresolved.
Last assessed 2026-07-30, by self-assessment. Two passes were run: a review of all 105 page templates, and an automated scan (axe-core) against the running site. The template review found 431 markup-level problems, of which 84 - every page failing to declare its language - have since been fixed.
The automated scan found no violations on the five public pages it could reach. That result is narrower than it sounds, and we would rather say so than let it stand as a clean bill of health: it covers five pages out of a hundred, it could not check colour contrast, and it could not test the interactive maps at all. The rest of the site - everything behind sign-in, where most of the problems below live - has not been scanned yet.
We have not done keyboard-only testing or screen-reader testing. Those are the tests that matter most, and they are the ones still outstanding.
We are publishing this before the full audit rather than after, because the barriers we already know about are worth telling you about now.
These are confirmed, not suspected.
73 templates have no top-level heading, so jumping through headings - a primary way to navigate with a screen reader - has no entry point for the page topic.
151 form controls across 42 templates have no accessible name; a further 106 rely on placeholder text, which disappears as soon as you type and is not a dependable label. Affected fields are mostly filters and search boxes inside the application.
Many data tables let you click a row to open its detail page. That behaviour has no keyboard equivalent, so the row is unreachable without a pointing device. Every table with clickable rows is affected. Where a row has a link inside it, that link does work with a keyboard.
The IP-density heatmap at /prospect/ip-density and the ASN location maps are interactive map canvases. Map interfaces of this kind are difficult to make usable with a keyboard or a screen reader, and we have not made ours usable that way. There is currently no text or table alternative presenting the same data. We consider this the most serious barrier on the platform.
Being honest about the gaps matters as much as listing the barriers. None of the following has been assessed:
Until that testing happens, assume there are barriers beyond the ones listed above.
If something on BGPScout blocks you, please tell us - including things not listed above. Email [email protected].
We aim to respond within 5 business days, and we will tell you whether we can fix it, when, and what to do in the meantime. If you need data you cannot reach through the interface, say so - we can often supply it directly, and our API and MCP server expose the same data in a form that does not depend on the visual interface at all.
This statement covers bgpscout.io, including the public marketing pages and the logged-in application.
Prepared 2026-07-30. We will review it when the browser-based audit is complete, and at least annually thereafter. A French translation is planned and not yet available.
BGPScout is operated by Hive Data Center Inc., Montreal, Quebec, Canada.