Accessibility statement

This accessibility statement applies to the main domain of the Met Office Aeronautical Visualisation Service. It does not cover subdomains.

The Met Office runs this service. We want as many people as possible to be able to use our service. For example, that means you should be able to:

• zoom in up to 400% without the text spilling off the screen
• navigate most of the website using a keyboard or speech recognition software
• listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

How accessible the website is

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

Feedback and contact information

We're always looking to improve the accessibility of this application. If you find any problems that aren't listed on this page or think we're not meeting accessibility requirements, please contact enquiries@metoffice.gov.uk.

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille, please contact us:

• email enquiries@metoffice.gov.uk
• call 0370 900 0100 (from the UK).
• call +44 330 135 0000 (outside the UK).

We aim to respond to all reasonable requests for accessible information.

Reporting accessibility problems with this application

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

The Met Office is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website has been tested against the Web Content Accessibility Guidelines (WCAG) version 2.2 AA standard.

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

A summary of findings is provided below. For a more detailed list of known accessibility issues, please read the full list of accessibility failures.

Perceivable:

• There are images with empty or missing alt attributes where they are required to have it. This fails WCAG criterion 1.1.1: Non-text content (A).
• In the Map Drawer (Sites). There are lists that contain invalid direct children. For example, the Weather data list contains elements as direct children between list items. This fails criterion 1.3.1: Info and Relationships (A).
• There are RAG boxes (Red/Amber/Green colour selectors) that can be read by NVDA but the highlighted/selected letter (R, A, or G) are not announced differently from non-selected states; Therefore screen reader users cannot determine which severity level is currently active. This fails WCAG criterion 1.3.3: Sensory Characteristics (A).
• On the login form, the email field is set as type="text" when the expected format is an email. This fails WCAG criterion 1.3.5: Identify Input Purpose (AA).
• There are many instances (at time of this audit, 167) where an aerodrome’s safety status on map markers is conveyed solely through colour. This fails WCAG criterion 1.4.1: Use of Colour (A).
• There are text elements throughout, notably on the Report a problem page as an example that have insufficient contrast (1.32:1 ratio) caused by links within body text not being underlined. This fails WCAG criterion 1.4.3: Contrast (Minimum) (AA).
• The “Install MAVIS" PWA banner uses fixed positioning and remains locked in place during zoom; at 200%/400% zoom banner covers significant page content on the Settings page (and likely other pages). This fails WCAG criterion 1.4.10: Reflow (AA).
• There are Reports rendered as Canvas with no accessible alternative. This fails WCAG criterion 1.1.1: Non-text content (A).
• On the Map page, screen reader users receive zero information about weather conditions. This fails WCAG criterion 1.1.1: Non-text content (A).
• All aerodrome map markers have multiple structural and labelling violations. This fails WCAG criterion 1.3.1: Info and Relationships (Level A)
• Decorative SVGs are missing aria-hidden="true" on icon spans. Screen readers may announce "image" or "graphic" 6 times (once per list item), creating noise without conveying meaning. This fails WCAG criterion 1.3.1: Info and Relationships (Level A).
• On specific Report pages, the validity time selection lacks sufficient context as it has label focusable and radio input hidden. This fails WCAG criterion 1.3.1: Info and Relationships (Level A).
• The lack of proper landmark structure limits screen reader user navigation options. This fails WCAG criterion 1.3.1: Info and Relationships (Level A).
• Headings don’t represent the content structure correctly. This fails WCAG criterion 1.3.1: Info and Relationships (Level A).

Operable:

• Nested interactive controls cause keyboard accessibility failures. This fails WCAG criterion 2.1.1: Keyboard (A).
• User cannot navigate Map Display Settings page with keyboard alone; the tab key skips all toggle controls and only reaches the info modal trigger and 'Save' button; The user is effectively trapped with no way to change settings or exit efficiently. This fails WCAG criterion 2.1.2: No Keyboard Trap (A).
• The four main content areas are not contained within semantic landmarks (nav, main, aside, footer, etc). This makes it more challenging for users to navigate easily by keyboard and fails WCAG criterion 2.4.1: Bypass Blocks (A).
• The hamburger menu has an illogical tab order with skipped items and what seems like a dead end 2.1.2 (but isn't). This fails WCAG criterion 2.4.3: Focus Order (A).
• The map page lacks a semantic headings structure; therefore screen reader users cannot navigate by headings or understand page structure. This fails WCAG criterion 2.4.6: Headings and Labels (AA).
• On the Map page, Interactive elements have focus indicators hidden or removed by CSS. This fails WCAG criterion 2.4.7: Focus Visible (AA).

Understandable:

• The link to Research Programmes in the main navigation opens in same tab, replacing the MAVIS application entirely with MS Forms. Therefore the user loses MAVIS context and the only way for the user to return is the browser back button. This fails WCAG criterion 3.2.2: On Input (A).
• On the Help & Support page, the page title does not match navigation link label (“Onboarding Support”), creating confusion about the page’s purpose. This fails WCAG criterion 3.2.4: Consistent Identification (AA).
• On the Map page, all map markers have radio button labels positioned before inputs. Additionally: Labels reference inputs that are visually hidden (opacity:0). This fails WCAG criterion 3.3.2: Labels or Instructions (A).
• The Email field during login/registration must have the autocomplete attribute to help users fill up the common details more easily. This fails WCAG criterion 3.3.7: Redundant Entry (A).

Robust:

• The menu buttons have aria-label on child element instead of parent button element. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• Timeline changes do not announce status updates to screen readers. This fails WCAG criterion 4.1.3: Status Messages (AA).
• The Terrain Selection button has no accessible label. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• The Attribution button has no accessible label. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• The close-drawer button has no accessible label. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• The site-search button has no accessible label. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• The site-data-hamburger-menu button has no accessible label. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• On the Map Drawer – Sites, the target icon' has no accessible label. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• On the Map there is an iframe element lacking an accessible name. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• The Reports tab panel has an invalid ARIA attribute name. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• Radio buttons have contradictory disabled and readonly attributes. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• When using a keyboard to navigate the website, there is a hidden button within the navigation with no label or purpose. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• When using a keyboard to navigate the website, the tab key moves through hamburger menu items, but screen readers do not announce anything. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• The sidebar close button only announces "button" with no indication it closes sidebar or where it returns user. This fails WCAG criterion 4.1.2: Name, Role, Value (A).
• The three dots menu button announces only "button". This fails WCAG criterion 4.1.2.
• The button to focus the map on selected aerodromes only announces, "clickable button" (which is redundant). This fails WCAG criterion 4.1.2: Name, Role, Value (A).

Disproportionate burden

We have not made any disproportionate burden claims.

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

Online maps and mapping services

Our service includes the use of online maps to show certain geographical information. These are not used for navigational purposes and are exempt under the regulations. If you require the information presented in an online map in a different format, please contact us to discuss reasonable adjustments.

PDFs and other documents

Some of our PDFs and documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and certain bulletins or reports within the service as PDFs or PNGs. We are currently working on enhancing these essential documents or replacing them with accessible html web pages.

Any new PDFs or Word documents we publish will meet accessibility standards.

What we are doing to improve accessibility

We are actively improving the accessibility of MAVIS, starting with the issues that have the greatest impact on everyday use of the service.

Our initial focus is on making it easier to use MAVIS across all user devices, with screen readers and keyboards, so that people can move through the service more confidently and access the information they need.

We know that some parts of MAVIS are more challenging to make accessible. This is particularly true of weather information provided through PDFs and map‑based layers. These products rely heavily on visual formats and are developed across multiple teams here at the Met Office. We are working closely with our science and operational colleagues to improve how this information is presented and to explore more accessible ways of providing the same content.

For an example of the work we are doing to improve the accessibility of the reports and charts available in MAVIS, check out the regional pressure (QNH) report.

Over the next 6 months, we will continue to track progress made and review the service’s overall accessibility posture. This review will help us understand what is working well, what still needs attention, and where we should focus next.

Preparation of this accessibility statement

This statement was prepared on 10 March 2026. It was last reviewed on 21 April 2026.

This website was last tested on 27 February 2026 against the WCAG 2.2 standard.

The test was carried out by CACI Ltd. on behalf of the Met Office. The testing included a manual audit of a representative sample of pages and components, supported by automated testing tools and assistive technologies.