XClose

Accessibility

Menu

Miro accessibility statement

This accessibility statement applies to the UCL Miro application.

Miro is a third-party application. We want as many people as possible to be able to use this website, which means that you should be able to:

  • change colours, contrast levels and fonts
  • zoom in up to 300% without the text spilling off the screen
  • navigate the website using just a keyboard
  • navigate the website using speech recognition software
  • listen to most of the website using a screen reader

Due to Miro being a third-party platform some aspects of its accessibility are outside of our immediate control.

There are a number of customisation options for your browser and device that could help you use this website and other websites more effectively. AbilityNet has advice on making your device easier to use if you have a disability.

Feedback and contact information

Please contact us if you have an accessibility query including:

  • If you are experiencing issues with accessing information or using the website
  • If you find an accessibility problem not listed on this statement
  • If you have positive feedback on the accessibility considerations made. 

When you contact UCL's Miro Team, there is a process in place to acknowledge your contact, tell you who is dealing with your query and give you a timescale by which you can expect a reply.

We aim to respond to all contacts within 2 working days.

Reporting accessibility problems with this website

We formally test the accessibility of key user journeys that represent the breadth of content across our website on a regular basis against WCAG (Web Content Accessibility Guidelines) 2.1 AA standards.

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 contact us.

Read tips on contacting organisation about inaccessible websites.

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

If you are in Northern Ireland and are not happy with how we respond to your complaint, you can contact the Equalities Commission for Northern Ireland who are responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’) in Northern Ireland

Technical information about this website's accessibility 

University College London is committed to making this 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 (WCAG) 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

Canvas content

Widgets

When using the widgets menu and guide dialog - custom controls do not provide name, role, or state information. This can make these features inaccessible to those using digital accessibility aides as Miro does not provide text alternatives for the above. This fails WCAG 1.1.1 Non-text Content (A).

On widgets the "Bulk mode" in notes is programmed as a list element. Also, some interactive elements are only styled to look like a list but are not programmatically indicated as such in the HTML. This means that screen readers can fail to convey information correctly to users. This fails WCAG 1.3.1 Info and Relationships (A).

On the widgets menu elements in the toolbar use colour as the only visual means to convey state, selection, or other information. This can cause confusion for users with colour deficiencies. This fails WCAG 1.4.1 Use of Colour (A).

On widgets the contrast ratio for "Type to bulk add notes" placeholder text is still below the minimum contrast ratio. This could cause users with moderately low vision trouble when trying to use this feature. This fails WCAG point 1.4.3 Contrast (Minimum) (AA).

Commenting

When adding a comment, the profile image beside the User Profile Name text is not marked as decorative. This could cause screen readers and other assistive technologies to misrepresent the icon, causing confusion for the user. This fails WCAG 1.1.1 Non-text Content (A).

The commenting function has the following accessibility issues:

  • Buttons are only styled to look like a list but are not programmatically indicated as such in the HTML.
  • The bell icon button is missing the "aria-label" attribute.
  • Some text areas are missing a label element.
  • The "Add a Comment" dialog is not marked as such.

All of the above could cause confusion for users who rely upon screen readers as the tool would not be able to correctly interpret information. These fail WCAG 1.3.1 Info and Relationships (A).

When adding a comment whilst using a screen reader the bell icon button is announced as "unlabelled one button" because it has no "aria-label" attribute. This can result in a confusing user experience for those who rely on screen readers. This fails WCAG 2.5.3 Label in Name (A).

If users try to override the text spacing when adding a comment some content can get cut off. This will cause those who rely on larger text spacing for their reading experience to potentially miss information. This fails WCAG 1.4.12 Text Spacing (AA).

When adding comments there is no visual indication of keyboard focus on the bell icon. This can lead to a confusing user journey for those who a reliant on keyboard navigation. This fails WCAG 2.4.7 Focus Visible (AA).

Exporting

When exporting boards the radio buttons are not nested in a field set element. This could lead screen readers to not announce the list option when tabbing through export options. This fails 1.3.1 Info and Relationships (A).

The export options on canvases fail because of the following reasons:

  • The export button is not operable/focusable with the keyboard.
  • The functionality to adjust the size of the image to export is not keyboard operable.
  • The "set start area" button and the "resize area controls" are not keyboard operable.

This can make the users journey confusing and/or difficult for those who rely on keyboard inputs to navigate. This fails 2.1.1 Keyboard (A).

When exporting the dropdown that appears by activating the Export button does not have an accessible name. This can make site orientation for users confusing. This fails WCAG 2.4.2 Page Titled (A).

Sharing

When sharing boards the groups of form controls do not provide <fieldset> and <legends> elements. his could lead screen readers to not announce the list option. This Fails 1.3.1 Info and Relationships (A).

Voting

When using the voting mechanism Miro fails for the following reasons:

  • The "voting area" cannot be resized/adjusted with the keyboard alone.
  • Keyboard users are not able to vote, interact or focus on elements on the CANVAS element.

The above can cause page navigation for keyboard users to be frustrating. This fails 2.1.1 Keyboard (A).

Miscellaneous

The canvas preview image does not programmatically provide alternative text for assistive technology. There is a read only screen reader mode that provides access to stickies, shapes, and text within the canvas area. This could be confusing for users who need to understand what a board contains before clicking on it. This fails WCAG 1.1.1 Non-text Content (A).

Controls on the canvas are not providing textual name, role and/or state. This could cause screen readers and other assistive technologies to misrepresent the icon, causing confusion for the user. This fails WCAG 1.1.1 Non-text Content (A).

On the canvas, the text above a Frame is only styled to look like heading but is not marked as such in HTML. This can cause screen reader technology to not properly announce the frame’s heading, misleading users. This fails WCAG 1.3.1 Info and Relationships (A).

On boards, frames in the bar/list view are not keyboard focusable. This will impact a keyboard only users use of the frame feature. This fails WCAG 2.1.1 Keyboard (A)

All sticky note elements (except black) do not meet the required contrast ratio of 3:1. This fails 1.4.11 Non-text Contrast (AA).

Some content/functionality can be lost on some screen ratios when using the share and export options on the canvas. This will cause those who rely on larger text/screen size for their reading experience to potentially miss information. This affects screen ratios of horizontal width 320 CSS pixels/vertical height is 256 CSS pixels for the following features:

  • Canvas: Share
  • Canvas: Export
  • Non-Canvas: Voting
  • Non-Canvas: Settings
  • Non-Canvas: Template picker

This fails WCAG 1.4.10 Reflow (AA)

Non-canvas content

On dashboards custom controls on the canvas are not providing textual name, role and/or state. This could cause screen readers and other assistive technologies to misrepresent the icon, causing confusion for the user. This fails WCAG 1.1.1 Non-text Content (A)

On dashboards, when using JAWS (screen reader) the "star" and the "three dot" menu are announced as "Kanban framework link". This does not occur with NVDA. This will cause confusion for any user of the JAWS service. This fails WCAG 4.1.2 Name, Role, Value (A)

Under templates the "Kanban Framework" dialog does not provide a adequately specific accessible label. This can cause screen readers to not adequately describe the option to the user. This fails WCAG 1.3.1 Info and Relationships (A)

When using reactions the heart, fire, hand, face, and celebration emojis do not meet the required contrast ratio of 3:1 which could make them hard to distinguish for users with moderately low vision. This fails WCAG 1.4.11 Non-text Contrast (AA).

If you find an issue that we have yet to identify, please contact us using one of the routes described in the ‘Reporting accessibility problems with this website’ section of this statement.

Disproportionate burden

At this time, we have not made any disproportionate burden claims.

Content that’s not within the scope of the accessibility regulations

This section covers issues that we do not need to fix right now. The law calls these exemptions.

Third-party content

Our websites contain third-party content. We do not have control over and are not responsible for the accessibility of this content, but we make best endeavours to work with the third-party to improve its accessibility. This may include:

  • links to non-UCL websites
  • content/functionality on our website
  • content hosted on other websites, such as social media sites.

To help accessibility compliance across the sector, University College London supports searchBOX , a centralised, independent directory of third-party accessibility information. 

searchBOX catalogues the contact information and accessibility statements of third-party suppliers, enables the sharing of community-generated accessibility statements, and allows users to map their supplier ecosystem. 

Users can access third-party accessibility statements using the free searchBOX Finder service. 

University College London encourages all our partners and suppliers to support this effort by ensuring that their accessibility information is included in the searchBOX directory. 

Our testing processes

We tested the website using a combination of manual and automated checks alongside reference to the existing conformance reports provided by OpenText. If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to the website owner who will review the issue, make sure it is included in our plan to fix issues and add it into the accessibility statement when it is next updated.

Preparation of this accessibility statement

This statement was prepared on 11/01/2023. It was last reviewed on 11/01/2023.

This website was last tested in July 2022. The test was carried out by Miro.

More information on Miro accessibility can be found in the following link: Miro accessibility statement.

This document was drafted using information from the Miro Accessibility Conformance Report (ACR) which can be found in the following link: Miro Accessibility Conformance Report (ACR).

What we’re doing to improve accessibility

UCL are working with Miro to fix or provide alternatives for all issues that we are made aware of and as identified by our periodic internal testing and auditing processes.