eNeighbor Accessibility

We want eNeighbor™ to work for as many people as possible. This page describes what we test for, what we know is not covered, and how to tell us when something isn't working for you.

What we aim for

Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, applied to the eNeighbor pages on curlewlabs.com and to the eNeighbor iOS and Android apps. The automated text-contrast checks on the eNeighbor iOS and Android apps use the stricter Level AAA threshold (7:1 for normal text, 4.5:1 for large text). We don't claim full Level AAA conformance.

How we check

Every change to the eNeighbor pages on curlewlabs.com is scanned automatically before it ships, using axe-core (run by pa11y-ci) against WCAG 2.1 Level A and AA plus axe's best-practice rules. Issues the scanner reports are fixed before the change ships; we do not maintain an ignore list of accepted defects.

Every change to the eNeighbor iOS and Android apps is checked automatically in CI before it ships. We render every user-facing screen and dialog at three system text scales (100%, 150%, and 200%) and verify:

• Tap targets are at least 48 dp on Android and 44 pt on iOS (WCAG 2.2 §2.5.8 Target Size (Minimum)).
• Every tappable control has an accessible label that screen readers can announce (WCAG 2.2 §4.1.2 Name, Role, Value).
• Text contrast meets the AAA threshold of 7:1 for normal text and 4.5:1 for large text — exceeding the AA requirement of 4.5:1 / 3:1 (WCAG 2.2 §1.4.6 Contrast (Enhanced)).
• The page renders at 200% text scale without controls or content being clipped (WCAG 2.2 §1.4.4 Resize Text).
• Every heading carries a meaningful name that a screen reader can announce — not blank, and not a bare control-type word like "Button" or "Tab" (WCAG 2.2 §2.4.6 Headings and Labels).
• Every screen you navigate to exposes a descriptive title that a screen reader announces on arrival, so you know which screen you have landed on; pop-up dialogs are announced with your device's standard dialog cue and their message (WCAG 2.2 §2.4.2 Page Titled).

One screen is excluded from this automated rendering: the QR scanner's live camera viewport, which shows the physical world rather than rendered UI controls — there is no label, contrast pair, or tap target for the automated matchers to assess. The scanner's static chrome (page title, back button, and the error fallback shown when the camera is unavailable) is rendered and checked.

These automated checks are not a full WCAG audit — they cover the six success criteria named above and not the rest of the standard.

We do not currently run any of the following:

• A third-party accessibility audit.
• Systematic manual testing with screen readers (VoiceOver, TalkBack, NVDA, JAWS) or other assistive technology.
• Automated checks that cover all of WCAG 2.2 Level AA on the eNeighbor iOS and Android apps. The checks above cover only the six criteria they name.

Conformance status

The eNeighbor pages on curlewlabs.com partially conform with WCAG 2.2 Level AA. "Partially conforms" means some parts of the content do not fully conform to the standard, as described under Known limitations below.

The eNeighbor iOS and Android apps are not assessed against WCAG 2.2 Level AA in full. The six success criteria named under How we check are verified automatically on every change; we have not commissioned a full audit covering the rest of the standard. Per the W3C accessibility statement guidance, content without a complete evaluation result is reported as "Not assessed," not as conformant or partially conformant.

Known limitations

On the eNeighbor pages on curlewlabs.com, our checking is automated only, so the following are not guaranteed to be covered:

• The five WCAG 2.2 AA success criteria that depend on user behavior and are not statically detectable by any tool we know of: Focus Not Obscured (Minimum), Dragging Movements, Consistent Help, Redundant Entry, and Accessible Authentication (Minimum).
• The Target Size (Minimum) criterion (also new in WCAG 2.2). axe-core has a rule for it, but our pa11y-ci runner does not currently pass it through.
• Anything that depends on judgment a static scanner cannot make — for example, whether alt text is meaningful, or whether heading order matches the actual visual structure of a page.

Technical specification

The eNeighbor pages on curlewlabs.com use HTML, CSS, and a small amount of JavaScript. The eNeighbor mobile apps are built with Flutter, targeting iOS and Android.

Feedback

If you encounter an accessibility barrier on the eNeighbor website or apps, please tell us:

We aim to acknowledge accessibility reports within 90 calendar days of receipt and to handle complaints directly.

Review

This statement was last reviewed on 2026-07-13. We review it at least once a year and after any significant change to the eNeighbor website or apps.