Accessibility Statement

1. Our commitment

Mme Waste Ldn is committed to ensuring digital accessibility for people with disabilities — including visual, auditory, physical, speech, cognitive, and neurological disabilities. We design our public-facing marketing website to be as inclusive as reasonably possible, and we treat accessibility failures with the same priority as service-impacting bugs.

This statement applies to the public website at mmewasteldn.co.uk, excluding authenticated back-office admin, driver, and customer-portal areas, which are covered by a separate internal accessibility roadmap. Authenticated users requiring accommodations should contact us directly (see §11) for alternative ways to access their account information.

2. Conformance target and current status

Our formal target is full conformance with the W3C Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This is the baseline accessibility standard required by the UK's Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 and is the widely accepted baseline for commercial websites operating in the UK.

3. Accessibility measures implemented

• Semantic HTML and ARIA landmarks. Pages use proper <header>, <nav>, <main>, <section>, <article>, and <footer> elements so screen readers and voice-control tools can skip to content areas.
• Keyboard-only navigation. All interactive elements (links, buttons, forms, menu items) are reachable and operable with Tab / Shift+Tab / Enter / Space / Arrow keys. Visible focus indicators (≥ 2px outline) are present on every focusable control.
• Colour contrast. Body text meets a minimum 4.5:1 contrast ratio against backgrounds and headings meet a minimum 3:1 ratio (WCAG 1.4.3). No meaning is conveyed by colour alone — status badges always include text labels.
• Responsive and resizable layouts. Content remains usable without horizontal scrolling down to 320px viewport width (iPhone SE). Text scales cleanly up to 400% zoom without overlap or truncation. Text-spacing controls (letter-spacing, line-height, word-spacing) do not break content.
• Image alternatives. All informative images include meaningful alt attributes; purely decorative images use alt=""; complex data visuals (charts, infographics) include on-page text summaries or <figure> captions.
• Form accessibility. Every form field has a visible, programmatically-associated <label>. Required fields are marked with both an asterisk and the required / aria-required attributes. Inline error messages use aria-describedby so they are announced by screen readers.
• Headings and reading order. Headings follow a single logical H1 → H2 → H3 hierarchy per page, with exactly one <h1>. Content and DOM reading order match visual reading order.
• Animations and motion. Parallax effects, auto-playing carousels, and transitions respect the user's prefers-reduced-motion: reduce system setting and are disabled or simplified when requested. Time-outs (e.g. session expiry) can be extended or disabled by user action.
• Link purpose. All links contain descriptive text — no generic "click here" / "read more". Icons-only buttons (e.g. mobile menu toggle, search, social icons) include aria-label attributes.
• Language and structure. Every page declares <html lang="en-GB">; content in other languages, if any, is wrapped with a lang attribute. Pages use descriptive, unique <title> elements.

4. Assistive technologies tested against

We test our pages against the following assistive tech stack in our internal QA cycles:

• Screen readers: NVDA + Firefox (Windows), VoiceOver + Safari (macOS / iOS), TalkBack + Chrome (Android)
• Zoom: macOS native zoom (5× — 8×), Windows Magnifier, Chrome 125% / 150% / 200% text-only zoom
• Keyboard navigation: pure Tab / Shift+Tab traversal with no mouse, Dragon NaturallySpeaking 16 voice control
• Automated scanners: axe-core 4.10 (browser extension + CI), Lighthouse accessibility audit, IBM Equal Access Toolkit

5. Accessibility in our procurement and build process

Accessibility is considered at every stage of our content and engineering pipeline:

• Design reviews include an explicit WCAG 2.2 AA checklist pass before hand-off to engineering.
• Pull requests that introduce new UI trigger an axe-core scan in CI; AA violations block the merge.
• Third-party scripts and embeds (maps, calendars, video players, chat widgets) are reviewed for accessibility before integration. Incompatible vendors are wrapped with accessible fallbacks or replaced.
• New content authors are trained on writing accessible alt text, link text, and heading structure as part of onboarding.

6. Content types we support

• PDFs and downloadable documents: customer-facing documents (quotes, invoices, terms) are exported with tagged PDF structure, reading order, and document title metadata. Scanned documents are OCR'd with output text verified.
• Video and audio: embedded marketing videos include burned-in English subtitles with 4.5:1 contrast. Post-launch we plan to add human-corrected transcripts and audio descriptions for any video with moving-image narrative.
• Maps and interactive widgets: embedded maps provide a text-based list alternative (postcodes served + phone number to book by phone) so users who cannot interact with visual maps still receive equivalent information.

7. Third-party content we do not control

Our Site may embed or link to content from the following third-party providers that falls outside of this statement and over which we have limited control: Google Maps embeds, Instagram/Facebook review widgets, Vimeo-hosted video embeds, and any ad-hoc document links provided by customers via booking attachments. Where these providers have their own accessibility statements we link to them from our provider pages, and where they do not we offer users an equivalent information alternative (text summary, phone booking, email) for the affected service.

8. Evaluation methodology

We evaluate our conformance using a combination of:

• Self-evaluation by the in-house engineering team (monthly axe/Lighthouse scans).
• Manual accessibility audits performed by senior engineers and content editors against WCAG 2.2 Level AA Success Criteria (quarterly).
• Feedback from external users with disabilities and disability advocacy groups (ongoing, via §11 contact).

9. Known limitations and planned remediation

10. How to request an accessible alternative

If any format on this Site prevents you from accessing the information or service you need (including booking a collection, downloading a receipt, or reading a policy document), contact us via the channels below and we will respond with a fully accessible alternative (plain-text email, telephone, document in a different format, or assisted booking) within 2 working days, free of charge.

11. Feedback and reporting accessibility barriers

We welcome feedback from users on any aspect of our accessibility work. To report an accessibility barrier, request an accommodation, or ask a question about this statement, please use any of the channels below. We aim to acknowledge all messages within 1 working day and resolve or propose a workaround within 5 working days.

In your message it helps to include: the URL or page name where you experienced the issue; a brief description of the problem; the assistive technology, browser, and operating system you were using (if known); and your preferred format for a response (telephone, plain-text email, Word, large-print PDF, etc.).

12. Escalation procedure

If you are not satisfied with our response to an accessibility concern, you may escalate the matter by replying to our response and asking for the case to be reviewed by the Head of Operations. The Head of Operations will respond personally within a further 5 working days. If the issue is still not resolved to your satisfaction, you may refer the matter to your local Citizens Advice Bureau or to the Equality Advisory and Support Service (EASS) at www.equalityadvisoryservice.com / telephone 0808 800 0082, who can provide free, confidential advice on discrimination and equality matters in England, Scotland, and Wales.

13. Approved by

This Accessibility Statement was reviewed and approved for publication by the Mme Waste Ldn Management Board on 2026-08-29. It is reviewed at least annually, or after any major site redesign, whichever comes sooner. Material updates are re-notified on this page and via the contact channels above.