Accessibility statement

Version 2.0 · Last updated: 2026-06-05

OutletPicks is committed to making the Service usable by the widest possible audience, regardless of ability or assistive technology. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the EU European Accessibility Act (Directive 2019/882, applicable from 28 June 2025), the harmonised EU standard EN 301 549 v3, the Americans with Disabilities Act Title III, the U.S. Section 508 standards, the Accessibility for Ontarians with Disabilities Act (AODA), §504 of the U.S. Rehabilitation Act of 1973, and the UK Equality Act 2010.

Table of contents

1. Conformance status
2. Measures we have taken
3. Assistive technology compatibility
4. WCAG 2.2 self-audit, criterion-by-criterion
5. Known limitations
6. Cognitive accessibility commitments
7. Testing methodology
8. ATAG and authoring tools
9. Feedback and complaints
10. Enforcement procedure

1. Conformance status

We self-assess as partially conformantwith WCAG 2.2 Level AA. “Partially conformant” means that some parts of the content do not yet fully conform — see Section 5 for the open list of known limitations and remediation timeline.

2. Measures we have taken

• Semantic HTML structure (one h1 per page, landmarks, lists, tables with th/scope).
• Keyboard navigation across the full UI with a visible focus ring (no positive tabindex; focus never trapped outside dialogs).
• Skip-to-content link as the first focusable element on every page.
• Colour palette tested for WCAG AA on body text and AAA on most editorial copy; UI components ≥3:1.
• Form controls have explicit label elements; errors are announced via role=“status” or aria-live.
• Images carry meaningful alt text or aria-hidden=“true” when decorative.
• Animation respects prefers-reduced-motion; animated counters fall back to static numbers.
• Touch targets are at least 44 × 44 CSS pixels on mobile; ≥24 × 24 elsewhere.
• Dialog and modal patterns use ARIA roles and trap focus correctly; close on Escape.
• Language is declared at the document level and inline for foreign-language quotations.
• Custom widgets (rating, vote, comparison) expose name, role, and value via WAI-ARIA.
• Editorial copy targets a Flesch-Kincaid reading age of 14–16 for guides, lower for instructions.
• No content flashes more than three times per second.
• Live regions for status updates (e.g. “Deal copied to clipboard”) use role=“status”.
• WCAG 2.2 new criteria: focus not obscured, target size minimum, dragging-movement alternative, accessible authentication minimum, redundant-entry avoidance, consistent help all implemented.

3. Assistive technology compatibility

We test with the following assistive technology / browser combinations as part of every major release:

4. WCAG 2.2 self-audit, criterion-by-criterion

5. Known limitations

• Some user-submitted images may lack alt text. We are progressively flagging and rewriting them. Target resolution: ongoing, with new submissions blocked from publishing without alt text by end of Q3.
• The deal-comparison table on small screens uses horizontal scroll; an alternative card view is available via the density toggle.
• A small number of legacy SVG illustrations do not yet expose accessible names; planned for the next release.
• Audio and video content: none currently. Any future audio/video will be published with captions, transcripts, and audio description as relevant.
• Mathematical content in articles uses Unicode where possible; complex equations are described in surrounding text rather than rendered as images.

6. Cognitive accessibility commitments

• Plain-language summaries at the top of every guide.
• Consistent navigation; same icons mean the same thing across the site.
• No surprise pop-ups; the consent banner is the only one and is dismissible.
• Generous time on any action; no countdown timers.
• Forms break long inputs into chunks with helper text.
• Tables include a one-line summary above; complex tables include both column and row headers.
• Errors include suggested fixes, not just “invalid”.

7. Testing methodology

Conformance is assessed by a combination of:

• Automated tooling — axe-core, Lighthouse and Pa11y run in CI on deploy, and new axe violations are triaged before release.
• Manual keyboard testing — releases are tested with only the keyboard.
• Manual screen-reader testing — VoiceOver and/or NVDA on representative pages.
• Visual checks at 200%, 400%, 90% column width zoom; light + dark + forced-colour mode.
• Third-party audit against WCAG 2.2 AA + EN 301 549 when resourcing permits.

Last full manual audit: 2026-06-05.

8. ATAG and authoring tools

The deal-submission and comment authoring tools follow the W3C Authoring Tool Accessibility Guidelines (ATAG 2.0) Level A where applicable: accessible authoring UI, accessible-by-default outputs (alt-text requirement on image upload), and accessible previews.

9. Feedback and complaints

If you encounter an accessibility barrier, please tell us. We aim to respond within 5 working days.

• Email: [email protected]
• Include: the URL, what you tried to do, what happened, your assistive technology + browser version + operating system.
• We will tell you whether the issue is reproducible, what we plan to do, and the expected timeline.

10. Enforcement procedure

EU users who are not satisfied with our response may contact the national enforcement authority designated under Article 14 of the European Accessibility Act in their member state. In Monaco: Direction des Plateformes et des Ressources Numériques for digital-accessibility matters. In Portugal: Autoridade Nacional de Comunicações (ANACOM), Avenida José Malhoa 12, 1099-017 Lisboa. In Germany: Bundesfachstelle Barrierefreiheit. In France: Autorité de Régulation de la Communication Audiovisuelle et Numérique (ARCOM). Equivalent national authorities in IT, ES, NL, BE, AT.

UK users may contact the Equality and Human Rights Commission (EHRC) or, in Northern Ireland, the Equality Commission. U.S. users may file a complaint with the Department of Justice under ADA Title III procedures. Canadian users may contact the Canadian Human Rights Commission or the equivalent provincial body.

Related policies

See our privacy policy, terms, and imprint.