Accessibility statement for Amara Living

This accessibility statement applies to the website: AMARA.COM

We are currently in the process of assessing the cost to fix the issues identified and identifying a timeline to implement these.

This website is run by Amara Living. We want as many people as possible to be able to use this website. For example, that means you should be able to:

  •       change colors, contrast levels and fonts
  •       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)

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

 

Feedback and contact information

If you need information on this website in a different format:

  • Email customerservices@amara.com
  • Call 0800 587 7645
  • Unit 4 Concord Farm, School Road, Rayne, Braintree, Essex, CM77 6SP

We’ll consider your request and get back to you in 2 days.

 

How accessible this website is

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

  • Alternative text attributes for non-decorative imagery are absent and images of text are present
  • Buttons and form fields are not identified via accessible text
  • A skip to main content button is not present meaning users have to tab through repeated navigation elements
  • Skipped and empty heading levels are present, potentially causing issues for screen reader software
  • The tab order is deemed to be illogical across several pages
  • Two-dimensional scrolling is required to view content on several pages
  • Some status messages are not announced whilst using screen reader software
  • Some user interface components have a low color contrast to the site background
  • Multiple elements lack a visible tab focus indicator
  • Copy in several areas lacks sufficient contrast
  • The user is unable to reverse, check or confirm a legal or financial transaction
  • Menu content that appears on hover or focus cannot be dismissed without moving hover or focus
  • Suggestions are not provided for input errors when interacting with the Newsletter sign up form

 

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: customerservices@amara.com

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).

 

Contacting us by phone

You can contact our Customer Care team on 0800 587 7645.

 

Technical information about this website’s accessibility

Amara Living 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 partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.

 

Non-accessible content

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

Non-compliance with the accessibility regulations 

Buttons do not have an accessible name. Without an accessible name, the purpose of the button will not be announced to users who navigate with a screen reader. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-text Content

We plan to resolve this by: November 2021.

 

Decorative and or spacer imagery contains alternative text. This will result in unnecessary keyboard navigation and decorative images being announced to users who navigate with a screen reader. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-text Content 

We plan to resolve this by: November 2021.

 

Form inputs lack text labels and their purpose will not be announced to users who rely on navigating with a screen reader. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-text Content

We plan to resolve this by: November 2021.

 

Adjacent images and text links are not combined, resulting to the user having to tab to redundant links. This is a failure of WCAG 2.1 success criterion 1.1.1 Non-text Content

We plan to resolve this by: November 2021.

 

Page regions are not identified with landmarks. People navigating with a screen reader will not be made aware of the regions of the page. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships.

We plan to resolve this by: November 2021.

 

Related links are not grouped using the nav element. It is expected that related links that are visually grouped, are contained within a <nav> element. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships.

We plan to resolve this by: November 2021.

 

Related form elements are not grouped, so the purpose of these form elements may not be made clear to users of assistive technology. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships. 

We plan to resolve this by: November 2021.

 

Aria-controls and aria-labelledby attributes do not point to IDs of elements in the same document. This may cause elements to not be announced when focused by a screen reader. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships. 

We plan to resolve this by:November 2021.

 

On the ‘Contact Us’ webpage, the list ‘Opening Hours’ and telephone numbers list does not use expected semantic markup, for example 'ul', 'ol', or 'dl'. This is a failure of WCAG 2.1 success criterion 1.3.1 Info and Relationships.

We plan to resolve this by: November 2021.

 

Form fields lack an autocomplete attribute meaning that their purpose cannot be programmatically determined. This is a failure of WCAG 2.1 success criterion 1.3.5 Identify Input Purpose

We plan to resolve this by: November 2021.

 

Contrast issues are present for some text copy on the site. People with low vision may have difficulty reading text. This is a failure of WCAG 2.1 success criterion 1.4.3 Contrast (Minimum).

We plan to resolve this by: November 2021.

 

The basket total is illegible due to the white copy rendering on a white background, and the last link within the main navigation renders off screen. Furthermore, the chat functionality is inaccessible and footer dropdown copy within the language and currency overlap within the dropdown when zooming text only to 200%. This is a failure of WCAG 2.1 success criterion 1.4.4 Resize Text.

We plan to resolve this by: November 2021.

 

Some pages contain images of text. People with low vision may have trouble reading the text with the authored font family, size and/or color. This is a failure of WCAG 2.1 success criterion 1.4.5 Images of Text. 

We plan to resolve this by: November 2021.

 

Two-Dimensional scrolling is present when viewing the site at 400% zoom. This is a failure of WCAG 2.1 success criterion 1.4.10 Reflow.

We plan to resolve this by: November 2021.

 

There is insufficient contrast between the visual boundaries of user interface components. This issue may make it hard for users of low vision to decipher the boundary of user interface components. Graphical objects are also noted to lack contrast. This is a failure of WCAG 2.1 success criterion 1.4.11 Non-Text Contrast.

We plan to resolve this by: November 2021.

 

When applying custom text styling, on the ‘My Bag’ webpage, the ‘Add To Bag’ button overlaps the copy within the 3rd card element of ‘Inspiration for you’. People who require increased space between lines, words, and letters may be unable to read text within this page. This is a failure of WCAG 2.1 success criterion 1.4.12 Text Spacing.

We plan to resolve this by: November 2021.

 

No functionality is present within the website that allows users to dismiss hover content. This is a failure of WCAG 2.1 success criterion 1.4.13 Content on Hover or Focus.

We plan to resolve this by: November 2021.

 

The user is currently unable to tab to all elements when navigating by keyboard. This is a failure of WCAG 2.1 success criterion 2.1.1 Keyboard.

We plan to resolve this by: November 2021.

 

Iframes are not labeled in a way that assistive technologies are informed of its purpose. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks. 

We plan to resolve this by: November 2021.

 

The heading structure on some pages is incorrect due to skipped heading levels. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks.

We plan to resolve this by: November 2021.

 

A ‘Skip to main content’ button is not present. Users who rely on navigating via keyboard will be unable to skip components that are repeated across pages. This is a failure of WCAG 2.1 success criterion 2.4.1 Bypass Blocks.

We plan to resolve this by: November 2021.

 

It has been observed that the page title ‘New’ is duplicated across 2 different pages. People may be unable to differentiate content when multiple web pages are open. This is a failure of WCAG 2.1 success criterion 2.4.2 Page Titled.

We plan to resolve this by: November 2021.

 

The tabbing order is illogical, with the user being tabbed to the header logo after the elements on the right hand side. The cookie banner is also tabbed to after the main page content. This is a failure of WCAG 2.1 success criterion 2.4.3 Focus Order. 

We plan to resolve this by: November 2021.

 

Several instances of empty links are present. People with visual disabilities will be unable to determine the purpose or context of the link. This is a failure of WCAG 2.1 success criterion 2.4.4 Link Purpose (In Context).

We plan to resolve this by: November 2021.

 

On the ‘Homepage’ and the ‘Ideas Landing’ Page, headings are present which do not describe the topic or purpose. Users may be unable to predict what each section contains. This is a failure of WCAG 2.1 success criterion 2.4.6 Headings and Labels.

We plan to resolve this by: November 2021.

 

A visible focus indicator is not always present when navigating the site using a keyboard. People who rely on the keyboard to operate the page may not be able to visually determine the component on which keyboard operations will interact. This is a failure of WCAG 2.1 success criterion 2.4.7 Focus Visible. 

We plan to resolve this by: November 2021.

 

On the ‘Newsletter Sign Up’ form, when entering an incorrect email, a suggestion is not provided to the user on how to correctly fill in the field. This is a failure of WCAG 2.1 success criterion 3.3.3 Error Suggestion.

We plan to resolve this by: November 2021.

 

No ability is present on the ‘Payment’ page to reverse, check or confirm the submission. This is a failure of WCAG 2.1 success criterion 3.3.4 Error Prevention (Legal, Financial, Data).

We plan to resolve this by: November 2021.

 

HTML validation errors are present which may influence how assistive technology software handles content on the site. This is a failure of WCAG 2.1 success criterion 4.1.1 Parsing.

We plan to resolve this by: November 2021.

 

Users are unable to interact with all functionality using Dragon Naturally Speaking. People who use voice recognition software will be unable to interact with all of the functionality. This is a failure of WCAG 2.1 success criterion 4.1.2 Name, Role Value.

We plan to resolve this by: November 2021.

 

When navigating the site using Android TalkBack, several elements are announced incorrectly to the user. This is a failure of WCAG 2.1 success criterion 4.1.2 Name, Role Value.

We plan to resolve this by:November 2021.

 

Status messages, such as form submission confirmations, are not announced by screen readers. Resulting in screen users not being made aware of key prompts and information. This is a failure of WCAG 2.1 success criterion 4.1.3 Status Messages.

We plan to resolve this by: November 2021.

 

Preparation of this accessibility statement

This statement was prepared on 22/06/2021. It was last reviewed on 22/06/2021.

This website was last tested on 27/05/2020. The test was carried out by Zoonou.

We used this approach to deciding on a sample of pages to test WCAG-EM