ÂÒÂ×Ðã

XClose

Accessibility

Home
Menu

Microsoft Authenticator Web and App accessibility statement

This accessibility statement applies to the Microsoft Authenticator mobile application.

Microsoft Authenticator is a Microsoft mobile application that also utilises a web page for interacting with the mobile 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 .

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

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.

.

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

Technical information about this website's accessibility 

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

Compliance status

Non-accessible content

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

Non-compliance with the accessibility regulations

Microsoft Authenticator Webpage.
No known issues.
If you find any issues with this site, please contact us.

Microsoft Authenticator (iOS)
Screen Reader users are not able to navigate using swipe right or left gestures when user activates 'I can't see the number'. This fails WCAG 1.3.2 Meaningful Sequence (A).

Screen Reader users are not able to fill authentication code in given time. Users are not able extend the 30 second times for one time passcode. This fails WCAG 2.2.1 Timing Adjustable (A).

Add Account: Colour Contrast ratio of 'x' icon button with its background is 1.605:1 is less than required 3:1. Also in the Authenticator (iOS)-Settings: Colour Contrast ratio of 'Toggle' icon button with its background is 1.2:1 is less than required 3:1. 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.

Microsoft Authenticator (Android)
Search Accounts: Colour Contrast ratio of placeholder text for 'Search Accounts' is 2.7:1 which is less than the required 4.5:1 with respect to its background. This fails WCAG 1.4.3 Contrast (Minimum) (AA).

Role is not defined for the controls present on the 'Help' page. This fails WCAG 4.1.2 Name, Role, Value (A).

Disproportionate burden

At this time, Microsoft 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-ÂÒÂ×Ðã 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 , 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 ²õ±ð°ù±¹¾±³¦±ð.Ìý

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 the developer. 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 25 April 2024. It was last reviewed on 15 September 2023. This application was last tested on 15 September 2023. The test was carried out by Microsoft.

What we’re doing to improve accessibility

University College London (ÂÒÂ×Ðã) are working 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.Â