Accessibility statement. No brand can pay to rank higher on Simscanner.
Simscanner is an independent travel eSIM comparison site that ranks brands country by country, and compares regional plans across the countries each region covers.
Policy · Effective 30 May 2026 · v1

Accessibility statement

Effective 30 May 2026 v1
The policy, in one line

Simscanner targets WCAG 2.2 Level AA across every public page.

This statement records the current conformance level, known gaps under remediation, the testing cadence, and the contact for accessibility escalation. The statement is reviewed against the conformance level on a published cadence and updated when material changes are made.

WCAG 2.2 Level AA

Target conformance

Simscanner targets Web Content Accessibility Guidelines version 2.2 at conformance Level AA across every public page. The target covers visual presentation (contrast, focus indicators, type scaling), structural semantics (headings, landmarks, lists), keyboard accessibility (all interactive elements operable without a mouse), and assistive technology compatibility (screen reader output, voice control). The target is reviewed annually.

Phase 1 baseline

Current state

At Phase 1 launch, Simscanner has been built against the target but has not undergone independent third-party audit. Self-testing across the 57 published routes confirms keyboard reachability of every interactive element, correct heading hierarchy on every page, sufficient colour contrast for body text against the published palette, and screen reader output that announces breadcrumbs, jump-nav, and accordion state. Independent audit is scheduled within 90 days of launch.

Under remediation

Known gaps

Known gaps as of the effective date above: the FAQ accordion uses the native HTML details element which is announced inconsistently across older screen readers; the country card grid uses CSS grid with auto-flow that some screen-reader navigation modes traverse out of source order; the methodology version pill uses a colour-only state indicator that fails Success Criterion 1.4.1 in monochrome. Each gap has a remediation ticket and a target completion date logged internally.

Quarterly review

Audit cadence

Simscanner reviews accessibility quarterly. Each quarter the team runs a structured audit covering navigation, forms, content, and structural integrity across the published routes. New routes are audited before merge. Material findings are added to the Known Gaps list above. Resolved findings are removed and the resolution date is logged in the revision history at the foot of this page.

What to do if a barrier is encountered

Escalation

Visitors who encounter an accessibility barrier on Simscanner are asked to report it. Reports help Simscanner prioritise remediation and may identify gaps the internal audit has missed. Reports are acknowledged within 2 working days. The team aims to resolve barriers within 30 days or to provide an alternative path to the information.

How to reach the accessibility team

Contact

Accessibility barriers and questions should be sent to accessibility@simscanner.app. Visitors may also use the general contact form at /contact and tag the message as accessibility. Phone contact is not currently available; the team aims to add an SMS or voice channel in 2026.

Structured data on this page: Article BreadcrumbList. No FAQPage schema is emitted: this policy is a single declarative document. No Product, Offer, AggregateRating, or Review schema is used.
Notes for the delivery team
  • The build brief's "Crawlable FAQ" instruction asks for a visible FAQ on every page, but the zero-paid-placements content pack explicitly renders no FAQ section and supplies no FAQ copy (section 7 and section 11). The content pack is treated as the source of truth, so no FAQ section and no FAQPage schema are emitted here. Confirm this is intended before sign-off.
  • Enforcement-map cards link to internal QA files (qa/qa-checklist.md, qa/schema-audit.md, qa/internal-link-audit.md) using the ../ relative convention. Confirm those files exist in qa/ at port time.
  • This is the reusable policy template. The same chrome renders /policies/editorial, /policies/data-sources, /about, and the remaining policy family by copy substitution only.
  • Internal links use the ../ relative convention from the brief and resolve to clean URLs after the post-extraction rewrite.