Accessibility Statement

Accessibility Statement

Our Commitment to an Accessible Site

councilbincollection.org/ is committed to making the site usable by everyone, including people who use screen readers, keyboard-only navigation, magnification, and other assistive technologies. We target WCAG 2.1 Level AA and apply the principles of the Equality Act 2010.

Effective date: 1 January 2026
Last reviewed: April 2026
Standards: WCAG 2.1 AA · Equality Act 2010

1. Our Commitment

Knowing your bin day shouldn’t depend on what device you use, what assistive technology is on it, or what motor ability you have on a given morning. We treat accessibility as an editorial standard alongside accuracy and currency, not an afterthought.

2. Standards We Apply

We target the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the W3C Web Accessibility Initiative. WCAG 2.1 AA is the recognised international benchmark for digital accessibility and is the standard set out in UK government accessibility guidance for the public sector — we apply it as a private-sector benchmark to the same level.

4. Accessibility Features Built Into the Site

📐

Semantic HTML

Proper heading hierarchy, landmarks, lists and tables with appropriate roles for screen readers

🎨

Colour contrast

Body text and key UI elements meet or exceed WCAG 2.1 AA contrast ratios (4.5:1 for normal text)

Keyboard navigation

All interactive elements are reachable and usable with the keyboard alone

🎯

Visible focus

Clear focus indicators on links, buttons and form controls

🖼

Alt text

Descriptive alt text on meaningful images; decorative images marked as such

🔗

Descriptive links

Link text describes the destination; no “click here” or “read more” without context

🔍

200% zoom

Layouts work at 200% browser zoom and at increased text sizes

No autoplay

No autoplay video or audio; no flashing content above the WCAG threshold

🅰

Resizable text

Text can be resized without loss of content or function

🏷

Form labels

Every form input has an explicit label; errors are programmatically associated

🌐

Declared language

The page language is declared (en-GB) so screen readers use the right pronunciation

🛑

Reduced motion

The site respects the prefers-reduced-motion setting in your operating system

5. Assistive Technology Compatibility

The site is built and tested to work with mainstream assistive technologies, including:

TechnologyStatus
NVDA (Windows screen reader)Tested with current and previous major versions
JAWS (Windows screen reader)Tested with current and previous major versions
VoiceOver (macOS & iOS)Tested with current macOS and iOS
TalkBack (Android)Tested with current Android
Narrator (Windows)Compatible
Browser zoom and OS magnificationUp to 200% with no loss of content
Voice control (Dragon, Voice Control on macOS/iOS)Compatible with semantic landmarks and labelled controls
Keyboard-only operationFull site usable without a mouse or pointing device

6. Supported Browsers

We support the current and one previous major version of:

  • Google Chrome (Windows, macOS, Linux, Android)
  • Mozilla Firefox (Windows, macOS, Linux, Android)
  • Apple Safari (macOS, iOS, iPadOS)
  • Microsoft Edge (Windows, macOS)
  • Samsung Internet (Android)

Older browsers may load the site, but accessibility features depending on modern web standards may not work consistently. If you can, please use a current version.

7. Keyboard Navigation

KeyAction
TabMove forward through interactive elements
Shift + TabMove backward through interactive elements
EnterActivate links and submit buttons
SpaceActivate buttons; scroll the page
Arrow keysMove within form controls and menus
EscClose modal dialogs and pop-ups

If you find a place where keyboard focus gets stuck, where a control isn’t reachable, or where an element activates without a clear focus indicator, please tell us — that’s a bug we want to fix.

8. Known Limitations

Known issues we are working on
  • Older content — pages published before our current accessibility standard was adopted may not yet meet WCAG 2.1 AA in every detail. We work through them in the quarterly review cycle.
  • Embedded Google Maps — when consented and loaded (used to show HWRC and council office locations), Maps inherits Google’s accessibility implementation, which is good but outside our direct control.
  • External PDFs from councils — many councils publish forms as PDF. The accessibility of those PDFs depends on the issuing council. Where a PDF appears not to have a tagged structure, we link to it with that caveat noted.
  • Auto-generated content — for the largest councils we publish across many subpages; if a subpage hasn’t been through the manual accessibility review yet, it may have minor issues we will catch in the next review pass.

If you encounter an accessibility barrier, please report it (Section 12) so we can address it directly and ahead of the next scheduled review.

9. Third-Party Content

The site includes content we don’t directly control:

  • Display advertising — accessibility is determined by the ad creative supplied by the advertiser through the ad network
  • Embedded Google Maps — accessibility per Google’s implementation
  • Outbound links to council websites — accessibility per each council’s own site

We make reasonable efforts to choose vendors and partners that take accessibility seriously, but we cannot guarantee third-party content the way we can for our own pages.

10. Alternative Formats

If you cannot access content on the site for accessibility reasons, please email us with the page URL and a description of the barrier. We will aim to provide the same information in an alternative format — typically plain text or a tagged PDF — within five working days.

11. Testing and Review

Our accessibility approach combines:

  • Automated testing — Axe, WAVE and Lighthouse accessibility audits run on representative pages
  • Manual screen-reader testing — NVDA on Windows and VoiceOver on macOS/iOS, focused on navigation, headings, link purpose and form labels
  • Keyboard-only walkthroughs on every new page template
  • Zoom and magnification testing at 100% / 150% / 200% / 400%
  • Colour-contrast checking against WCAG 2.1 AA thresholds
  • Reduced-motion check with prefers-reduced-motion enabled
  • Quarterly review of representative pages alongside the editorial review

12. Reporting an Accessibility Issue

If something isn’t working for you

Please email info@councilbincollection.org with subject line “Accessibility issue.”

To help us fix the issue quickly, please include:

  • The URL of the page where you encountered the problem
  • A short description of what happened and what you expected
  • The browser, version, operating system and any assistive technology you were using (if you know)

We acknowledge accessibility reports within one to three working days and prioritise fixes ahead of routine editorial work.

13. External Escalation

If you believe we haven’t addressed an accessibility concern adequately, you can also raise it through the following routes:

BodyScopeReference
Equality and Human Rights Commission (EHRC)Equality Act 2010 enforcementequalityhumanrights.com
Citizens AdviceFree, confidential advice on Equality Act rightscitizensadvice.org.uk
Local Government and Social Care OmbudsmanIf your concern is about a council’s own service rather than this sitelgo.org.uk

14. Standards References

Tell Us If Something Isn’t Accessible

Accessibility reports are our priority queue. We acknowledge within one to three working days and fix ahead of routine editorial work.

📧 info@councilbincollection.org

Leave a Comment