Accessibility

The Web Content Accessibility Guidelines 2.2, level AA, across the customer site: the home page and results, the disposal pages for each item, the quote check, the sign-in page, the explainer pages and these legal pages. Nobody has audited the site and issued a conformance claim, so we do not make one. What we can say is what is checked, how, and what we found.

• Every public page runs through an automated WCAG check (the axe engine, with the WCAG 2.0, 2.1 and 2.2 A and AA rule sets) in a phone-sized browser. Those checks run in continuous integration on every change and again in the release checklist before a deploy. A failing rule fails the run.
• The same run checks that no page scrolls sideways on a phone, that no visible text is smaller than 12 pixels, and that the answer on a results page sits near the top rather than under a marketing banner.
• A separate test measures rendered controls: the buttons a customer taps to get somewhere must be at least 44 pixels tall, and every other target must clear the 24 pixel minimum in WCAG 2.2, with links inside a sentence exempt as the guideline allows.

• Keyboard. The first thing on every page is a skip link that becomes visible when focused and jumps to the main content. Every focusable element shows a 3 pixel focus ring with an offset, on light and dark backgrounds alike.
• Motion. If your system asks for reduced motion, smooth scrolling is switched off and animations and transitions are cut to nothing.
• Colour and contrast. Our brand green measures 2.66:1 against white, so it is used only for fills, icons and borders. Wherever white text sits on green a darker green is used, and a darker green again is used for green text on the soft background. Nothing is signalled by colour alone: an amber or green result card also says in words what it means.
• Forms. Every input has a visible label tied to it. A postal code error is announced as an alert and linked to the field it belongs to. Results and quote verdicts appear inside regions that announce themselves to screen readers.
• Structure. Pages declare their language, have one main heading, use landmark regions for the header, navigation, main content and footer, and label every section by its heading. Expandable questions use native disclosure elements so they work without scripts.
• Text. Layouts use fluid widths and minimum heights rather than fixed ones, so text can grow when you zoom without being clipped, and no visible text is smaller than 12 pixels.

• Automated checks catch only part of what matters. We have not yet completed a full manual audit with a screen reader or switch access, so there will be problems the tools do not see.
• The company portal, where haulers manage their listing, is covered by the phone layout audit but is not in the automated WCAG page list, so it has had less accessibility testing than the customer site.
• Photos that customers attach to a quote request have no alternative text, because only the customer knows what is in them and we do not ask for a description.
• The site has a light colour scheme only. A system preference for dark mode is not followed.

Email access@helpmedump.com and tell us what you were trying to do, the page you were on, and the browser or assistive technology you use. We will fix it and tell you when it is done. If you need information from this site in another format in the meantime, ask and we will send it to you.

You do not need an account for any of this. Finding out what your council or city will take, comparing prices and checking a quote all work without signing in, and the how it works page describes each step in plain text.