Accessibility

F

Heading Hierarchy

Action

102 headings, 21 skip(s)

FIX

102 headings, 21 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H3 → H6 (missing H4)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 Home
H4 What we do. skipped
H6 Broking and Risk Transfer skipped
H6 Claims Management
H6 Reinsurance
H6 Risk Analytics
H6 Risk Management
H6 Risk Retention
H6 Health and Benefits
H6 Human Capital Analytics
H6 Investments
H6 Pensions and Retirement
H6 Talent and Rewards
H6 Workplace Wellbeing
H4 Insights and advice, tailored to your needs.
H6 Construction and Real Estate skipped
H6 Financial Institutions
H6 Financial Sponsors
H6 Food, Agribusiness and Beverage
H6 Healthcare Providers and Services
H6 Hospitality, Travel and Leisure
H6 Industrials and Manufacturing
H6 Insurance
H6 Life Sciences
H6 Natural Resources
H6 Professional and Business Services
H6 Public Sector
H6 Retail and Consumer Goods
H6 Sports and Entertainment
H6 Technology, Media and Communications
H6 Transportation and Logistics
H4 Discover new insights from Aon.
H6 Trade skipped
H6 Technology
H6 Weather
H6 Workforce
H4 Aon is in the business of better decisions.
H6 Our Story skipped
H6 Our Values
H6 Our Impact
H6 Engagement and Wellbeing
H6 Leadership and Governance
H6 Risk Capital
H6 Human Capital
H6 How can we help you?
H6 Popular Searches
H6 Top Insights
H6 Report
H6 Report
H6 (empty)
H2 Aon is in the Business of Better Decisions
H6 Trade skipped
H2 Turning Risk into Resilience
H6 Turning Risk into Resilience skipped
H6 Technology
H2 Finding Security in New Opportunities
H6 Finding Security in New Opportunities skipped
H6 Weather
H2 Unlock Capital to Protect People and Property
H6 Unlock Capital to Protect People and Property skipped
H6 Workforce
H2 Realize the Full Potential of Your People
H6 Realize the Full Potential of Your People skipped
H3 Expertise Across Today's Risk and People Issues
H4 Risk Capital
H6 Making Better Risk Decisions skipped
H4 Human Capital
H6 Making Better People Decisions skipped
H3 Featured Insights
H6 Client Trends 2025 skipped
H6 5 Top Trends for Risk Capital in 2025
H6 5 Human Resources Trends to Watch in 2025
H3 Keep Exploring
H4 Industry Experience Matters
H6 Tailored advice for you skipped
H3 Aon is in the Business of Better Decisions
H4 Talk to Our Team
H2 Subscribe to Aon
H6 About You skipped
H4 Subscribe
H2 Thank You
H3 What Comes Next?
H6 Featured Insights skipped
H6 How Data and Analytics Can Optimize HR Programs
H4 Thank You
H2 Let’s Connect
H6 I’m interested in skipped
H3 Talking to Aon
H6 About You skipped
H6 About Your Business
H6 How Can We Help?
H4 Let’s Connect
H2 Thank You
H3 We’ll be in touch soon.
H6 Featured Insights skipped
H6 How Data and Analytics Can Optimize HR Programs
H4 Thank You
H2 Thank You for Your Interest!
H4 Access Content skipped
H2 Thank You for Your Interest!
H4 Your file is downloading. skipped
H4 Access Content

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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.

Why this matters

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F

Form Accessibility

Action

20 of 35 controls have issues

FIX

20 of 35 controls have issues

18 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <select id="vjs_select_652">; <select id="vjs_select_671">; <select id="vjs_select_686">; <input type="text" name="firstname">; <input type="text" name="lastname">; <input type="email" name="Email">; <input type="text" name="firstName">; <input type="text" name="lastName">; <input name="title" id="jobtitle">; <input type="email" name="emailAddress"> (+8 more)

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">; <textarea name="comments">

15 control(s) properly labeled

35 controls

15 labeled

2 placeholder only

18 unlabeled

Control	Type	Label	Method
#vjs_select_602	select	Color	for/id
#vjs_select_607	select	Opacity	for/id
#vjs_select_617	select	Color	for/id
#vjs_select_622	select	Opacity	for/id
#vjs_select_632	select	Color	for/id
#vjs_select_637	select	Opacity	for/id
#footer-subscribe-email	email	Email Address:	for/id
#location	select	Location *	for/id
#country	select	Location *	for/id
#countryCode	select	Country Code*	for/id
#industry	select	Employee Headcount *	for/id
#title	text	Job Title *	for/id
#emailAddress	email	Business Email Address: *	for/id
contact_me	checkbox		none
subscribe	checkbox		none
input	text	(Search)	placeholder only
comments	textarea	(Add a message)	placeholder only
#jobtitle	input	(none)	none
emailAddress	email	(none)	none
#vjs_select_686	select	(none)	none
#vjs_select_652	select	(none)	none
busPhone	tel	(none)	none
company	text	(none)	none
firstname	text	(none)	none
#revenue	select	(none)	none
#headcount	select	(none)	none
lastname	text	(none)	none
firstName	text	(none)	none
lastName	text	(none)	none
Email	email	(none)	none
#vjs_select_671	select	(none)	none
country	select	(none)	none
company	text	(none)	none
firstName	text	(none)	none
lastName	text	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<select id="vjs_select_652">; <select id="vjs_select_671">; <select id="vjs_select_686">; <input type="text" name="firstname">; <input type="text" name="lastname">; <input type="email" name="Email">; <input type="text" name="firstName">; <input type="text" name="lastName">; <input name="title" id="jobtitle">; <input type="email" name="emailAddress"> (+8 more)

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

Placeholder text disappears on focus and is not a reliable label.

Why this matters

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

F

Link & Button Quality

Action

14 issue(s) across 136 links and 46 buttons

FIX

14 issue(s) across 136 links and 46 buttons

6 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /en/; /en/insights/client-trends; /en/insights/articles/5-top-trends-risk-capital-2025; /en/insights/articles/five-human-resources-trends-to-watch-in-2025; /en/; /en/

8 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /en/about ("Learn More"); /en/insights/trade ("Learn More"); /en/insights/technology ("Learn More"); /en/insights/weather ("Learn More"); /en/insights/workforce ("Learn More"); /en/about/risk-capital ("Learn More"); /en/about/human-capital ("Learn More"); https://mypreferences.aon.com/ ("click here")

25 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://aon.mediaroom.com; /en/insights/articles/reputational-resilience-in-oil-and-gas-protecting-value; /en/insights/articles/reputational-resilience-in-oil-and-gas-protecting-value; /en/insights/articles/beyond-traditional-markets-unlocking-alternative-risk-c…; /en/insights/articles/beyond-traditional-markets-unlocking-alternative-risk-c…; /en/insights/articles/building-tomorrows-grid-managing-extreme-heat-risk-in-a…; /en/insights/articles/building-tomorrows-grid-managing-extreme-heat-risk-in-a…; /en/insights/articles/geopolitical-risks-reshaping-north-american-energy; /en/insights/articles/geopolitical-risks-reshaping-north-american-energy; /en/insights/articles/when-an-employee-benefits-captive-is-the-right-solution (+15 more)

97 link(s) with descriptive text

136 links

6 empty

8 generic text

25 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/en/	(empty)	empty	Add link text or aria-label
https://aon.mediaroom.com	News	new tab	Add '(opens in new tab)' to text
/en/about	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: About
/en/insights/trade	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Trade
/en/insights/technology	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Technology
/en/insights/weather	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Weather
/en/insights/workforce	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Workforce
/en/about/risk-capital	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Risk Capital
/en/about/human-capital	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Human Capital
/en/insights/client-trends	(empty)	empty	Add link text or aria-label
/en/insights/articles/5-top-trends-risk-…	(empty)	empty	Add link text or aria-label
/en/insights/articles/five-human-resourc…	(empty)	empty	Add link text or aria-label
/en/insights/articles/reputational-resil…	Reputational Resilience in Oil…	new tab	Add '(opens in new tab)' to text
/en/insights/articles/reputational-resil…	Reputation as a Value Driver: …	new tab	Add '(opens in new tab)' to text
/en/insights/articles/beyond-traditional…	Beyond Traditional Markets: Un…	new tab	Add '(opens in new tab)' to text
/en/insights/articles/beyond-traditional…	Beyond Traditional Markets: Un…	new tab	Add '(opens in new tab)' to text
/en/insights/articles/building-tomorrows…	Building Tomorrow’s Grid: Ma…	new tab	Add '(opens in new tab)' to text
/en/insights/articles/building-tomorrows…	Building Tomorrow’s Grid: Ma…	new tab	Add '(opens in new tab)' to text
/en/insights/articles/geopolitical-risks…	Geopolitical Risks Reshaping N…	new tab	Add '(opens in new tab)' to text
/en/insights/articles/geopolitical-risks…	Converging Geopolitical and En…	new tab	Add '(opens in new tab)' to text
/en/insights/articles/when-an-employee-b…	When an Employee Benefits Capt…	new tab	Add '(opens in new tab)' to text
/en/insights/articles/when-an-employee-b…	When an Employee Benefits Capt…	new tab	Add '(opens in new tab)' to text
/en/insights/articles/how-axa-xl-transfo…	How AXA XL Transformed into a …	new tab	Add '(opens in new tab)' to text
/en/insights/articles/how-axa-xl-transfo…	How AXA XL Transformed into a …	new tab	Add '(opens in new tab)' to text
/en/	(empty)	empty	Add link text or aria-label
/en/	(empty)	empty	Add link text or aria-label
https://jobs.aon.com/	Careers	new tab	Add '(opens in new tab)' to text
https://ir.aon.com/	Investors	new tab	Add '(opens in new tab)' to text
https://aon.mediaroom.com	News	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/Aonplc/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/aon	Linked In	new tab	Add '(opens in new tab)' to text
https://twitter.com/aon_plc	Twitter	new tab	Add '(opens in new tab)' to text
/en/about/leadership-and-governance/priv…	Aon's global privacy statemen…	new tab	Add '(opens in new tab)' to text
/en/about/leadership-and-governance/priv…	Aon's global privacy statement	new tab	Add '(opens in new tab)' to text
/en/about/leadership-and-governance/priv…	Aon's global privacy statement	new tab	Add '(opens in new tab)' to text
https://mypreferences.aon.com/	click here	generic text	Replace with descriptive text
Before: click here Suggested: Home page
https://policies.google.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://policies.google.com/terms	Terms of Service	new tab	Add '(opens in new tab)' to text
	Access Content	new tab	Add '(opens in new tab)' to text

143 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/en/; /en/insights/client-trends; /en/insights/articles/5-top-trends-risk-capital-2025; /en/insights/articles/five-human-resources-trends-to-watch-in-2025; /en/; /en/

Why this matters

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.

/en/about ("Learn More"); /en/insights/trade ("Learn More"); /en/insights/technology ("Learn More"); /en/insights/weather ("Learn More"); /en/insights/workforce ("Learn More"); /en/about/risk-capital ("Learn More"); /en/about/human-capital ("Learn More"); https://mypreferences.aon.com/ ("click here")

Why this matters

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://aon.mediaroom.com; /en/insights/articles/reputational-resilience-in-oil-and-gas-protecting-value; /en/insights/articles/reputational-resilience-in-oil-and-gas-protecting-value; /en/insights/articles/beyond-traditional-markets-unlocking-alternative-risk-c…; /en/insights/articles/beyond-traditional-markets-unlocking-alternative-risk-c…; /en/insights/articles/building-tomorrows-grid-managing-extreme-heat-risk-in-a…; /en/insights/articles/building-tomorrows-grid-managing-extreme-heat-risk-in-a…; /en/insights/articles/geopolitical-risks-reshaping-north-american-energy; /en/insights/articles/geopolitical-risks-reshaping-north-american-energy; /en/insights/articles/when-an-employee-benefits-captive-is-the-right-solution (+15 more)

Why this matters

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

F

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

D

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModeNo Dark Mode Detected

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Search

Skip Link

Labeled Navigation 1 <nav> element(s)

Back to Top

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

B

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

2 pass 18 fail WCAG AA

h2 Aon is in the Business of Better Decisio…

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Turning Risk into Resilience

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Finding Security in New Opportunities

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Unlock Capital to Protect People and Pro…

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Realize the Full Potential of Your Peopl…

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Subscribe to Aon

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Thank You

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Let’s Connect

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Thank You

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Thank You for Your Interest!

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Thank You for Your Interest!

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Expertise Across Today's Risk and People…

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Featured Insights

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keep Exploring

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Aon is in the Business of Better Decisio…

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 What Comes Next?

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Talking to Aon

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We’ll be in touch soon.

1.62:1

#000000

on

#2C313E

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Home	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Aon is in the Busine…	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Turning Risk into Re…	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Finding Security in …	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Unlock Capital to Pr…	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Realize the Full Pot…	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Subscribe to Aon	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Thank You	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Let’s Connect	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Thank You	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Thank You for Your I…	1.62:1	3.0:1	#000000	#2C313E	Fail
h2 Thank You for Your I…	1.62:1	3.0:1	#000000	#2C313E	Fail
h3 Expertise Across Tod…	1.62:1	3.0:1	#000000	#2C313E	Fail
h3 Featured Insights	1.62:1	3.0:1	#000000	#2C313E	Fail
h3 Keep Exploring	1.62:1	3.0:1	#000000	#2C313E	Fail
h3 Aon is in the Busine…	1.62:1	3.0:1	#000000	#2C313E	Fail
h3 What Comes Next?	1.62:1	3.0:1	#000000	#2C313E	Fail
h3 Talking to Aon	1.62:1	3.0:1	#000000	#2C313E	Fail
h3 We’ll be in touch …	1.62:1	3.0:1	#000000	#2C313E	Fail
title Better Decisions \| A…	21.00:1	4.5:1	#000000	#FFFFFF	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.

A

Landmark Structure

15 landmarks

PASS

15 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

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

A

Alt Text Quality

2 of 29 images have issues

PASS

2 of 29 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with generic alt text

2 decorative image(s) correctly marked

25 image(s) with good alt text

29 images 25 good alt text 2 decorative 1 generic 1 missing

Issue	Count
missing	1 image(s)
generic	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

A

Lighthouse Accessibility Audits

Score 91/100 — 3 failing, 30 passed

PASS

91

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.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Turning Risk into Resilience `section.aon-homepage-hero__section > div.aon-homepage-hero__content-wrapper > div.aon-homepage-hero__content > h6.title`
Making Better Risk Decisions `main.page-main > div.grid > div.text-media-content > h6.text-media__sub-title`
Making Better People Decisions `main.page-main > div.grid > div.text-media-content > h6.text-media__sub-title`
Client Trends 2025 `li.super-component__item > article.content-card > a.content-card__title > h6`
Tailored advice for you `div.featured-content__card > div.featured-content__information > div.featured-content__subtitle > h6.regular`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
View All Industries `div.aon-component > div.featured-content__card > div.featured-content__button > a.aon-button`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●ARIA attributes are used as specified for the element's role

●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

●ARIA IDs are unique

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●All heading elements contain content.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○No form fields have multiple labels

○`<frame>` or `<iframe>` elements have a title

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○Tables have different content in the summary attribute and `<caption>`.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.