Emergency Nutrition Network is committed to making its website accessible, in accordance with the UK’s Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This accessibility statement applies to the Emergency Nutrition Network (ENN) website.  

Preparation of this accessibility statement

This statement was prepared on 19 July 2024 preceding the launch of ENN’s new website on 22 July 2024, based on an assessment by the web development company Olamalu.

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 office@ennonline.net
• Or call  (+44) 01865 372340  and ask for the Communications Manager

We’ll consider your request and get back to you in 14 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, please email us on office@ennonline.net

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

Emergency Nutrition Network (ENN) is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This website is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, specifically: 

• 1.1.1 Non-Text Content: we have provided text alternatives for non-text content that serves the same purpose.
• 1.2.1 Audio-Only and Video-Only: we have provided an alternative to video-only and audio-only content.
• 1.2.2 Captions (Prerecorded): we have provided captions for videos with audio.
• 1.2.3 Audio Description or Media Alternative: we have provided audio description or text transcript for videos with sound.
• 1.2.4 Captions (Live): we have added captions to live videos.
• 1.2.5 Audio Description (Pre-Recorded): we have provided audio descriptions for pre-recorded videos where the visual aspect is not explained in the dialog of the video.
• 1.3.1 Info and Relationships: Content, structure and relationships can be programmatically determined on forms and lists.
• 1.3.2 Meaningful Sequence: we have presented content in a meaningful order and have ensured that content presented on the page is logical & intuitive. We have used headings, lists, paragraphs etc to mark our content and have made sure our users can differentiate the navigation menus from main content.
• 1.3.3 Sensory Characteristics: we have ensured instructions don’t rely solely on sensory characteristics.
• 1.3.4 Orientation: our website adapts to portrait and landscape views.
• 1.3.5 Identify Input Purpose: we have ensured input fields must be programmatically determinable i.e we have used appropriate token values while using autocomplete attributes
• 1.4.1 Use of Colour: we don’t use presentation that relies solely on colour on our website. Instructions are provided in text for graphs and charts where colour is used to convey information.
• 1.4.2 Audio Control: audio does not play automatically.  Don’t play audio automatically if possible. If audio is more than 3 seconds we provide a pause/stop or a mechanism to control the audio player volume from the overall system volume.
• 1.4.3 Contrast Minimum: the contrast ratio between text and background is at least 4.5:1.
• 1.4.4 Resize Text: website text can be resized to 200% without loss of content or function.
• 1.4.5 Images of Text:  we don’t use images of text.
• 1.4.10 Reflow: our content retains meaning and function without scrolling in two dimensions. We have used Responsive Web Design (RWD) from the conception of design itself.
• 1.4.12 Text Spacing: the website  content and function retain meaning when users change elements of text spacing.
• 1.4.13 Content on Hover or Focus: when hover or focus triggers content to appear, it is dismissible, hoverable and persistent.
• 2.1.1 Keyboard: all functionality is accessible by keyboard with no specific timings.
• 2.1.2 No keyboard Trap: users can navigate to and from all content using a keyboard.
• 2.4.1 Bypass Blocks: we provide a way for users to skip repeated blocks of content e.g. we provide a skip link on top of the page to skip navigational menus.
• 2.4.2 Page Titles: we ensure we have helpful and clear page titles.
• 2.4.3 Focus Order: Our web components receive focus in a logical sequence. We have aligned the focus order with the reading order as much as possible in order to maintain a logical and intuitive navigation of the content. 
• 2.4.4 Link Purpose (In Context): Every link’s purpose is clear from its text or context e.g. we have avoided ambiguous links like “here” or “click here”
• 2.4.5 Multiple Ways: we offer at least two ways to find pages on our website. Breadcrumbs work if the users want to go back in a process or a layered structure. Search function is the most powerful to achieve faster navigation. Menus are the most straightforward way of finding content. 
• 2.4.6 Headings and Labels: headings and labels describe topic or purpose and follow a sequential order to avoid confusion.
• 2.4.7 Focus Visible: keyboard focus is visible when used. Browsers handle the visible focus for active elements. When the user is navigating through the page using the keyboard, visible focus moves along for every element presented on the page.
• 2.4.11 Focus Not Obscured (Minimum): when a user interface component is selected, the focus indicator encompasses the visual presentation of the component, maintains a contrast ratio of at least 3:1 between its pixels in focused and unfocused states, and ensures a contrast ratio of at least 3:1 against adjacent colours.
• 2.5.3 Label in Name: where a component has a text label, the name of the component also contains the text displayed.
• 2.5.8 Target Size (Minimum):  we have ensured the target of any UI element has 24 by 24 CSS PX target size or there is enough spacing provided between two targets that have undersize targets.
• 3.1.1 Language of Page: Each webpage has a default human language assigned.
• 3.2.1 On Focus: elements do not change when they receive focus.
• 3.2.2 On Input: elements do not change when they receive input. We provide a submit button for all forms and ensure that control of how data is populated is in the hands of our users.
• 3.2.3 Consistent Navigation:  we have positioned menus and standard controls consistently. All the standard elements like logo, search functionality, and skip links etc are represented in the same location on all pages.
• 3.2.4 Consistent Identification: components with the same function are identified consistently e.g. Facebook, YouTube etc.
• 3.3.1 Error Identification: we identify and describe input errors for users. We do not just use colour or visual cues to point out form errors.
• 3.3.2 Labels or Instruction: we provide labels or instructions for user input using a webform module e.g. we provide group level labels and associate them with the group of form fields where the user input is required in more than one field like phone number or credit card number
• 3.3.3 Error Suggestion: We suggest corrections when users make mistakes, using a webform module.
• 3.3.7 Redundant Entry: we use autofill form- fields that repeat across steps so that users can select the information that they previously entered
• 3.3.8 Accessible Authentication (Minimum): Users are able to access authentication methods using only a keyboard. This means that the authentication process should not require the use of a mouse or other pointing device.