Miro Accessibility Statement

This accessibility statement applies to: https://miro.com/signup/

This website is bought and used by Apps Service Managements office at the University of 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 using browser or device settings
• Experience no time limits when using the site
• Use the website without having to repeatedly input information 

We’ve also made the website text as simple as possible to understand. However, some of our content is technical, and we use technical terms where there is no easier wording, we could use without changing what the text means.

Customising the Website

AbilityNet has advice on making your device easier to use if you have a disability. This is an external site with suggestions to make your computer more accessible:

AbilityNet - My Computer My Way

With a few simple steps you can customise the appearance of our website using your browser settings to make it easier to read and navigate:

Additional information on how to customise our website appearance

If you are a member of University staff or a student, you can use the free SensusAccess accessible document conversion service:

Information on SensusAccess

How accessible this Website is

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

• Some information is conveyed by colour only 
• Speech-to-text assistive software (for example, Dragon NaturallySpeaking) is not necessarily compatible with all browser configurations when using this website
• Text-to-speech assistive technology (Job Access with Speech (JAWS)) is not necessarily compatible with all browser configurations when using this website
• Not all content can be reached when navigating by keyboard
• Tabbing by keyboard does not follow a logical order
• Selection displays are not clearly visible or lack colour contrast 
• Inconsistent keyboard accessibility with some sections, like videos and drag-and-drop functions, being inaccessible
• Reflow is not enabled in the project section
• Colour contrasts do not necessarily meet the recommended Web Content Accessibility Guidelines 2.2 AA standard;
• Some URLs are not formatted correctly with meaningful hypertext
• There are pop-ups and new browser tabs that open without warning
• Captions are not functioning and not human corrected. There are no transcripts or audio descriptions.
• Tooltips are not consistently available or useful, with some obscuring content or missing on important icons or contain information necessary for the operation of the item 
• Users may need to complete a cognitive test to access the site
• Not all content can be magnified to 200% and reflow is not enabled to 400%
• There is movement that cannot be paused by the end user
• Headings are not used appropriately, formatted correctly and some headings are hidden
• Some non-text content is missing alt text or has inappropriate descriptions.
• Some parts of the website are not fully compatible with mobile accessibility functionality

Feedback and contact information

If you need information on this website in a different format, including accessible PDF, large print, audio recording or braille:

• Email: IS.Helpline@ed.ac.uk 
• Telephone: +44 (0)131 651 515 (Information Services Helpline)
• British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service.

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

Reporting accessibility problems with this website

We are 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:

• Email: IS.Helpline@ed.ac.uk 
• Telephone: +44 (0)131 651 515 (Information Services Helpline)
• British Sign Language (BSL) users can contact us via Contact Scotland BSL, the on-line BSL interpreting service.

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

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 please contact the Equality Advisory and Support Service (EASS) directly:

Contact details for the Equality Advisory and Support Service (EASS)

The government has produced information on how to report accessibility issues:

Reporting an accessibility problem on a public sector website

Contacting us by phone using British Sign Language

British Sign Language service

Contact Scotland BSL runs a service for British Sign Language users and all of Scotland’s public bodies using video relay. This enables sign language users to contact public bodies and vice versa. The service operates from 8.00am to 12.00am, 7 days a week.

Contact Scotland BSL service details.

Technical information about this website’s accessibility

The University of Edinburgh is committed to making its websites and applications 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.2 AA standard, due to the non-compliances listed below.

The full guidelines are available at:

Web Content Accessibility Guidelines (WCAG) 2.2 AA standard

Non accessible content

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

Non-compliance with the accessibility regulations

The following items to not comply with the WCAG 2.2 AA success criteria:

• Images lack alternative text
  • 1.1.1: Non-text Content
• Lack of transcripts for audio-only content.
  • 1.2.1 Audio-only and Video-only (Prerecorded)
• Captions are not working on user recorded videos and may not be human corrected and it is not possible to human correct the captions
  • 1.2.2 Captions (Prerecorded)
• Lack of audio descriptions for prerecorded videos.
  • 1.2.3 Audio Description or Media Alternative (Prerecorded)
• Certain ARIA roles must be contained by particular parents
  • 1.3.1: Info and Relationships
• The sequence of elements is not always logical for instance when using keyboard navigation
  • 1.3.2 Meaningful Sequence
• Some information is conveyed by colour only
  • 1.4.1: Use of Colour
• Colour contrast is not always sufficient between text and background colours
  • 1.4.3: Contrast (Minimum)
• Text should be able to be resized up to 200% without loss of content or functionality.
  • 1.4.4: Resize Text
• Reflow is not available on the project section 
  • 1.4.10: Reflow
• Tooltips are not accessible by mouse or assistive software, and some tooltips obscure content and some are needed for the operation of the item 
  • 1.4.13 – Content on Hover or Focus
• Some parts of the site aren’t accessible by keyboard, and some frames with focusable content have tabindex=-1
  • 2.1.1: Keyboard
• No option to pause moving content like loading icons and some demonstration videos.
  • 2.2.2: Pause, Stop, Hide
• Links do not always have meaningful hypertext
  • 2.4.4 Link Purpose in Context
• Headings are not used appropriately or formatted correctly and some headings are hidden
  • 2.4.6 Headings and Labels
• Where a keyboard user has tabbed to was not always sufficiently visible
  • 2.4.7 Focus visible
• Users are required to use a dragging motion in some places and there is no keyboard alternative
  • 2.5.7 Dragging Movements
• Users are not alerted when links open new windows or pop ups
  • 3.2.2: On Input
• The website is not fully compatible with assistive software as not all items are coded correctly e.g. – Not all buttons must have discernible text, ARIA dialog and alertdialog nodes do not always have an accessible name, Required ARIA attributes are not always provided, ARIA commands do not always have an accessible name and there are instances where interactive controls are nested.
  • 4.1.2 - Name, Role, Value

We aim to improve our website accessibility on a regular and continuous basis. See the section below ('What we're doing to improve accessibility') on how we are improving our website accessibility. 

We will continue to address the accessibility issues highlighted, working alongside the software suppliers of Miro to deliver a solution or suitable workaround. Unless specified otherwise, a complete solution or significant improvement will be in place for those items within our control by December 2025. 

Disproportionate burden

We are not currently claiming that any accessibility problems would be a disproportionate burden to fix.

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

At this time, we believe no content is out with the scope of the accessibility regulations.

What we’re doing to improve accessibility

We will continue to address the accessibility issues highlighted, working alongside the software suppliers of Miro to deliver a solution or suitable workaround. We have shared our accessibility testing results with Miro and are working together in the resolution of the identified issues, hoping to have a complete solution or significant improvement in place by December 2025. 

While we are in the process of resolving these accessibility issues, we will ensure reasonable adjustments are in place to make sure no user is disadvantaged. As changes are made, we will continue to review accessibility and retest the accessibility of this website.

Preparation of this accessibility statement

This statement was prepared on 20^th August 2024. It was last reviewed on 16 ^th December 2024.

The website was last tested on 19^th July 2024. The testing was carried out by the Service Management team at the University of Edinburgh using both automated and manual methods. The site was tested on a PC, primarily using the browsers Microsoft Edge (126.0.2592.113), Firefox (128.0.2) and Google Chrome (127.0.6533.73). Recent world-wide usage levels survey for different screen readers and browsers shows that Chrome, Mozilla Firefox and Microsoft Edge are increasing in popularity and Google Chrome is now the favoured browser for screen readers:

WebAIM: Screen Reader User Survey

The aforementioned three browsers have been used in certain questions for reasons of breadth and variety.

We ran automated testing using Axe DevTools and then manual testing that included:

• Spell check functionality;
• Scaling using different resolutions and reflow;
• Options to customise the interface (magnification, font, background colour, etc);
• Keyboard navigation and keyboard traps;
• Data validation;
• Warning of links opening in new tab or window;
• Information conveyed in the colour or sound only;
• Flashing, moving or scrolling text;
• Use with screen reading software (for example JAWS);
• Assistive software (TextHelp Read and Write, Windows Magnifier, ZoomText, Dragon Naturally Speaking, TalkBack and VoiceOver);
• Tooltips and text alternatives for any non-text content;
• Time limits;
• Compatibility with mobile accessibility functionality (Android and iOS);
• Any drag functionality and alternatives;
• Consistent help functions;
• No need to re-enter data already submitted;
• Any cognitive tests.

Change Log

This section will receive updates as and when accessibility improvements are made to the website.