XClose

Accessibility

Menu

Microsoft Dynamics 365 accessibility statement

This accessibility statement applies to Microsoft Dynamics 365.

Dynamics 365 is run by Microsoft. Dynamics is the software that underpins the following UCL services:

  • Revenue Recognition

We want as many people as possible to be able to use this application, 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 application using just a keyboard
  • navigate the application using speech recognition software
  • listen to most of the application using a screen reader

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

How accessible this application is

We know some parts of this application are not fully accessible. You can see a full list of issues we currently know about in the non-accessible content section of this statement.

  • Some images do not have meaningful alternative text
  • Some elements do not have accessible names

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 service
  • If you find an accessibility problem not listed on this statement
  • If you have positive feedback on the accessibility considerations made. 

When you contact us there is a process in place that will acknowledge your contact, tell you who is dealing with it and give you a timescale by which you can expect a reply:

The IT (Information Technology) Services Service desk aims to respond to emails within one business day. 

If you need information on this website in a different format like accessible PDF (Portable Document Format), large print, easy read, audio recording or braille, please contact us.

Reporting accessibility problems with this application

We’re always looking to improve the accessibility of this application. 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 organisations 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 application's accessibility

University College London is committed to making its applications accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This application 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

This section covers issues that we need to fix and are working to do so.

Microsoft Dynamics 365 conformance report

Some non-text content may lack descriptive text alternatives, which can affect understanding for users relying on assistive technologies. This fails WCAG 1.1.1 Non-text Content (A).

Some user interface components may not fully expose their names, roles, or states to assistive technologies, which could affect how users interact with these elements. This fails WCAG 4.1.2 Name, Role, Value (A).

UCL audit

Creating a new proforma

After selecting "New", the keyboard focus lands on the "Proforma" tab, which skips the progress indicator at the top of the screen. While it reads well when navigated through backwards, users who cannot see the screen visually would not know it was there. This fails WCAG 1.3.3 Sensory Characteristics (A).

After selecting the Organisation, all auto-filled fields are read-only, but some empty read-only fields are not in the tab order while others are. This fails WCAG 2.1.1 Keyboard (A).

The very small plus icons, to indicate "recommended" fields, are so similar to the asterisks indicating "required" fields that it may cause confusion for users. This fails WCAG 3.3.2 Labels or Instructions (A).

After selecting "Save" without having filled in all required fields, a notification reading: "You have [number] new notifications. Select to view" appears at the top of the page, but this is not announced by some screen readers. This fails WCAG 3.3.1 Error Identification (A).

In some cases, the "unsaved" status after a failed save (triggering the notification above) is not announced to some screen readers, in which case it is only visible via the light grey "Unsaved" text next to the "New Opportunity" heading, which is also not announced to some screen readers. The unsaved status is only announced to all screen readers when the back button is pressed and "Save and close" selected from the pop-up, but not when the "Save" button is pressed on its own. This fails WCAG 4.1.3 Status Messages (AA).

Creating a new milestone

There appears to be no way to access the calendar/date picker using the keyboard, although the date can be entered manually. Both options should be available via all input methods. This fails WCAG 2.1.1 Keyboard (A).

Failure to save notifications are again not announced to some screen readers. This fails WCAG 4.1.3 Status Messages (AA).

Income calculations

When the modal for adding income details to a milestone is first opened, the keyboard focus/cursor lands automatically in the "Product Name" field, but the "Milestone" field is above it and is a required field, so the keyboard focus/cursor should land there upon opening. This would prevent users needing to tab backwards to fill out all required fields, and screen reader users in particular may not realise the previous fields are there to be filled in at all until an attempt to save has failed. This fails WCAG 2.4.3 Focus Order (A).

The calculator icon is accessible by keyboard as it toggles the visibility of the "Calculate" button; this is not really necessary as the "Calculate" button is quite a small button, and could just be kept in place without need for a toggle. Users relying on the mouse or keyboard rather than a screen reader would have less information than the screen reader users in this instance, as the tooltip on hover does not provide any information about what the icon button does. This fails WCAG 3.3.2 Labels or Instructions (A).

File upload

The file upload function announces when an upload is processing, but does not announce when the upload is complete (for all screen readers tested). This fails WCAG 4.1.3 Status Messages (AA).

Teams chat

The notifications on the chat icon button are not read by screen reader, although they are visually present on the icon. This fails WCAG 1.3.3 Sensory Characteristics (A).

Disproportionate burden

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

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

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
  • documents which are sent to us and uploaded, or comments left on pages by members of the public

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. 

UCL 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

This accessibility statement has been produced based on information provided in the Microsoft conformance report for Dynamics 365 Customer Engagement - Sales (Web).

UCL has also conducted its own accessibility audit, the findings from which have been included in the non-compliances section above.

Preparation of this accessibility statement

This statement was prepared on 25 June 2026. It was last reviewed on 25 June 2026. This application was last tested on 7 March 2026. The test was carried out by Microsoft. UCL have also carried out an independent audit and have reported the findings to Microsoft.