Accessibility Statement

This statement applies to content published on the whatsonhebdenbridge.com domain. It does not apply to content on third party sites, or to the widget, kiosk and screens versions of this service where they are embedded in someone else's website.

This website is run by Hebden Royd Town Council, Hebden Bridge Community Association and Mike Stephens. It is designed to be used by as many people as possible. The text should be clear and simple to understand. You should be able to:

  • zoom in up to 300% without the text spilling off the screen
  • use the site on a narrow screen, down to 320 pixels wide, without scrolling sideways
  • navigate most of the website using just a keyboard, and see clearly which item you are on
  • skip straight past the header and navigation to the main content of every page
  • read the text at a contrast level that meets the AA standard throughout

We have not yet tested this website with screen reading software or with speech recognition software, so we cannot tell you how well it works with them. We test the underlying markup those tools depend on — headings, labels, landmarks and the names and roles of controls — but that is not the same thing, and testing with the software itself is the next stage of our work.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible this website is

Parts of this website are not fully accessible. We know about the following problems:

  • if you increase the spacing between lines, letters and words, text is cut off in some card and listing layouts
  • some buttons and links are smaller than the minimum recommended size, which makes them harder to tap accurately — this is worst on the "My events" page
  • the sign in, register and password reset forms do not tell your browser what each field is for, so it cannot fill them in for you
  • on three screens — the custom date range on the events listing, the events listing when it finds no results, and the "Add a festival" form — keyboard focus can become stuck and you may need to reload the page to get out
  • a small number of form fields have no visible label or instructions
  • the outline showing which item you are on is not distinct enough on three screens in the account area
  • the filter panel does not tell assistive technology whether it is open or closed
  • one event page has headings that skip a level
  • some PDF documents may not be fully accessible to screen reading software
  • some embedded audio or video content from third parties may not have transcripts, captions or audio descriptions
  • images added by event organisers may not always have a suitable description

Feedback and contact information

If you find any problems not listed on this page, or think we're not meeting accessibility requirements, our contact information is available on our contact us page. Please tell us the page you were on and what went wrong.

If you need information on this website in a different format — accessible PDF, large print, easy read, audio recording or braille — our contact information is available on our contact us page. We'll consider your request and get back to you within 10 working days.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you're not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Technical information about this website's accessibility

Hebden Royd Town Council, Hebden Bridge Community Association and Mike Stephens are committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, because of the non-compliances listed below.

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

  • Text is clipped or overlapped in several card and listing layouts when line height, letter spacing and word spacing are increased. This fails WCAG 2.2 success criterion 1.4.12 (Text Spacing).
  • Some interactive controls are smaller than 24 by 24 pixels and are not spaced far enough apart to compensate. This fails WCAG 2.2 success criterion 2.5.8 (Target Size (Minimum)).
  • Fields on the sign in, register and password reset forms do not identify their purpose to the browser, so browser autofill does not work. This fails WCAG 2.2 success criterion 1.3.5 (Identify Input Purpose).
  • Keyboard focus can become trapped on three screens, with no way out other than reloading the page. This fails WCAG 2.2 success criterion 2.1.2 (No Keyboard Trap).
  • A small number of form fields have no associated label or instructions. This fails WCAG 2.2 success criterion 3.3.2 (Labels or Instructions).
  • The focus indicator does not have sufficient contrast against its background on three screens in the account area. This fails WCAG 2.2 success criterion 1.4.11 (Non-text Contrast).
  • Headings skip a level on one event page, which makes the structure harder to follow with assistive technology. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
  • The filter panel does not expose whether it is expanded or collapsed. This fails WCAG 2.2 success criterion 4.1.2 (Name, Role, Value).
  • Images added by event organisers do not always have a suitable description. This fails WCAG 2.2 success criterion 1.1.1 (Non-text Content).
  • Some documents are in less accessible formats, for example PDF. Non-HTML documents published on or after 23 September 2018 must have an accessible format.

We intend to fix the issues above, other than those in organiser-submitted content and third-party documents, by 31 March 2027. Organiser-submitted content is addressed in the section on what we're doing to improve accessibility.

PDFs and non-HTML documents

Some documents are not accessible in a number of ways, including missing text alternatives and missing document structure. Many are uploaded by event organisers and festivals rather than by us. Where a document is essential to using a service, we will provide the information in an accessible format on request.

Disproportionate burden

We are not currently claiming that any fix would be a disproportionate burden.

Content that's not within the scope of the accessibility regulations

Links to other websites

For the benefit of our users we link to other websites, including:

  • social media platforms
  • event organisers' and venues' own websites and ticketing pages
  • other sources of information

We are not responsible for the accessibility of these or any other websites we do not manage.

Using third party content or functionality on our website

We feature third party content or functionality on our website, including:

  • maps
  • insight tools which tell us how people are using the website
  • applications for creating forms and storing data

Where we choose to feature third party content or functionality on our website, we are responsible for ensuring it meets accessibility standards.

Where we are legally required to feature third party content or functionality, we cannot reasonably accept responsibility for ensuring it meets accessibility standards. However, where it is within our control, we will make every reasonable effort to work towards meeting accessibility requirements.

How we tested this website

This website was last tested on 20 September 2026. The test was carried out by us, in house.

We test against the Web Content Accessibility Guidelines version 2.2, levels A and AA. We used the Website Accessibility Conformance Evaluation Methodology (WCAG-EM) approach to decide which pages to test, and we tested 36 pages and states, chosen to cover every distinct template and every step of a multi-step form, including:

  • the homepage
  • the events listing, and its filtered, empty, paginated, map and custom date range states
  • event, festival, venue, area and category pages
  • content pages, the help page and the "report an event" form
  • sign in, register, password reset and expired reset link
  • the account dashboard, profile, change password, and the my events, my venues and my festivals lists
  • all six steps of the add an event form, and the add a venue and add a festival forms

Testing is automated and runs against every one of those pages on each change. It covers the checks that can be made reliably without a person: contrast, reflow at 320 pixels, zoom to 300%, text spacing, keyboard order and focus visibility, keyboard traps, heading structure, landmarks, form labels, target sizes, and the names and roles of controls.

We have not yet carried out manual testing with screen reading software, with speech recognition software, or with disabled users. Until we have, we do not make claims about how well the site works with those tools.

What we're doing to improve accessibility

We have an ongoing programme of work. In priority order:

  • fixing the keyboard traps, which are the issues most likely to stop someone completing a task
  • fixing the text spacing and target size issues across the shared card and listing layouts
  • adding the missing form labels and autofill information
  • testing with screen reading software, and then with disabled users
  • prompting event organisers for image descriptions when they add an event, and giving them guidance on writing accessible listings

Our automated tests will not let a new page or feature reach the site with a kind of accessibility problem we have already fixed, so the list above should only get shorter.

Preparation of this accessibility statement

This statement was prepared on 1 October 2024. It was last reviewed and updated on 20 September 2026, following a full audit of the site against WCAG 2.2 AA. We review it at least once a year, and whenever we re-test the site.