Accessibility Statement
Last updated: July 21, 2026
Software Development Services, LLC is committed to making TallyTill usable by as many people as possible, including people with disabilities. Because TallyTill is used as a self-service checkout by members of the public, we treat this as a product requirement rather than a compliance exercise.
We would rather tell you exactly where we stand than claim more than we have verified. This page states what we have tested, what we have fixed, and what we have not yet checked.
1. Standard We Measure Against
We measure against WCAG 2.2 Level AA. Where a customer requires a conformance report against WCAG 2.1 Level AA (still the more common procurement request) or EN 301 549, contact us and we will respond with our current status.
2. What We Have Tested and Fixed
As of July 21, 2026, automated WCAG 2.2 AA testing (axe-core) reports no violations on:
- The customer-facing checkout, across its idle, cart, and payment screens
- Our public website — home, features, pricing, and help pages
Fixes made in this round include:
- Screen-reader announcements at checkout. Adding an item to the cart updated the screen visually but announced nothing. Cart additions and the running total are now announced.
- Pinch-zoom restored. The checkout previously disabled zoom. It is now available, including on our Android kiosk app, where it required an additional platform-level change.
- Colour contrast. Body text, the payment screen's total, and our primary call-to-action all failed the 4.5:1 minimum and have been corrected.
- Labels, focus and structure. Unlabelled dropdowns and date fields, a missing focus indicator, and missing page headings were corrected across the checkout and merchant portal.
3. Keyboard Access
The checkout is fully operable by keyboard. Every control, including each product button, is reachable in a logical order with a visible focus indicator, and there are no keyboard traps.
4. Known Gaps
We are aware of the following and are working on them:
- Screen-reader testing has not been completed. Our work so far is based on automated testing and code review. We have not yet completed a manual pass with NVDA, VoiceOver, or TalkBack. Automated tools catch roughly a third of real accessibility problems, so we do not claim conformance on this basis alone.
- Our Android kiosk app has not been separately tested with TalkBack. It shares its interface with the web checkout, so the fixes above apply to it, but it has not been verified on-device.
- Signed-in areas of the merchant portal have had automated testing but less coverage than the public pages and the checkout.
- Item recognition is camera-based and therefore visual by nature. Our voice assistant is the intended path for shoppers who cannot use the camera, and we are continuing to improve it. See section 5.
- Time limits. An inactive cart is cleared after a configurable period without first warning the shopper or offering more time. We intend to add that.
5. Third-Party Components
Card payment entry is handled by Stripe and rendered by Stripe's own software, which we cannot modify. Shoppers who prefer to pay using their own phone can do so by scanning a code, which lets them use the assistive technology already configured on their own device. Where a merchant uses a physical card reader, readers with tactile keys are available and we recommend them for this reason.
6. Feedback
If you encounter a barrier using TallyTill, please tell us — including if you are a shopper who ran into a problem at a merchant's checkout. Reports of specific barriers are the most useful thing we receive, and we prioritise them.
Email: support@tallytill.com
We aim to respond within five business days.
7. Formal Complaints
If you are not satisfied with our response, you may escalate to Software Development Services, LLC at the address listed in our Terms of Service.