Accessibility statement

Our commitment

Pricy is built to be usable by everyone, including people who browse with a keyboard only, with a screen reader, at high zoom, or with a display setting that changes how colour and motion appear. Accessibility is treated as part of the product, not an add-on: the same checks that run our tests also fail the build when an accessibility rule regresses.

Conformance level

This website aims to conform to WCAG 2.1 Level AA. That standard covers both of the frameworks that apply to us: the level US courts use in ADA Title III settlements, and Israeli standard IS 5568, which adopts WCAG for websites offering a service to the public.

Conformance is self-assessed. We have not commissioned a third-party accessibility audit, and we say so plainly rather than implying certification we do not hold.

What has been done

• Every page is checked with the axe accessibility engine against the WCAG 2.0 and 2.1 A and AA rule sets, and ships only when that check reports no violations.
• Text colours were re-tuned so body, meta and caption text meet the 4.5:1 contrast minimum for small text on every background they appear on.
• A “Skip to main content” link is the first item reachable by keyboard on every page.
• Pages use real landmark regions (header, navigation, main, footer) and a single, correctly ordered heading structure.
• Every control is reachable and operable with the keyboard alone, and the focused element is always visibly outlined.
• Images carry text alternatives that describe the image actually shown; decorative graphics are hidden from assistive technology instead of being announced.
• Animation respects the operating system’s “reduce motion” setting, which removes non-essential movement.
• The page language is declared, and layouts reflow without horizontal scrolling down to a 320 pixel viewport.

Tested with

Current Chrome, Edge, Firefox and Safari on desktop, and Chrome and Safari on mobile, together with automated testing using axe-core. Keyboard-only navigation is verified on every page. We have not yet completed structured testing with every screen reader; see the limitations below.

Known limitations

We would rather list these than pretend they do not exist.

• We have not yet completed a full manual pass with JAWS, NVDA and VoiceOver. Automated testing catches roughly a third of accessibility problems, so this is a real gap and it is our next piece of work.
• Blog articles are published continuously. Each is generated with descriptive image alternatives and correct heading order and is covered by the automated check, but an individual article may still contain a wording or structure issue we have not caught.
• Some third-party content we do not control, such as external links to retailer sites, may not meet the same standard once you leave our site.

Accessibility arrangements in the Pricy extension

The browser extension itself is keyboard operable: its deal card can be reached, read and dismissed without a mouse, it never traps focus, and it never auto-plays sound or blocks the page it appears on. If it finds nothing to tell you, it shows nothing at all, so it does not add noise for screen reader users.

Reporting a problem, and how to reach a person

If any part of this site or the extension is difficult to use, please tell us. We treat accessibility reports as bugs with priority, not as feedback to file away.

• Accessibility coordinator: Oren Kuperman
• Email: support@pricyapp.ai
• What to include: the page address, what you were trying to do, and the browser or assistive technology you were using. That is usually enough for us to reproduce it.
• Response: we aim to reply within a few business days, and to fix confirmed accessibility problems as a priority.

Formal details

This statement applies to pricyapp.ai and the Pricy browser extension. It was prepared in July 2026 on the basis of our own review and automated testing, and is updated whenever the site changes materially or a problem is reported and fixed.