XClose

Accessibility

Menu

Microsoft 365 Copilot accessibility statement

This accessibility statement applies to Microsoft 365 Copilot

Microsoft 365 Copilot is a Microsoft owned 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 400% 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

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 Copilot Support Team via MyServices 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 the Copilot Support Team, if there is a process in place to acknowledge your contact, you will receive an email stating who is dealing with your query. This response should also outline an potential timescales by which you can expect a reply.

We aim to respond to all contacts within 3-5 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.2 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 Copilot Support Team.

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

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 version 2.2 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

Microsoft 365 Copilot Windows 32.

Screen reader announces all the information correctly except for a few scenarios as listed below. These all fail WCAG 1.3.1 Info and Relationships (A):

  • In Outlook, upon invoking the "Generate" button, Narrator announces an extra announcement as 'editable text' along with the success message.
  • While navigating through suggestions list, Narrator announces additional information as "Exit Record filters menu bar, Enter Search results list, group,".
  • Narrator announces incorrect instructions while navigating through posted questions.

Narrator reads all content correctly except it stops reading the Tone/Reader Sentiment/Clarity section before reaching the end of the section. When it cuts out, it will read the first letter of the next word, then announce group. This fails WCAG 1.3.2 Meaningful Sequence (A).

In Outlook profile names do not look like interactive elements in summary by Copilot pane. Also, upon hovering on the username, button colour changes to blue. This Fails WCAG 1.4.1 Use of Colour (A).

Users can perform all key tasks using the keyboard. There are a few areas that users cannot access using keyboard navigation, these all fail WCAG 2.1.1 Keyboard (A) and are:

  • In Outlook, whereupon invoking any interactive element in the pane, keyboard navigation is not visible anywhere and no action is performed upon using Tab/Shift+ Tab/ arrow keys.
  • Keyboard and screen reader focus are not in sync while navigating through the 'More option' in chat.
  • Tooltips are not visible for Context data.
  • Json & remove file under feedback pane in chat when accessing through with tab key.
  • Tooltips do not close when users use the “Control” key to close the ‘Thumbs up/ Thumbs down’ tooltip.
  • Prompts are not accessible using arrow keys.

Upon using the Shift+ tab key from the Create a new Contact button focus gets lost, and no action is performed to navigate to Switch Copilots button. This fails WCAG 2.1.2 No Keyboard Trap (A).

All of the below items fail WCAG 2.4.3 Focus Order (A).

  • In PowerPoint, keyboard focus moves out of the 'Designer card' and is unable to interact with 'Designer card' using the enter key.
  • In Outlook feedback dialog, focus order is overall correct except for a few places such as while navigating inside/outside the Outlook Copilot pane, the focus order is inconsistent.
  • In Whiteboard, focus order does not start with Ideas that is the first control rather than menu's.
  • In Microsoft 365 Copilot, there are a few areas where focus order is not correct in ‘Copilot Chat’ section, including after activating ‘Copilot Chats’ control in ‘More’ control.
  • Focus moves out of the 'Edit your screenshot' popup without closing it.

In Whiteboard, the screen reader correctly announces all failure messages except for when it fails to copy content or when an incorrect file format is being uploaded. This fails WCAG 3.3.1 Error Identification (A).

All the controls have the correct name and role except a few areas such as In PowerPoint, the screen reader is announcing an incorrect name for the "Microsoft designer" logo. The below list fails WCAG 4.1.2 Name, Role, Value (A).

  • In Outlook, upon invoking the "Previous / Next" button in the Copilot card, Narrator remains silent.
  • Screen reader does not recognize the state of selection of some menu items.
  • In Whiteboard, Like and Dislike buttons are announced as toggle buttons.

In the PowerPoint-prompt area, the colour contrast between text and background on slides generated by PowerPoint Copilot is insufficient. Slides created by PowerPoint Copilot are unreadable due to dark text on dark backgrounds; increased colour contrast is necessary. In Outlook, "See all Prompts in Copilot lab" in dark mode and “Character limit exceeded, 2112/2000” has low contrast ratio. This fails WCAG 1.4.3 Contrast (Minimum) (AA).

Text resizes at 200% through Copilot experiences. There are a few instances where text truncates and fails WCAG 1.4.4 Resize text (AA):

  • In Word and Whiteboard while inserting images text on a designer card slightly truncates.
  • In Outlook, the suggestion list is getting truncated.
  • In Microsoft 365 Copilot, dialog is not adapting to 200% zoom properly and is not scrollable using up/down arrow keys.

Contrast of non-text controls/content has good contrast ration except for a few instances such as in PowerPoint "Create a new presentation based on file" option's button is appearing in pinkish red in Black and Dark Gray theme. In Outlook, the dismiss button has low contrast ratio. This fails WCAG 1.4.11 Non-text Contrast (AA 2.1 only).

In Outlook Copilot Keyboard focus indicator is not clearly visible at 'Open copilot for sale/Show contacts/Save this email/Dismiss’ buttons without any broken focus. This fails WCAG 2.4.7 Focus Visible (AA).

In Copilot users get all the status messages except when Narrator does not read the Copilot generated content by default. Narrator also does not inform users immediately when character limit is reached in Edit fields. This fails WCAG 4.1.3 Status Messages (AA 2.1 only).

Microsoft 365 Web Copilot

Info and relationships exist for all the components are properly defined in different Copilot versions, except in a few cases as listed below. These all fail WCAG 1.3.1 Info and Relationships (A).

  • In Copilot chat history pane of Office apps, the screen reader only reads the recent chat history by default and does not include the date announcement along with it. To read the chat history date, screen reader users can use scan/item/browse mode based on the screen reader.
  • When Sales Copilot is added to the Office and the user is drafting anything in Word and bringing Sales Copilot options and then using "/" in the menu, the heading of Copilot is also defined as a menu item.
  • In Copilot Chat, when there is some text already written, then navigating again to the field using JAWS, the screen reader is just reading the text, not the name and other details related to the chat field.

Keyboard navigation is working fine in all the different versions of Copilot and all interactive elements are working as expected. In Sales CoPilot (Not actual "Copilot") there are a few keyboard navigation and access issues. These fail WCAG 2.1.1 Keyboard (A) and are listed below:

  • Sales CoPilot does not have the Keyboard focus inside the pane.
  • Close Pane button is not keyboard navigable and users are not able to dismiss the pane using the ESC key.

All controls have correct Name, Role and Values defined, except for a few places that can be accessed with some workaround. The below items fail WCAG 4.1.2 Name, Role, Value (A):

  • In Copilot chat pane, when summarizing any document and navigating to the summary, the "AI generated content may be incorrect" disclaimer button does not have a label. To read the label, users need to use scan/browse mode and navigate to the associated visual label.
  • In Copilot chat history pane in PowerPoint, Date is added in the label of delete history. Screen reader is reading the "Press enter to delete this chat."
  • In Outlook, for Sales Copilot, the dismiss button and message tile on top of email has a name defined as "undefined".
  • For Sales Copilot in Outlook, the selection state of specific Copilot is not announced by the screen reader.

All text and controls zoom at 200% except some of the file reference suggestions for draft with Copilot in Word Online. Only the first file from the list of suggestions is visible on the screen; the rest are out of screen view. This fails WCAG 1.4.4 Resize text (AA).

For Sales Copilot in Outlook, there are few instances where 200% browser zoom is having some issues, as search suggestions are going out of view. Suggestion menu is partially visible, for example. This fails WCAG 1.4.4 Resize text (AA).

Please find below more Copilot results for other systems in link form below.

Copilot for MAC results are listed here.

Copilot for iOS results are listed here.

Copilot for Android results are listed here.

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 may 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

Microsfot tested this web application using a combination of manual and automated checks. If you find an issue we have not yet identified, you can report it to us. We’ll pass this information to Microsoft who will review the issue, make sure it is included in their plan to fix issues and add it into the accessibility statement when it is next updated.

Preparation of this accessibility statement

Microsoft 365 Copilot and Web Copilot

This statement was prepared on 18 March 2025. It was last reviewed on 18 March 2025. This application was last tested on 25 July 2024. The test was carried out by Microsoft you can view their full statement here.

What we’re doing to improve accessibility

University College London (UCL) are working with Microsoft 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.