Accessibility Statement

Accessibility statement for Royal Botanic Garden Edinburgh Shop

This accessibility statement applies to https://rbgeshop.org/

This website is run by Royal Botanical Garden Edinburgh. 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
  • complete and cancel all interactions using simple gestures
  • 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:

  • Informative images do not always have an appropriate alternative attribute, including logos and complex images.
  • Some decorative imagery contains inappropriate alternative text.
  • Related form elements are not grouped appropriately.
  • Autocomplete functionality is not available on some expected input fields.
  • Text does not always meet sufficient contrast requirements.
  • Headings are not appropriately structured across the site.
  • Tab order is not logical.
  • Focus indicator is not visible for some user interface elements.
  • Controls cannot always be cancelled using simple gestures.
  • Format requirements are not always specified within the error text or field label.

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 webmaster@rbge.org.uk
  • call 0131 552 7171

If you email us, please include ‘accessibility’ in your subject line. We’ll confirm receipt of your request and get back to you within seven 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, we’d love to hear from you. Please send us an email in which you describe the problem and tell us which page you were using when it happened. Send this email to webmaster@rbge.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).

 

Feedback and contact information

If you need information on this website in a different format, such as accessible PDF or large print, we will do our best to support you:

  • email webmaster@rbge.org.uk
  • call 0131 552 7171

If you email us, please include ‘accessibility’ in your subject line. We’ll confirm receipt of your request and get back to you within seven days.

You can find more contact details on our contact page.

Technical information about this website’s accessibility

The Royal Botanic Garden Edinburgh 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

Non-text Content

Some images do not have a text alternative, so people using a screen reader cannot access the information. This includes logos and complex images. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content.

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.

Images and links are not combined correctly, causing screen readers to announce content multiple times. This fails WCAG 2.2 success criterion 1.1.1 Non-text Content.

We are in the process of reviewing all images and buttons to ensure that they have meaningful alternative text within the next 12 months. We will continue to work with our website editors to provide them with training and guidance on best practices.

Info and Relationships

Semantic markup is not used correctly for some ARIA attributes which may cause incorrect announcements by screen readers. This fails WCAG 2.2 success criterion 1.3.1.

Related form elements are not grouped appropriately which may cause them to be announced incorrectly by screen readers. This fails WCAG 2.2 success criterion 1.3.1.

As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

Identify Input Purpose

A valid autocomplete attribute is not present on the address, payment and password fields and these fields cannot be programmatically determined. This fails WCAG 2.2 success criterion 1.3.5.

As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

Contrast (minimum)

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

We are in the process of reviewing our brand colour palette to ensure all text has sufficient contrast within the next 12 months. We will continue to work with our website editors to provide them with training and guidance on best practices.

 

Images of Text

Images of text are present across some of the pages. This may mean that users of screen readers are not able to access this information. This fails WCAG 2.2 success criterion 1.4.5.

We are reviewing our images to ensure that images of text provide the correct alternative for screen readers. We plan to resolve this within the next 12 months.

 

Reflow

Users who view the page within a 1280-pixel wide browser at a 400% zoom level cannot scroll when the menu is open, so the menu cannot be navigated. This fails WCAG 2.2 success criterion 1.4.10.

As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

 

Non-Text Contrast.

Some non-textual content lacks contrast with the background page and within the content itself. This includes buttons and error-identifying graphical objects. This fails WCAG 2.2 success criterion 1.4.11.

As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

 

Bypass Blocks.

A correctly formed heading structure is not present to facilitate navigation across the site, with skipped or no heading levels present. This fails WCAG 2.2 success criterion 2.4.1.

As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

 

Focus Order & Focus Not Obscured (Minimum).

Focused elements become obscured by the header if entering content from the ‘Skip to Main content’ button. This could cause confusion for users who navigate via keyboard. This fails WCAG 2.2 success criterion 2.4.11.

The tab order on some of the pages is not logical. The tab order does not reflect the visual hierarchy of the page or follow a left to right path. This fails WCAG 2.2 success criterion 2.4.3.

The tab order when using iOS VoiceOver (a mobile screen reader) to navigate is not logical. Opening the search bar overlay results in the user needing to tab backwards to access the search field. This fails WCAG 2.2 success criterion 2.4.3.

The tab order when using NVDA (a desktop screen reader) to navigate is not logical. The user must tab backwards to access the ‘Skip to Main Content’ Button. This fails WCAG 2.2 success criterion 2.4.3.

As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

 

Link Purpose (In Context)

Empty links that contain no text or images without an alternative text are present. The function or purpose of these links will not be presented to screen reader users. This fails WCAG 2.2 success criterion 2.4.4.

We are in the process of reviewing all links to ensure they have clear text indicating to the user the link’s destination. We plan to resolve this within the next 12 months.  

 

Focus Visible

The focus indicator is not visible for some user interface elements, including vertical scrollbars. This can make it difficult for keyboard-only users to keep track of the elements currently in focus. This fails WCAG 2.2 success criterion 2.4.7.
 
As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

 

Labels or Instructions.

Required formats are not communicated within the label of input fields. This fails WCAG 2.2 success criterion 3.3.2.
 
As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

Error Suggestion

Format requirements are not specified for the email field on the Create Account page. This fails WCAG 2.2 success criterion 3.3.3.
 
As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

 

Name, Role, Value

Zooming and scaling is disabled which may cause problems for mobile navigation. This fails WCAG 2.2 success criterion 4.1.2.

The increase button on the Basket page is not announced correctly by JAWS (a desktop screen reader). This fails WCAG 2.2 success criterion 4.1.2.
 
As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.



Status Messages

The newsletter subscription success status message is not announced by Android TalkBack (a mobile screen reader). This fails WCAG 2.2 success criterion 4.1.3.
 
As the site is run on a third-party platform, we have minimal influence on the code that is delivered to users. As part of an organisation-wide programme of digital transformation, we are in the process of reviewing our systems. This programme is underway and we expect to migrate to a new platform by December 2025.

 

What we’re doing to improve accessibility

We are continually working to improve the accessibility of our website. We conduct regular accessibility audits and act on their findings. We learn from these audits and other accessibility information, and we apply our increased knowledge to all updates we make.

Preparation of this accessibility statement

This statement was prepared on 05/06/2024. It was last reviewed on 09/05/2024.

This website was last tested on 08/05/2024. The test was carried out by Zoonou.

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

 

Every purchase supports the vital research and conservation work of the Royal Botanic Garden Edinburgh.