Accessibility statement
Accessibility statement for Pocketa
This page describes the accessibility standard we aim for, the current status of the website and product workspace, known limitations, and how to report a barrier.
Intended standard
We aim to make Pocketa easy to read, navigate and understand, working toward the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA where practical. This statement does not claim WCAG conformance or a formal audit certificate.
Statement last reviewed: 20 July 2026. The review included automated public-page checks and a review of the claims on this page.
Current status
These points describe practices on the public site and product chrome today.
Skip link and page landmarks
A “Skip to main content” link is available from the start of every page for keyboard users. Marketing, sign-in, and signed-in shells mark a main content target so that link has somewhere useful to land.
Readable colour contrast
Helper text and brass labels on light backgrounds use darker brand tokens so text stays easier to read. We still use colour for emphasis, but critical sign-in and form errors also use text and alert roles rather than colour alone.
Responsive layouts and zoom
Pages are built to reflow across common phone, tablet and desktop widths. We expect 200% browser zoom and narrow viewports to remain readable on core public and auth journeys.
Clear page structure
Headings and sections follow a predictable order so you can scan from hero content through supporting blocks to footer links. Auth fields use visible labels linked to their inputs.
Keyboard friendly links and buttons
Links and buttons use visible focus styles so keyboard users can see where they are on supported journeys.
Plain language where possible
We favour straightforward sentences alongside renovation terms, and we signpost product limits so expectations stay realistic.
Known limitations
Automated scans and spot keyboard checks do not replace fuller journey testing. These topics stay on the review list as the product grows.
Signed-in dense screens
Project checklists, filters, and admin tables still need ongoing keyboard, focus, and assistive-technology checks as they change.
Complex forms
Supplier application and multi-step commercial flows need continued label, error, and mobile review. Automated scans do not replace journey checks.
Uploads and rich controls
File upload and drag/reorder patterns need clear instructions, keyboard paths, and progress states wherever they appear.
Modal dialogs
Pocketa does not yet use a shared modal dialog system with focus trapping. Overlays such as cookie consent are regions, not dialogs. We will treat full modal patterns carefully when introduced.
How to report an accessibility issue
If you notice an accessibility barrier, contact Pocketa through the contact page. Describe the page, what you were trying to do and, if you can, the browser or assistive technology you use. That detail helps us reproduce issues and plan fixes.
Continuous checks
We use automated checks on public pages during development, and we treat accessibility as part of ordinary product work. These checks can identify some barriers, but they do not replace feedback from people using different browsers, devices, keyboards or assistive technologies.
Last review date: 20 July 2026.