Squawk — Accessibility Statement

Last Updated: 12 August 2026

Jamison Tech LLC is committed to making Squawk usable by as many people as possible, including people with disabilities. This statement describes what we have done, what we have not yet done, and how to tell us when we have got it wrong.

1. Conformance Target

We are working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, applied to a mobile application, together with the platform accessibility guidance from Apple and Google.

Current status: not yet assessed. An internal review against WCAG 2.1 AA has been completed and its findings fixed — see Section 3 for what that changed. We are not yet making a conformance claim, because one part of our own assessment method is still outstanding: testing with VoiceOver and TalkBack on physical devices. We will update this statement with a specific conformance claim when that testing is complete.

We would rather tell you that an audit is pending than publish a conformance claim we have not earned.

2. What Squawk Already Does

These are accessibility-relevant properties of the app as built today:

19 languages. The interface, including error messages and notifications, is fully translated into 19 languages, and follows your device’s language preference by default.
Right-to-left support. Layout, alignment, and navigational icons mirror correctly for right-to-left languages such as Arabic.
System text sizing. The app uses the platform’s text scaling, so enlarging text in your device settings enlarges it in Squawk.
Light and dark themes, plus a system-following option.
No time-limited interactions in the core flow. Beacons expire, but nothing in the interface requires you to act within a countdown. Sign-in codes are the one exception, and they can be re-requested freely.
An alternative to camera QR scanning. Contacts can be added by pasting an invite link instead of scanning a code, so the flow does not depend on aiming a camera.
Manual entry as an alternative to the map. Cities and venues can be typed in directly rather than selected from the map, so dropping a beacon does not require interacting with a map surface.

3. Known and Anticipated Limitations

We expect the pending review to find issues. These are the areas we already consider most likely to present barriers:

The map picker. Selecting a location on a map is inherently visual, and the map is a third-party component whose accessibility we do not fully control. Alternative: type your city or venue name instead. This path is fully supported and produces the same result.
The QR code display and scanner. Camera-based scanning is not usable by everyone. Alternative: the invite link can be copied and shared through any messaging app, and pasted by the recipient.
Screen reader labeling — reviewed, but not yet tested with a screen reader. Every form field, button and icon has been given an accessible name, headings have been marked so you can navigate between sections, and status messages are announced when they appear. Keyboard navigation, focus order and text scaling have been checked by hand. Still outstanding: none of this has yet been verified with VoiceOver or TalkBack running on a real device, which is the only way to confirm what is actually announced. We expect that testing to find issues.
Color contrast — measured and fixed. Every color pair in the app and on this website has been measured against the WCAG 2.1 AA ratios (4.5:1 for text, 3:1 for interface elements), and the pairs that fell short were corrected in both light and dark themes.
Touch target sizes — measured. Interactive controls are checked against the Apple and Google minimums by automated tests that run with every build.

If you encounter a barrier that is not listed here, please tell us — see Section 5.

4. Compatibility With Assistive Technology

Squawk is intended to work with the accessibility features built into iOS and Android, including:

VoiceOver (iOS) and TalkBack (Android)
Display and text size settings, including bold text and larger accessibility sizes
Screen magnification and zoom
Reduce Motion and Reduce Transparency
External keyboard navigation
Voice Control and Voice Access

Our testing will cover current versions of iOS and Android; older operating system versions may behave differently. As noted in Sections 1 and 3, that device testing has not happened yet — the mobile builds do not exist. Until it does, treat this section as what Squawk is built to support rather than what we have confirmed.

5. Feedback — Please Tell Us

If you encounter an accessibility barrier in Squawk, we want to hear about it. Accessible alternatives are available to us in most cases, and a specific report is far more useful than a general one.

In the app: Settings → Help → Send feedback
Email: squawk@jamisontech.com
Phone: +1 (605) 310-7796
Post: Jamison Tech LLC, 6150 64th Ln, Norwalk, IA 50211, United States

Please describe what you were trying to do, what happened, and what assistive technology and device you were using.

We aim to respond within 5 business days, and to tell you either how to work around the problem now or when we expect to fix it. If you need information from the app in an alternative format, ask and we will provide it.

6. How We Assess Accessibility

Self-evaluation against WCAG 2.1 Level AA and the Apple and Google platform accessibility guidelines.
Assistive technology testing with VoiceOver and TalkBack on real devices.
Automated checking using the accessibility tooling in the Flutter framework and the platform inspectors.
User feedback, through the channels in Section 5.

We treat reported accessibility defects as ordinary bugs, prioritised by the severity of the barrier rather than by how many people report them.

7. Enforcement and Escalation

If you report an accessibility barrier and are not satisfied with our response, you may escalate by writing to Jamison Tech LLC at the postal address above, marked for the attention of the owner. We will review the matter directly.

8. Changes to This Statement

We will update this statement when the pending accessibility review is complete, when known limitations are resolved, and whenever significant changes to the app affect accessibility. The “Last Updated” date reflects the most recent revision.

9. Approval

This statement is approved by:

Daniel Jamison, Owner, Jamison Tech LLC