Accessibility Statement

1. Scope of this statement

This statement applies to the public DFF Reach website and the signed-in web application at dffreach.com. External social providers, payment portals and other third-party services have their own accessibility responsibilities and statements.

DFF Reach is a responsive web service used across mobile, tablet and desktop layouts. Accessibility work therefore covers interaction as well as visual presentation.

2. Accessibility target

DFF Reach uses WCAG 2.2 level AA as its working technical target. The service also aims to meet applicable equality, disability and consumer-access requirements in supported markets.

A target is not the same as a completed independent audit. DFF Reach does not currently claim full WCAG 2.2 AA conformance across every released and third-party-dependent journey.

3. Current design approach

The interface is designed around semantic page structure, familiar controls and clear operational states.

• Keyboard-visible focus for interactive controls.
• Accessible names for icon-only actions and form controls.
• Status, warning and error information that does not depend on colour alone.
• Responsive layouts and support for browser zoom and text scaling.
• Reduced-motion handling for non-essential movement.
• Plain, action-oriented error messages that explain the next step.
• Solid, readable surfaces for forms, settings and legal text.
• Normal visible alternatives for important actions rather than swipe-only, drag-only or long-press-only controls.

4. Known and potential limitations

DFF Reach is still being expanded and tested. Some complex provider authorisation windows, embedded payment journeys, maps, charts, uploaded user media or third-party content may not offer the same level of accessibility as native Reach controls.

Some newly released or translated surfaces may contain an incomplete label, focus order, live-region announcement, contrast treatment or alternative text until the issue is identified and corrected. DFF Reach prioritises barriers that prevent account access, security, billing, provider connection, scheduling or publication.

5. Third-party services

DFF Reach connects to independent services such as social providers, authentication services and payment processors. Their consent screens, dashboards and hosted controls are not authored by DFF Reach.

Where a third-party barrier blocks a Reach journey, report it to DFF Reach as well as the provider. DFF Reach will consider a practical alternative or provider escalation where one is available, but cannot directly change an external interface.

6. Report an accessibility problem

Email support@directfoodfinder.com with the subject “DFF Reach accessibility”. Identify the page or feature, what you were trying to do, the assistive technology or browser used where relevant, and the barrier encountered.

Do not include a password, one-time code, full payment credential or raw provider token. DFF Reach will acknowledge the report and prioritise a response according to impact.

7. Alternative formats and assistance

You may request reasonable help accessing legal information or completing a support process in another accessible format. State the document or task and the format or adjustment needed.

An alternative route must not weaken account security, reveal another person's information or bypass a provider's mandatory identity check.

8. Review and testing

Accessibility is reviewed during component, responsive, keyboard and production verification. Automated checks are useful but do not replace manual keyboard, screen-reader and task-based testing.

This statement will be updated when the audit position, significant known limitations or contact process changes.