Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction26 landmarksFIX
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.
Learn more ▾ ▴
The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.
Source: WAI-ARIA / WCAG 2.4.1
Multiple navigations need aria-label to distinguish them for screen readers.
Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.
Learn more ▾ ▴
When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.
Source: WAI-ARIA Authoring Practices
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
FHeading HierarchyAction343 headings, 43 skip(s)FIX
- H6 Languages
- H5 Seventh Assessment Report
- H5 Sixth Assessment Report
- H5 Special and Methodology Reports
- H5 Working Group I
- H5 Working Group II
- H5 Working Group III
- H5 TFI
- H1 The Intergovernmental Panel on Climate Change
- H3 The Intergovernmental Panel on Climate Change (IPCC) is the United Nations body for assessing the science related to climate change. skipped
- H6 Latest skipped
- H2 The IPCC was created to provide policymakers with regular scientific assessments on climate change, its implications and potential future risks, as well as to put forward adaptation and mitigation op
- H5 Follow skipped
- H5 Engage
- H5 Learn More
- H2 Activities
- H5 Meeting skipped
- H4 Opening of the Sixty-fourth Session of the IPCC
- H6 March 24, 2026 skipped
- H5 Expert Meetings & Workshops
- H4 IPCC Expert Meeting on Adaptation Metrics, Methodologies and Indicators
- H6 March 3, 2026 skipped
- H5 Expert Meetings & Workshops
- H4 IPCC Workshop on Engaging Diverse Knowledge Systems and IPCC Workshop on Methods of Assessment
- H6 February 10, 2026 skipped
- H5 Expert Meetings & Workshops
- H4 IPCC – Wellcome Trust Co-sponsored Expert Meeting on Climate Change and Health
- H6 January 27, 2026 skipped
- H5 Lead Author Meetings
- H4 Third Lead Author Meeting for the Special Report on Climate Change and Cities
- H6 January 12, 2026 skipped
- H5 Lead Author Meetings
- H4 Joint First Lead Author Meeting for Working Groups I, II and III
- H6 December 1, 2025 skipped
- H2 Reports
- H3 Special Report
- H5 Special Report skipped
- H3 The Ocean and Cryosphere in a Changing Climate
- H4 September 2019
- H5 Working Group Report
- H3 Global Warming of 1.5°C
- H4 October 2018
- H5 Working Group Report
- H3 Climate Change and Land
- H4 August 2019
- H5 Special Report
- H3 Aviation and the Global Atmosphere
- H4 March 1999
- H3 Methodology Report
- H5 Working Group Report skipped
- H3 2027 IPCC Methodology Report on Inventories for Short-lived Climate Forcers
- H4 December 2027
- H5 Working Group Report
- H3 2027 IPCC Methodology Report on Carbon Dioxide Removal Technologies, Carbon Capture, Utilization, and Storage for National Greenhouse Gas Inventories (Additional guidance)
- H4 December 2027
- H5 Methodology Report
- H3 1994 IPCC Guidelines for National Greenhouse Gas Inventories
- H4 May 1994
- H3 Sixth Assessment Report: 2023
- H5 Synthesis Report skipped
- H3 AR6 Synthesis Report: Climate Change 2023
- H4 March 2023
- H5 Working Group Report
- H3 AR6 Climate Change 2022: Impacts, Adaptation and Vulnerability
- H4 February 2022
- H5 Working Group Report
- H3 AR6 Climate Change 2022: Mitigation of Climate Change
- H4 April 2022
- H5 Working Group Report
- H3 AR6 Climate Change 2021: The Physical Science Basis
- H4 August 2021
- H3 Special and Methodology Reports
- H5 Special Report skipped
- H3 Special Report on Climate Change and Cities
- H4 March 2027
- H5 Working Group Report
- H3 2027 IPCC Methodology Report on Inventories for Short-lived Climate Forcers
- H4 December 2027
- H5 Working Group Report
- H3 2027 IPCC Methodology Report on Carbon Dioxide Removal Technologies, Carbon Capture, Utilization, and Storage for National Greenhouse Gas Inventories (Additional guidance)
- H4 December 2027
- H5 Working Group Report
- H3 Global Warming of 1.5°C
- H4 October 2018
- H3 Seventh Assessment Report: 2029
- H5 Synthesis Report skipped
- H3 AR7 Synthesis Report: Climate Change
- H4 March 2026
- H5 Working Group Report
- H3 AR7 Climate Change: Impacts, Adaptation and Vulnerability
- H4 March 2026
- H5 Working Group Report
- H3 AR7 Climate Change: The Physical Science Basis
- H4 March 2026
- H5 Working Group Report
- H3 AR7 Climate Change: Mitigation of Climate Change
- H4 March 2026
- H3 Fifth Assessment Report: 2014
- H5 Synthesis Report skipped
- H3 AR5 Synthesis Report: Climate Change 2014
- H4 October 2014
- H5 Working Group Report
- H3 AR5 Climate Change 2013: The Physical Science Basis
- H4 September 2013
- H5 Working Group Report
- H3 AR5 Climate Change 2014: Impacts, Adaptation, and Vulnerability
- H4 March 2014
- H5 Working Group Report
- H3 AR5 Climate Change 2014: Mitigation of Climate Change
- H4 April 2014
- H3 Fourth Assessment Report: 2007
- H5 Synthesis Report skipped
- H3 AR4 Climate Change 2007: Synthesis Report
- H4 September 2007
- H5 Working Group Report
- H3 AR4 Climate Change 2007: The Physical Science Basis
- H4 June 2007
- H5 Working Group Report
- H3 AR4 Climate Change 2007: Impacts, Adaptation, and Vulnerability
- H4 July 2007
- H5 Working Group Report
- H3 AR4 Climate Change 2007: Mitigation of Climate Change
- H4 June 2007
- H3 Third Assessment Report: 2001
- H5 Synthesis Report skipped
- H3 TAR Climate Change 2001: Synthesis Report
- H4 October 2001
- H5 Working Group Report
- H3 TAR Climate Change 2001: The Scientific Basis
- H4 January 2001
- H5 Working Group Report
- H3 TAR Climate Change 2001: Impacts, Adaptation, and Vulnerability
- H4 May 2001
- H5 Working Group Report
- H3 TAR Climate Change 2001: Mitigation
- H4 July 2001
- H3 Second Assessment Report: 1995
- H5 Synthesis Report skipped
- H3 SAR Climate Change 1995: Synthesis Report
- H4 October 1995
- H5 Working Group Report
- H3 SAR Climate Change 1995: The Science of Climate Change
- H4 February 1995
- H5 Working Group Report
- H3 SAR Climate Change 1995: Impacts, Adaptations and Mitigation of Climate Change: Scientific-Technical Analyses
- H4 July 1995
- H5 Working Group Report
- H3 SAR Climate Change 1995: Economic and Social Dimensions of Climate Change
- H4 July 1995
- H3 First Assessment Report: 1990
- H5 Synthesis Report skipped
- H3 FAR Climate Change: Synthesis
- H4 March 1990
- H5 Working Group Report
- H3 FAR Climate Change: Scientific Assessment of Climate Change
- H4 June 1990
- H5 Working Group Report
- H3 FAR Climate Change: Impacts Assessment of Climate Change
- H4 July 1990
- H5 Working Group Report
- H3 FAR Climate Change: The IPCC Response Strategies
- H4 October 1990
- H3 Special Report
- H5 Special Report skipped
- H3 The Ocean and Cryosphere in a Changing Climate
- H4 September 2019
- H5 Working Group Report
- H3 Global Warming of 1.5°C
- H4 October 2018
- H5 Working Group Report
- H3 Climate Change and Land
- H4 August 2019
- H5 Special Report
- H3 Aviation and the Global Atmosphere
- H4 March 1999
- H3 Methodology Report
- H5 Working Group Report skipped
- H3 2027 IPCC Methodology Report on Inventories for Short-lived Climate Forcers
- H4 December 2027
- H5 Working Group Report
- H3 2027 IPCC Methodology Report on Carbon Dioxide Removal Technologies, Carbon Capture, Utilization, and Storage for National Greenhouse Gas Inventories (Additional guidance)
- H4 December 2027
- H5 Methodology Report
- H3 1994 IPCC Guidelines for National Greenhouse Gas Inventories
- H4 May 1994
- H3 Sixth Assessment Report: 2023
- H5 Synthesis Report skipped
- H3 AR6 Synthesis Report: Climate Change 2023
- H4 March 2023
- H5 Working Group Report
- H3 AR6 Climate Change 2022: Impacts, Adaptation and Vulnerability
- H4 February 2022
- H5 Working Group Report
- H3 AR6 Climate Change 2022: Mitigation of Climate Change
- H4 April 2022
- H5 Working Group Report
- H3 AR6 Climate Change 2021: The Physical Science Basis
- H4 August 2021
- H3 Special and Methodology Reports
- H5 Special Report skipped
- H3 Special Report on Climate Change and Cities
- H4 March 2027
- H5 Working Group Report
- H3 2027 IPCC Methodology Report on Inventories for Short-lived Climate Forcers
- H4 December 2027
- H5 Working Group Report
- H3 2027 IPCC Methodology Report on Carbon Dioxide Removal Technologies, Carbon Capture, Utilization, and Storage for National Greenhouse Gas Inventories (Additional guidance)
- H4 December 2027
- H5 Working Group Report
- H3 Global Warming of 1.5°C
- H4 October 2018
- H3 Seventh Assessment Report: 2029
- H5 Synthesis Report skipped
- H3 AR7 Synthesis Report: Climate Change
- H4 March 2026
- H5 Working Group Report
- H3 AR7 Climate Change: Impacts, Adaptation and Vulnerability
- H4 March 2026
- H5 Working Group Report
- H3 AR7 Climate Change: The Physical Science Basis
- H4 March 2026
- H5 Working Group Report
- H3 AR7 Climate Change: Mitigation of Climate Change
- H4 March 2026
- H3 Fifth Assessment Report: 2014
- H5 Synthesis Report skipped
- H3 AR5 Synthesis Report: Climate Change 2014
- H4 October 2014
- H5 Working Group Report
- H3 AR5 Climate Change 2013: The Physical Science Basis
- H4 September 2013
- H5 Working Group Report
- H3 AR5 Climate Change 2014: Impacts, Adaptation, and Vulnerability
- H4 March 2014
- H5 Working Group Report
- H3 AR5 Climate Change 2014: Mitigation of Climate Change
- H4 April 2014
- H3 Fourth Assessment Report: 2007
- H5 Synthesis Report skipped
- H3 AR4 Climate Change 2007: Synthesis Report
- H4 September 2007
- H5 Working Group Report
- H3 AR4 Climate Change 2007: The Physical Science Basis
- H4 June 2007
- H5 Working Group Report
- H3 AR4 Climate Change 2007: Impacts, Adaptation, and Vulnerability
- H4 July 2007
- H5 Working Group Report
- H3 AR4 Climate Change 2007: Mitigation of Climate Change
- H4 June 2007
- H3 Third Assessment Report: 2001
- H5 Synthesis Report skipped
- H3 TAR Climate Change 2001: Synthesis Report
- H4 October 2001
- H5 Working Group Report
- H3 TAR Climate Change 2001: The Scientific Basis
- H4 January 2001
- H5 Working Group Report
- H3 TAR Climate Change 2001: Impacts, Adaptation, and Vulnerability
- H4 May 2001
- H5 Working Group Report
- H3 TAR Climate Change 2001: Mitigation
- H4 July 2001
- H3 Second Assessment Report: 1995
- H5 Synthesis Report skipped
- H3 SAR Climate Change 1995: Synthesis Report
- H4 October 1995
- H5 Working Group Report
- H3 SAR Climate Change 1995: The Science of Climate Change
- H4 February 1995
- H5 Working Group Report
- H3 SAR Climate Change 1995: Impacts, Adaptations and Mitigation of Climate Change: Scientific-Technical Analyses
- H4 July 1995
- H5 Working Group Report
- H3 SAR Climate Change 1995: Economic and Social Dimensions of Climate Change
- H4 July 1995
- H3 First Assessment Report: 1990
- H5 Synthesis Report skipped
- H3 FAR Climate Change: Synthesis
- H4 March 1990
- H5 Working Group Report
- H3 FAR Climate Change: Scientific Assessment of Climate Change
- H4 June 1990
- H5 Working Group Report
- H3 FAR Climate Change: Impacts Assessment of Climate Change
- H4 July 1990
- H5 Working Group Report
- H3 FAR Climate Change: The IPCC Response Strategies
- H4 October 1990
- H3 Special Report
- H5 Special Report skipped
- H3 The Ocean and Cryosphere in a Changing Climate
- H4 September 2019
- H5 Working Group Report
- H3 Global Warming of 1.5°C
- H4 October 2018
- H5 Working Group Report
- H3 Climate Change and Land
- H4 August 2019
- H5 Special Report
- H3 Aviation and the Global Atmosphere
- H4 March 1999
- H3 Methodology Report
- H5 Working Group Report skipped
- H3 2027 IPCC Methodology Report on Inventories for Short-lived Climate Forcers
- H4 December 2027
- H5 Working Group Report
- H3 2027 IPCC Methodology Report on Carbon Dioxide Removal Technologies, Carbon Capture, Utilization, and Storage for National Greenhouse Gas Inventories (Additional guidance)
- H4 December 2027
- H5 Methodology Report
- H3 1994 IPCC Guidelines for National Greenhouse Gas Inventories
- H4 May 1994
- H2 Working Groups and Task Force
- H4 Working Group I skipped
- H6 August 2017 skipped
- H4 Working Group II
- H6 January 2018 skipped
- H4 Working Group III
- H6 August 2017 skipped
- H4 TFI
- H6 November 2016 skipped
- H4 Follow the IPCC
- H4 Engage with the IPCC
- H4 © 2026 The Intergovernmental Panel on Climate Change
- H3 Reports
- H5 Seventh Assessment Report skipped
- H5 Sixth Assessment Report
- H5 Special and Methodology Reports
- H3 Working Groups
- H5 Working Group I skipped
- H5 Working Group II
- H5 Working Group III
- H5 TFI
- H3 Activities
- H5 Press Release skipped
- H4 IPCC authors begin work on Methodology Report on Carbon Dioxide Removal Technologies, Carbon Capture, Utilization, and Storage
- H6 April 2026 skipped
- H5 Press Release
- H4 IPCC wraps up 64th plenary session in Bangkok
- H6 March 2026 skipped
- H5 Press Release
- H4 IPCC opens its Sixty Fourth Plenary Session in Bangkok, Thailand
- H6 March 2026 skipped
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
FLink & Button QualityAction101 issue(s) across 303 links and 1 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.ipcc.ch | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/meeting-doc/ipcc-64/ | IPCC-64 | new tab | Add '(opens in new tab)' to text |
| https://www.ipcc.ch/about/vacancies/ | Vacancies | new tab | Add '(opens in new tab)' to text |
| https://www.ipcc.ch/2026/04/14/pr-ipcc-c… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Pr Ipcc Cdrt Mr First Lead Author Meeting | |||
| https://www.ipcc.ch/2026/03/19/ipccs-six… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Ipccs Sixty Fourth Plenary In Bangkok Thailand | |||
| https://www.ipcc.ch/2025/11/19/calltficd… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Calltficdrccus | |||
| https://www.ipcc.ch/2026/03/27/ipcc-64th… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Ipcc 64th Plenary Session | |||
| https://www.ipcc.ch/2026/04/14/pr-ipcc-c… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Pr Ipcc Cdrt Mr First Lead Author Meeting | |||
| https://www.ipcc.ch/2026/03/19/ipccs-six… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Ipccs Sixty Fourth Plenary In Bangkok Thailand | |||
| https://www.ipcc.ch/2025/11/19/calltficd… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Calltficdrccus | |||
| https://www.ipcc.ch/2026/03/27/ipcc-64th… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Ipcc 64th Plenary Session | |||
| https://www.ipcc.ch/2026/04/14/pr-ipcc-c… | Read more | generic text | Replace with descriptive text |
Before: Read more Suggested: Pr Ipcc Cdrt Mr First Lead Author Meeting | |||
| https://www.ipcc.ch/site/assets/uploads/… | endorsed the action by WMO and… | new tab | Add '(opens in new tab)' to text |
| https://facebook.com/IPCC | new tab | Add '(opens in new tab)' to text | |
| https://twitter.com/IPCC_ch | svg{fill:#5492cd} | new tab | Add '(opens in new tab)' to text |
| https://youtube.com/IPCCGeneva | YouTube | new tab | Add '(opens in new tab)' to text |
| https://instagram.com/IPCC | new tab | Add '(opens in new tab)' to text | |
| http://slideshare.com/IPCCGeneva | SlideShare | new tab | Add '(opens in new tab)' to text |
| https://www.ipcc.ch/about/engage_with_th… | Learn More | generic text | Replace with descriptive text |
Before: Learn More Suggested: Engage With The Ipcc | |||
| https://www.ipcc.ch/report/srocc/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sr15/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/srccl/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/aviation-and-… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/methodology-r… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/2027-ipcc-met… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ipcc-guidelin… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sixth-assessm… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sixth-assessm… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sixth-assessm… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sixth-assessm… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/special-repor… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/methodology-r… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/2027-ipcc-met… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sr15/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/seventh-asses… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/seventh-asses… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/seventh-asses… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/seventh-asses… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar5/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar5/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar5/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar5/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar4/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar4/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar4/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar4/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar3/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar3/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar3/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar3/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar2/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar2/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar2/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar2/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar1/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar1/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar1/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar1/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/srocc/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sr15/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/srccl/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/aviation-and-… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/methodology-r… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/2027-ipcc-met… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ipcc-guidelin… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sixth-assessm… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sixth-assessm… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sixth-assessm… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sixth-assessm… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/special-repor… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/methodology-r… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/2027-ipcc-met… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sr15/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/seventh-asses… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/seventh-asses… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/seventh-asses… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/seventh-asses… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar5/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar5/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar5/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar5/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar4/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar4/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar4/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar4/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar3/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar3/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar3/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar3/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar2/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar2/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar2/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar2/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar1/syr/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar1/wg1/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar1/wg2/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ar1/wg3/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/srocc/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/sr15/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/srccl/ | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/aviation-and-… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/methodology-r… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/2027-ipcc-met… | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch/report/ipcc-guidelin… | (empty) | empty | Add link text or aria-label |
| https://facebook.com/IPCC | new tab | Add '(opens in new tab)' to text | |
| https://twitter.com/IPCC_ch | svg{fill:#5492cd} | new tab | Add '(opens in new tab)' to text |
| https://youtube.com/IPCCGeneva | YouTube | new tab | Add '(opens in new tab)' to text |
| https://instagram.com/IPCC | new tab | Add '(opens in new tab)' to text | |
| http://slideshare.com/IPCCGeneva | SlideShare | new tab | Add '(opens in new tab)' to text |
| https://www.ipcc.ch/about/engage_with_th… | Learn more | generic text | Replace with descriptive text |
Before: Learn more Suggested: Engage With The Ipcc | |||
| https://www.ipcc.ch | (empty) | empty | Add link text or aria-label |
| # | (empty) | empty | Add link text or aria-label |
| https://www.ipcc.ch | (empty) | empty | Add link text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
https://www.ipcc.ch; https://www.ipcc.ch/report/srocc/; https://www.ipcc.ch/report/sr15/; https://www.ipcc.ch/report/srccl/; https://www.ipcc.ch/report/aviation-and-the-global-atmosphere-2/; https://www.ipcc.ch/report/methodology-report-on-short-lived-climate-forcers/; https://www.ipcc.ch/report/2027-ipcc-methodology-report-on-carbon-dioxide-rem…; https://www.ipcc.ch/report/ipcc-guidelines-for-national-greenhouse-gas-invent…; https://www.ipcc.ch/report/sixth-assessment-report-cycle/; https://www.ipcc.ch/report/sixth-assessment-report-working-group-ii/ (+79 more)
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Generic link text like 'click here' doesn't describe the destination.
https://www.ipcc.ch/2026/04/14/pr-ipcc-cdrt-mr-first-lead-author-meeting/ ("Read more"); https://www.ipcc.ch/2026/03/19/ipccs-sixty-fourth-plenary-in-bangkok-thailand/ ("Read more"); https://www.ipcc.ch/2025/11/19/calltficdrccus/ ("Read more"); https://www.ipcc.ch/2026/03/27/ipcc-64th-plenary-session/ ("Read more"); https://www.ipcc.ch/2026/04/14/pr-ipcc-cdrt-mr-first-lead-author-meeting/ ("Read more"); https://www.ipcc.ch/2026/03/19/ipccs-sixty-fourth-plenary-in-bangkok-thailand/ ("Read more"); https://www.ipcc.ch/2025/11/19/calltficdrccus/ ("Read more"); https://www.ipcc.ch/2026/03/27/ipcc-64th-plenary-session/ ("Read more"); https://www.ipcc.ch/2026/04/14/pr-ipcc-cdrt-mr-first-lead-author-meeting/ ("Read more"); https://www.ipcc.ch/about/engage_with_the_ipcc ("Learn More") (+1 more)
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
https://www.ipcc.ch/meeting-doc/ipcc-64/; https://www.ipcc.ch/about/vacancies/; https://www.ipcc.ch/site/assets/uploads/2019/02/UNGA43-53.pdf; https://facebook.com/IPCC; https://twitter.com/IPCC_ch; https://youtube.com/IPCCGeneva; https://instagram.com/IPCC; http://slideshare.com/IPCCGeneva; https://facebook.com/IPCC; https://twitter.com/IPCC_ch (+3 more)
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
button.search-submit (#1475 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
B404 Error PageHTTP 404, custom pageREVIEW
BFavicon & Branding7 icon(s) detectedREVIEW
BWeb ManifestValid manifestREVIEW
CLighthouse Accessibility AuditsActionScore 71/100 — 8 failing, 17 passedREVIEW
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Names and labels
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.overlay-content > form#header-search > div#search-btn > button.search-submit div.overlay-content > form#header-search > div#search-btn > button.search-submit |
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
div.section-container > div.section-content > div.section-block > img div.section-container > div.section-content > div.section-block > img |
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body#page-home > header#main-header > nav#nav-secondary > a#nav-overlay-trigger body#page-home > header#main-header > nav#nav-secondary > a#nav-overlay-trigger |
nav#nav-secondary > div#nav-tertiary > div#nav-secondary-search > a#search-trigger nav#nav-secondary > div#nav-tertiary > div#nav-secondary-search > a#search-trigger |
body#page-home > header#main-header > nav#nav-primary > a#nav-primary-logo body#page-home > header#main-header > nav#nav-primary > a#nav-primary-logo |
div.slide > div.block > div.block-content > a.block-link div.slide > div.block > div.block-content > a.block-link |
div.slide > div.block > div.block-content > a.block-link div.slide > div.block > div.block-content > a.block-link |
div.slide > div.block > div.block-content > a.block-link div.slide > div.block > div.block-content > a.block-link |
div.slide > div.block > div.block-content > a.block-link div.slide > div.block > div.block-content > a.block-link |
body#page-home > div#search-overlay > a#search-close body#page-home > div#search-overlay > a#search-close |
header#sticky-header > div#sticky-content > div.section-container > a#sticky-overlay-trigger header#sticky-header > div#sticky-content > div.section-container > a#sticky-overlay-trigger |
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ABOUT div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-169 > a |
DATA div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-12593 > a |
DOCUMENTATION div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-12754 > a |
DASHBOARD div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-657 > a |
BUREAU PORTAL div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-165 > a |
LIBRARY div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-25140 > a |
LINKS div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-841 > a |
HELP div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-36755 > a |
REPORTS div#nav-primary-menu > ul.menu > li > a#menu-link-reports |
SYNTHESIS REPORT div#nav-primary-menu > ul.menu > li > a#menu-link-synthesis-report |
WORKING GROUPS div#nav-primary-menu > ul.menu > li > a#menu-link-working-groups |
ACTIVITIES div#nav-primary-menu > ul.menu > li > a#menu-link-activities |
NEWS div#nav-primary-menu > ul.menu > li > a#menu-link-news |
CALENDAR div#nav-primary-menu > ul.menu > li > a#menu-link-calendar |
VACANCIES div.section-container > div.section-content > div.section-block > a.btn |
Follow the IPCC div.section-content > div#footer-engage-follow > div.section-block-text > h4 |
The Intergovernmental Panel on Climate Change (IPCC) is active socially – choos… div.section-content > div#footer-engage-follow > div.section-block-text > p |
Engage with the IPCC div.section-content > div#footer-engage-participate > div.section-block-text > h4 |
There are many ways to be involved and participate in the IPCC world. div.section-content > div#footer-engage-participate > div.section-block-text > p |
LEARN MORE div#footer-engage-participate > div.section-block-text > p > a.btn |
These are opportunities to improve the legibility of your content.
Navigation
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
The Intergovernmental Panel on Climate Change (IPCC) is the United Nations body… section#home-page-splash-1 > div.section-container > header.section-header > h3 |
FOLLOW div.section-container > aside.section-aside > div.aside-block > h5 |
MEETING div.post > div.preview-content > div.preview-text > h5 |
March 24, 2026 div.post > div.preview-content > div.preview-text > h6 |
March 3, 2026 div.post > div.preview-content > div.preview-text > h6 |
February 10, 2026 div.post > div.preview-content > div.preview-text > h6 |
January 27, 2026 div.post > div.preview-content > div.preview-text > h6 |
January 12, 2026 div.post > div.preview-content > div.preview-text > h6 |
December 1, 2025 div.post > div.preview-content > div.preview-text > h6 |
Synthesis Report div.slide > div.block > div.block-caption > h5 |
Working Group I div.post > div.preview-content > div.preview-text > h4 |
SEVENTH ASSESSMENT REPORT div.nav-reports-container > div.report-menu-column > div.report-menu-list > h5 |
These are opportunities to improve keyboard navigation in your application.
Internationalization and localization
If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These are opportunities to improve the interpretation of your content by users in different locales.
Best practices
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
ABOUT div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-169 > a |
DATA div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-12593 > a |
DOCUMENTATION div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-12754 > a |
DASHBOARD div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-657 > a |
BUREAU PORTAL div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-165 > a |
LIBRARY div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-25140 > a |
LINKS div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-841 > a |
HELP div.menu-secondary-navigation-container > ul#menu-secondary-navigation > li#menu-item-36755 > a |
COPYRIGHT div.menu-copyright-information-container > ul#menu-copyright-information > li#menu-item-37487 > a |
PRIVACY POLICY div.menu-copyright-information-container > ul#menu-copyright-information > li#menu-item-37491 > a |
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html html |
These items highlight common accessibility best practices.
AAlt Text Quality1 of 3 images have issuesPASS
| Issue | Count |
|---|---|
| missing | 1 image(s) |
Images without alt text are invisible to screen readers.
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
AForm Accessibility1 of 1 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #search | search | (Search by keyword) | placeholder only |
Placeholder text disappears on focus and is not a reliable label.
<input type="search" name="search" id="search">
Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.
Learn more ▾ ▴
Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).
Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Activities | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h2 Reports | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h2 Working Groups and T… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 The Intergovernmenta… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 Special Report | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 The Ocean and Cryosp… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 Global Warming of 1.… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 Climate Change and L… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 Aviation and the Glo… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 Methodology Report | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 2027 IPCC Methodolog… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 2027 IPCC Methodolog… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 1994 IPCC Guidelines… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 Sixth Assessment Rep… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 AR6 Synthesis Report… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 AR6 Climate Change 2… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 AR6 Climate Change 2… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 AR6 Climate Change 2… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 Special and Methodol… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
| h3 Special Report on Cl… | 6.37:1 | 3.0:1 | #000000 | #5492CD | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.