Web accessibility

Accessibility statement for www.shop.bfi.org.uk

This accessibility statement applies to www.shop.bfi.org.uk

This website is run by the British Film Institute (BFI). We want as many people as possible to be able to use this website. For example, that means you should be able to:

change colours, contrast levels and fonts
zoom in up to 300% without the text spilling off the screen
navigate most of the website using just a keyboard
navigate most of the website using speech recognition software
listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

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

How accessible this website is

We know some parts of this website are not fully accessible:

adjacent image and text are not combined within a link
form inputs lack text labels
pages titles are not descriptive
related form elements are not grouped
link purpose cannot be determined
there are elements which cannot be accessed via keyboard navigation alone

Reporting accessibility problems with this website

If you have issues with using parts of our website or identify accessibility issues that we’ve not stated, please do get in touch using the feedback form at the bottom of each page so that we can address them:

Email: bfishop@bfi.org.uk

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

The British Film Institute (BFI) is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is not compliant with the Web Content Accessibility Guidelines version 2.2 AA standard. The non-compliances are listed below.

Non-accessible content

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

Non-compliance with the accessibility regulations

Adjacent image and text links are not combined, which may result in screen readers announcing these elements multiple times. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to resolve this by: July 2026

Some images do not have informative text alternatives, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to resolve this by: July 2026

Buttons do not have appropriate labels. Buttons without labels do not provide information about the functionality of the button to screen reader users. This can be seen on the ‘Product Detail’ page’s carousel buttons and sub-menu items within the navigation on mobiles. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to resolve this by: July 2026

Form input fields lack an associated text label or descriptive title. Incorrectly associated labels do not provide functionality or information about the form control to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to resolve this by: July 2026

A form label is present on the ‘Product Detail’ and ‘Checkout’ pages, but they are not correctly associated with the form control. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

We plan to resolve this by: July 2026

Grouped fields are not contained within a fieldset element, which may result in screen reader users missing content. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to resolve this by: July 2026

Semantic markup has not been used appropriately throughout the ‘Homepage’ and ‘Product Detail’ pages. List elements have not been marked-up correctly, meaning users of screen readers may not understand the type of list they’re navigating. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to resolve this by: July 2026

Sliders throughout the ‘Homepage’ and ‘Product Detail’ pages have ARIA roles which do not contain particular parents, which means that screen readers may not be able to convey this information to users. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to resolve this by: July 2026

ARIA Landmarks aren’t used to identify all page content. This may cause content to be missed by screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

We plan to resolve this by: July 2026

Information on the page is communicated only by colour. This may be difficult to understand for users with visual impairments or colour blindness. This can be seen throughout the site when the user interacts with the “Favourites” button. This fails WCAG 2.2 success criterion 1.4.1 (use of colour).

We plan to resolve this by: July 2026

Links within paragraphs of text are not sufficiently differentiated and may be less visible to users with visual impairments. This fails WCAG 2.2 success criterion 1.4.1 (use of colour).

We plan to resolve this by: July 2026

Text throughout the site does not meet sufficient contrast requirements against the page background. This fails WCAG 2.2 success criterion 1.4.3 (contrast (minimum)).

We plan to resolve this by: July 2026

Rendering issues are present with text when zooming text only to 200% using browser zoom controls. This fails WCAG 2.2 success criterion 1.4.4 (resize text).

We plan to resolve this by: July 2026

On the ‘Checkout’ page, the text scaling and zooming have been disabled. This means users who need bigger text to navigate the site might not be able to change this. This fails WCAG 2.2 success criterion 1.4.4 (resize text).

We plan to resolve this by: July 2026

Some content is not available when the browser size is reduced to 1280px and zoomed in 400%. This fails WCAG 2.2 success criterion 1.4.10 (reflow).

We plan to resolve this by: July 2026

Some non-textual content lacks contrast against the background page. This includes form field boundaries, the favourite button, which overlaps some of the product images, and radio buttons. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).

We plan to resolve this by: July 2026

Content that appears on hover or focus is unable to be dismissed without moving the pointer cursor. This fails WCAG 2.2 success criterion 1.4.13 (content on hover or focus).

We plan to resolve this by: July 2026

Content that appears on hover or focus disappears when the mouse is moved over the content. This fails WCAG 2.2 success criterion 1.4.13 (content on hover or focus).

We plan to resolve this by: July 2026

Some content is inaccessible when using a keyboard to navigate the site. This is seen globally, where the user is unable to access the account button within the main navigation. Also, within the ‘Product Listing’ pages, the main products on the page are inaccessible via a keyboard. This fails WCAG 2.2 success criterion 2.1.1 (keyboard).

We plan to resolve this by: July 2026

Frame elements are not appropriately titled, which may result in unexpected announcements by screen readers. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks).

We plan to resolve this by: July 2026

Page titles are not sufficiently descriptive or informative which may cause navigation issues between tabs. This fails WCAG 2.2 success criterion 2.4.2 (page titled).

We plan to resolve this by: July 2026

The focus order of the page is not logical when navigating with a mobile screen reader enabled. Throughout the mobile version of the site, the user is unable to swipe to all content on the page, limiting their access throughout. This fails WCAG 2.2 success criterion 2.4.3 (focus order).

We plan to resolve this by: July 2026

There are instances of links which cannot be determined which may affect how assistive technology users navigate the site. This fails WCAG 2.2 success criterion 2.4.4 (link purpose (in context)).

We plan to resolve this by: July 2026

The focus indicator is not visible for some user interface elements. This can make it difficult for keyboard-only users to track the elements in focus. This fails WCAG 2.2 success criterion 2.4.7 (focus visible).

We plan to resolve this by: July 2026

When the cookie banner is visible, the user is able to tab to elements which sit behind it. Additionally, the background page can be tabbed to once the “Shop” navigational menu is open. This could confuse users who navigate via keyboard. This fails WCAG 2.2 success criterion 2.4.11 (focus not obscured (minimum)).

We plan to resolve this by: July 2026

The displayed name of a user interface component does not always match the accessible label. This may result in navigation issues for speech recognition users. This fails WCAG 2.2 success criterion 2.5.3 (label in name).

We plan to resolve this by: July 2026

Across multiple pages, the navigation is not consistent, as the breadcrumb disappears off the page. This may hinder users who rely on screen magnification who benefit from being able to quickly locate repeated content. This fails WCAG success criterion 3.2.3 (consistent navigation).

We plan to resolve this by: July 2026

Required fields do not have a text error, which indicates the field has an error. This fails WCAG 2.2 success criterion 3.3.1(error identification).

We plan to resolve this by: July 2026

Format requirements are not specified for email address and credit card number fields, which may confuse some users. This fails WCAG 2.2 success criterion 3.3.1 (error identification).

We plan to resolve this by: July 2026

Format requirements are not specified with the field label for email address fields, which may hinder users from filling the form out correctly the first time. This fails WCAG 2.2 success criterion 3.3.2 (labels or instructions).

We plan to resolve this by: July 2026

Fields which have an error do not provide adequate suggestions on how to fix the error. This fails WCAG 2.2 success criterion 3.3.3 (error suggestion).

We plan to resolve this by: July 2026

When navigating with a screen reader, some elements announce incorrectly. Decorative chevrons are focused on and announced, error messages incorrectly inform the user of how to fix email address mistakes, hidden content can be heard, and duplicated announcements are made when tabbing to items within the ‘Search Tool’. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: July 2026

Within the ‘Homepage’ and ‘Product Listing’ page, the user may struggle to focus on the product items by tabbing alone. When navigating with JAWS (desktop screen reader) the user is able to focus on the image, which acts as a link, but for users of NVDA, the user must use the arrow keys to locate the hidden “View” button to access the ‘Product Detail’ page. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: July 2026

Some elements are not supported by ARIA attributes, which may interfere with the accessibility of the webpage. This can mainly be seen where radio buttons are present. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: July 2026

The main navigation sub-menu includes an ARIA-hidden element that contains focusable elements. This could impact the way screen reader users navigate this element. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: July 2026

The ARIA role is not appropriate for the elements on the ‘Homepage’ and ‘Product Listing’ pages. This means that users of assistive technology may not be able to access these elements. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: July 2026

On several pages, there are broken ARIA references. This may make it difficult for screen reader users to navigate the elements correctly. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: July 2026

Certain elements are not available to Dragon Naturally Speaking (speech recognition software) users. This includes the ‘Account’ button within the main navigation. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: July 2026

Dragon Naturally Speaking users can see hidden links when the command “Show Links” is spoken. This means that users may be confused to which link number relates to which element. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

We plan to resolve this by: July 2026

Additional content is not announced by a screen reader. This can be seen on all pages when the user signs up using their email address within the footer, the user is not informed that they have been successful. Additionally, new search items, new content within the slider and accordion elements are not announced when collapsed or expanded. This fails WCAG 2.2 success criterion 4.1.3 (status messages).

We plan to resolve this by: July 2026

What we’re doing to improve accessibility

We’re continuing to work with our accessibility partner Zoonou to run regular accessibility testing of our website and routinely address issues that occur.

Preparation of this accessibility statement

This statement was prepared on 27 February 2026. It was last reviewed on 27February 2026.

This website was last tested on 26 February 2026. The test was carried out by Zoonou.

Zoonou used WCAG-EM to define the pages tested and test approach.