Cash Reader

Back to Accessibility & Compliance

Cash Reader Accessibility Conformance Report (ACR)

Based on VPAT® Version 2.5, WCAG 2.2 Edition

This Accessibility Conformance Report is a self-disclosure of the accessibility of Cash Reader, prepared using the ITI Voluntary Product Accessibility Template® (VPAT®) Version 2.5, WCAG edition.

Product and Report Information

Field Detail
Name of Product/Version Cash Reader for iOS and Android, version 1.77
Report Date June 11, 2026
Product Description Cash Reader is a mobile application that identifies banknotes for people who are blind or have low vision. The user points the device camera at a banknote and the app immediately announces its denomination. It recognizes banknotes from 114 currencies, works fully offline after a one-time currency download, and reads folded, worn, or partially visible notes from any angle, activating the flashlight automatically in low light. Results are delivered through speech (primary output), distinct countable vibration patterns, and a large, high-contrast on-screen display. Cash Reader is optimized for Apple VoiceOver and Google TalkBack and is used by more than one million blind and low-vision users worldwide.
Contact Information Tomas Jelinek, CEO, Cash Reader s.r.o. ([email protected])
Notes The target conformance level for this report is WCAG 2.2 Level AA (Level A and Level AA criteria are evaluated). Level AAA is included for completeness but was outside the scope of this evaluation. Cash Reader is a native mobile application; the WCAG success criteria, which are written for web content, are interpreted for non-web software in line with the W3C WCAG2ICT guidance. The application is localized into 39 languages, including right-to-left languages (Arabic, Hebrew). The application runs in portrait orientation only (see SC 1.3.4).
Evaluation Methods Used This report is based on: (1) internal accessibility testing by the development team using Apple VoiceOver and the iOS Accessibility Inspector on iOS, and Google TalkBack and Accessibility Scanner on Android, across all application screens; (2) functional accessibility testing and expert review by TyfloCentrum o.p.s., a Czech non-profit organization serving people who are blind or visually impaired, performed by screen-reader users, which identified no accessibility barriers; and (3) continuous real-world validation: Cash Reader’s entire user base consists of blind and low-vision people who operate the app exclusively through screen readers and other assistive technologies.

Applicable Standards / Guidelines

Standard / Guideline Included in Report
Web Content Accessibility Guidelines 2.2, Level A Yes
Web Content Accessibility Guidelines 2.2, Level AA Yes
Web Content Accessibility Guidelines 2.2, Level AAA Included (Not Evaluated, outside target level)

Terms

The terms used to describe each criterion’s conformance level are defined as follows:

WCAG 2.2 Report

Conformance target: Level AA (Level AA conformance includes all Level A criteria).

Table 1: Success Criteria, Level A

Criteria Conformance Level Remarks and Explanations
1.1.1 Non-text Content Supports All interactive controls (icons, buttons) expose text alternatives to VoiceOver/TalkBack. The result of the camera recognition is conveyed to the user as speech and as on-screen text.
1.2.1 Audio-only and Video-only (Prerecorded) Not Applicable The app contains no prerecorded audio-only or video-only media.
1.2.2 Captions (Prerecorded) Not Applicable The app contains no prerecorded synchronized media.
1.2.3 Audio Description or Media Alternative (Prerecorded) Not Applicable The app contains no prerecorded synchronized media.
1.3.1 Info and Relationships Supports Structure, grouping, and control roles are programmatically exposed through the native platform accessibility APIs.
1.3.2 Meaningful Sequence Supports Focus and reading order are logical and match the visual order, including in right-to-left locales.
1.3.3 Sensory Characteristics Supports Instructions do not rely solely on shape, size, location, or sound; all controls have text labels. The app is designed for non-visual operation.
1.4.1 Use of Color Supports Color is never the only means of conveying information; all information is available through speech, text, and/or vibration.
1.4.2 Audio Control Supports Speech output is user-initiated and can be stopped at any time; there is no automatically playing audio. Volume follows the device controls.
2.1.1 Keyboard Supports The app uses standard native controls and is fully operable via assistive technologies (VoiceOver/TalkBack gestures, Switch Control, and external/hardware keyboards).
2.1.2 No Keyboard Trap Supports Focus can be moved to and away from every component; no focus traps exist.
2.1.4 Character Key Shortcuts Supports The app does not implement single-character key shortcuts, so none can be triggered accidentally.
2.2.1 Timing Adjustable Supports The app imposes no time limits on user interaction.
2.2.2 Pause, Stop, Hide Supports The app has no moving, blinking, scrolling, or auto-updating content other than the live camera preview, which is essential to the core function.
2.3.1 Three Flashes or Below Threshold Supports The app contains no flashing content.
2.4.1 Bypass Blocks Not Applicable The concept of bypassing repeated blocks of content does not apply; the app’s screens are single-purpose and contain no repeated navigation blocks.
2.4.2 Page Titled Supports Each screen has a descriptive title/accessible name that is announced by the screen reader.
2.4.3 Focus Order Supports Focus order is logical and preserves meaning and operability.
2.4.4 Link Purpose (In Context) Supports Links and buttons (e.g., to settings, help, privacy policy) have descriptive accessible names.
2.5.1 Pointer Gestures Supports All functionality is operable with single-pointer taps and standard screen-reader gestures; no multipoint or path-based gestures are required.
2.5.2 Pointer Cancellation Supports Activation occurs on the up-event; users can move away from a control to abort an action.
2.5.3 Label in Name Supports The accessible name of each control contains its visible label text.
2.5.4 Motion Actuation Supports No functionality is operated by device motion; vibration is used only as output, never as input.
3.1.1 Language of Page Supports The application language is set programmatically and follows the device locale. The app is localized into 39 languages.
3.2.1 On Focus Supports Moving focus to a component does not trigger an unexpected change of context.
3.2.2 On Input Supports Changing a setting or control does not cause an unexpected change of context.
3.2.6 Consistent Help Supports Help and contact options are available in a consistent location within the app’s settings.
3.3.1 Error Identification Supports Where input is accepted (e.g., redeeming a code), errors are described in text and announced by the screen reader.
3.3.2 Labels or Instructions Supports All interactive controls have labels and, where needed, instructions exposed to assistive technology.
3.3.7 Redundant Entry Not Applicable The app contains no multi-step process that requires users to re-enter previously provided information.
4.1.1 Parsing Supports This criterion was removed in WCAG 2.2 and is always considered satisfied. The app additionally uses standard native UI components with valid accessibility trees.
4.1.2 Name, Role, Value Supports All UI components expose name, role, state, and value through the native accessibility APIs, the foundation of the app’s screen-reader support.

Table 2: Success Criteria, Level AA

Criteria Conformance Level Remarks and Explanations
1.2.4 Captions (Live) Not Applicable The app contains no live synchronized media.
1.2.5 Audio Description (Prerecorded) Not Applicable The app contains no prerecorded video.
1.3.4 Orientation Partially Supports The app is presented in portrait orientation only. The fixed orientation provides a consistent, predictable layout for screen-reader users and stable camera framing for banknote capture. Because the view is nonetheless restricted to a single orientation, this is conservatively reported as Partially Supports.
1.3.5 Identify Input Purpose Not Applicable The app does not collect personal user information through input fields.
1.4.3 Contrast (Minimum) Supports The interface uses a large, high-contrast text display designed for low-vision users; text and essential controls meet or exceed the required contrast ratios (4.5:1, or 3:1 for large text).
1.4.4 Resize Text Supports The app honors the operating-system text-size settings and offers a large-text display; content remains available and functional when enlarged.
1.4.5 Images of Text Supports The app uses real text rather than images of text.
1.4.10 Reflow Supports Content adapts to the device viewport and to enlarged text without loss of information or two-dimensional scrolling.
1.4.11 Non-text Contrast Supports Interactive controls and meaningful graphics meet the 3:1 contrast ratio against adjacent colors.
1.4.12 Text Spacing Supports Content adapts to increased text spacing without loss of content or function.
1.4.13 Content on Hover or Focus Not Applicable The app is a touch application with no hover interaction, and it does not present additional content on focus that must be dismissed.
2.4.5 Multiple Ways Not Applicable The app is a single-function tool; the concept of providing multiple ways to locate one of a set of pages does not apply.
2.4.6 Headings and Labels Supports Headings and labels describe their topic or purpose.
2.4.7 Focus Visible Supports A visible focus indicator is shown for keyboard, Switch Control, and screen-reader focus.
2.4.11 Focus Not Obscured (Minimum) Supports A component that receives focus is not entirely hidden by other content.
2.5.7 Dragging Movements Supports The app does not rely on dragging; any adjustable control offers a single-tap or stepper alternative operable via assistive technology.
2.5.8 Target Size (Minimum) Supports Touch targets meet or exceed the 24×24 CSS-pixel minimum; the interface intentionally uses large targets for low-vision and motor accessibility.
3.1.2 Language of Parts Supports The app presents content in the user’s selected language; where languages are mixed, the language is set programmatically.
3.2.3 Consistent Navigation Supports Navigation and controls appear in a consistent order across screens.
3.2.4 Consistent Identification Supports Components with the same functionality are identified consistently throughout the app.
3.3.3 Error Suggestion Supports When an input error is detected (e.g., an invalid code), the app describes the problem and how to correct it, announced via the screen reader.
3.3.4 Error Prevention (Legal, Financial, Data) Supports Subscriptions and purchases are processed by the Apple App Store and Google Play, which provide their own confirmation, receipt, and cancellation mechanisms; the app itself does not process or store payment data.
3.3.8 Accessible Authentication (Minimum) Not Applicable The app does not require user accounts, sign-in, or any authentication.
4.1.3 Status Messages Supports Status messages (including the recognized denomination, “no banknote detected,” and loading/processing states) are announced to assistive technologies without moving focus. This is the central interaction of the app.

Table 3: Success Criteria, Level AAA

Level AAA is outside the target conformance level for this report (the target is Level AA). The following criteria were not evaluated. WCAG does not require Level AAA conformance for general policy.

Criteria Conformance Level Remarks and Explanations
1.2.6 Sign Language (Prerecorded) Not Evaluated Outside target level. (No prerecorded synchronized media is present.)
1.2.7 Extended Audio Description (Prerecorded) Not Evaluated Outside target level.
1.2.8 Media Alternative (Prerecorded) Not Evaluated Outside target level.
1.2.9 Audio-only (Live) Not Evaluated Outside target level.
1.3.6 Identify Purpose Not Evaluated Outside target level.
1.4.6 Contrast (Enhanced) Not Evaluated Outside target level.
1.4.7 Low or No Background Audio Not Evaluated Outside target level.
1.4.8 Visual Presentation Not Evaluated Outside target level.
1.4.9 Images of Text (No Exception) Not Evaluated Outside target level.
2.1.3 Keyboard (No Exception) Not Evaluated Outside target level.
2.2.3 No Timing Not Evaluated Outside target level.
2.2.4 Interruptions Not Evaluated Outside target level.
2.2.5 Re-authenticating Not Evaluated Outside target level.
2.2.6 Timeouts Not Evaluated Outside target level.
2.3.2 Three Flashes Not Evaluated Outside target level.
2.3.3 Animation from Interactions Not Evaluated Outside target level.
2.4.8 Location Not Evaluated Outside target level.
2.4.9 Link Purpose (Link Only) Not Evaluated Outside target level.
2.4.10 Section Headings Not Evaluated Outside target level.
2.4.12 Focus Not Obscured (Enhanced) Not Evaluated Outside target level.
2.4.13 Focus Appearance Not Evaluated Outside target level.
2.5.5 Target Size (Enhanced) Not Evaluated Outside target level.
2.5.6 Concurrent Input Mechanisms Not Evaluated Outside target level.
3.1.3 Unusual Words Not Evaluated Outside target level.
3.1.4 Abbreviations Not Evaluated Outside target level.
3.1.5 Reading Level Not Evaluated Outside target level.
3.1.6 Pronunciation Not Evaluated Outside target level.
3.2.5 Change on Request Not Evaluated Outside target level.
3.3.5 Help Not Evaluated Outside target level.
3.3.6 Error Prevention (All) Not Evaluated Outside target level.
3.3.9 Accessible Authentication (Enhanced) Not Evaluated Outside target level.

Summary

Cash Reader’s conformance target is WCAG 2.2 Level AA. Of the 56 Level A and Level AA success criteria, the product Supports all applicable criteria except 1.3.4 Orientation (the app is portrait-only), which is reported as Partially Supports. Because one criterion at the target level is only partially supported, this report does not claim full WCAG 2.2 Level AA conformance. Criteria reported as Not Applicable relate to capabilities the product does not include (prerecorded/live media, user authentication, personal-data input fields, and web-style multi-page navigation).

Accessibility is the core purpose of Cash Reader: the product is built for and used exclusively by people who are blind or have low vision, and is optimized for Apple VoiceOver and Google TalkBack.

This report is provided by Cash Reader s.r.o. for informational purposes and represents a good-faith self-assessment of the product’s accessibility as of the report date. Accessibility is evaluated on an ongoing basis and this document may be updated as the product evolves. Questions about this report may be directed to [email protected].