Accessibility This accessibility statement applies to https://www.ipsea.org.uk/ This website is run by IPSEA. 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: text does not meet sufficient contrast requirements against the page background a clear focus indicator is not always present when tabbing to page elements the focus order is not always logical when navigating with a keyboard and/or screen reader not all elements are accessible using a keyboard form input fields lack a correctly associated text label or descriptive title some page content may not be contained within a landmark element the heading structure is not always correct Feedback and contact information If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille: email [email protected] call 01799 582030 We’ll consider your request and get back to you in 5 working days. Reporting accessibility problems with this website We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: [email protected] Contacting us by phone We provide a text relay service for people who are D/deaf, hearing impaired or have a speech impediment. Find out how to contact us. Technical information about this website’s accessibility Compliance status This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to 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 Decorative images have informative alternative attributes, which present unnecessary information to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (non-text content). We plan to resolve this by: 31 July 2025 Form input fields lack a correctly 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: 31 July 2025 The ‘Close’ button within the Cookie Preferences window does not have an appropriate accessible name. Buttons without labels do not provide information about their functionality to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (non-text content). We plan to resolve this by: 31 July 2025 A layout table is present on the Homepage which may introduce reading and navigation order issues. Screen readers may interpret this as a data table. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to resolve this by: 31 July 2025 Tables on the Event pages are incorrectly formed, with table header cells not marked up as such. Screen reader users may have difficulty navigating these tables. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to resolve this by: 31 July 2025 Related ‘Accessibility’, ‘Get in touch’, and ‘Donate’ navigational links are not contained within a navigation element. This may make accessing the navigational content difficult for some screen reader users. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to resolve this by: 31 July 2025 Some page content may not be contained within a landmark element. This may impact users who navigate the page using landmarks. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to resolve this by: 31 July 2025 Some related form elements are not grouped using fieldset and legend. Some radio buttons or checkboxes may lack context without being grouped. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to resolve this by: 31 July 2025 The ‘Log in’ and ‘Basket’ links within the footer do not have the required parent roles present. Elements containing ARIA role values missing required parent element role values will not enable assistive technology to function as intended. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). We plan to resolve this by: 31 July 2025 For some input fields, such as ‘First name’, ‘Last name’, and ‘Email’, the autocomplete attribute is not present. This may require the user to manually fill these inputs. This fails WCAG 2.2 success criterion 1.3.5 (identify input purpose). We plan to resolve this by: 31 July 2025 Text lacks contrast against its background. People with low vision may have difficulty reading text that does not contrast with its background. This fails WCAG 2.2 success criterion 1.4.3 (contrast (minimum)). We plan to resolve this by: 31 July 2025 Some user interface components may not meet the contrast minimum of 3.5:1 when in both a selected and unselected state. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast). We plan to resolve this by: 31 July 2025 The ‘Cookie Preferences’ link below the footer and elements within the cookie preferences screen are not accessible when navigating using a keyboard. This may make navigation difficult or certain elements inaccessible to users who navigate with a keyboard. This fails WCAG 2.2 success criterion 2.1.1 (keyboard). We plan to resolve this by: 31 July 2025 Accesskeys ‘1’ and ‘2’ are present, which may conflict with user or assistive technology shortcut keys. This fails WCAG 2.2 success criterion 2.1.1 (keyboard). We plan to resolve this by: 31 July 2025 A correctly formed heading structure is not present within the homepage to facilitate navigation. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks). We plan to resolve this by: 31 July 2025 An iframe on the Donate page lacks a title. Screen reader users may not be able to identify the content or purpose of the iframe. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks). We plan to resolve this by: 31 July 2025 The focus order is not always logical when navigating with a keyboard, and with desktop and mobile screen readers enabled. This may result in keyboard and/or screen reader users becoming disoriented. This fails WCAG 2.2 success criterion 2.4.3 (focus order). We plan to resolve this by: 31 July 2025 Adjacent links that navigate to the same destination are present. This results in additional navigation and repetition for keyboard and screen reader users. This fails WCAG 2.2 success criterion 2.4.4 (link purpose (in context)). We plan to resolve this by: 31 July 2025 A clear and consistent visual focus indicator is not always present on the Donate page. 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: 31 July 2025 Focus is obscured when navigating with a keyboard to accordion elements on the FAQ page. Additionally, when the cookie banner is present, this obscures page content. This fails WCAG 2.2 success criterion 2.4.11 (focus not obscured (minimum)). We plan to resolve this by: 31 July 2025 Some accessible names may differ from the visual name on the FAQ page, which may impact users who navigate using voice recognition software. This fails WCAG 2.2 success criterion 2.5.3 (label in name). We plan to resolve this by: 31 July 2025 When pressing the Enter key on the keyboard to select the ‘Other’ input on the homepage, the users focus is unexpectedly reset to the top of the page. This fails WCAG 2.2 success criterion 3.2.2 (on input). We plan to resolve this by: 31 July 2025 Form fields on the Donate and Event pages lack an example of the required format within the fields label. Users may have trouble entering the correct information. This fails WCAG 2.2 success criterion 3.3.2 (labels or instructions). We plan to resolve this by: 31 July 2025 On the Donate and Event pages, suggestions on how to fix errors within the forms are not provided. This fails WCAG 2.2 success criterion 3.3.3 (error suggestion). We plan to resolve this by: 31 July 2025 Accordion elements on the FAQ page do not use supported ARIA attributes, which can cause assistive technologies to report nonsensical user interface information. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value). We plan to resolve this by: 31 July 2025 When navigating with Android TalkBack enabled, the navigation menu and accordions on the FAQ page are not announced as expected. Therefore, users may not be aware if these items are collapsed or expanded. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value). We plan to resolve this by: 31 July 2025 Screen reader users are not informed when accordions on the FAQ page are collapsed or expanded when they have been expanded by the user. This fails WCAG 2.2 success criterion 4.1.3 (status messages). We plan to resolve this by: 31 July 2025 Preparation of this accessibility statement This statement was prepared on 21/06/2024. It was last reviewed on 21/06/2024. This website was last tested on 19/06/2024. The test was carried out by Zoonou. Zoonou used WCAG-EM to define the pages tested and test approach. Manage Cookie Preferences