Skip to content
https://irishexaminer.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
D
Landmark Structure
Action
6 landmarks
FIX
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

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.

Why this matters

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.

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

F
Heading Hierarchy
Action
107 headings, 13 skip(s)
FIX
107 headings, 13 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Pfizer to cut more than 100 jobs at Ringaskiddy plant in Cork
  • H5 Legacy furniture superstore The Loft hits the market for €6m
  • H5 Man who tried to steal delivery van in Cork and punched driver is jailed
  • H5 Richard Hogan: My open letter to America — what a state you are in
  • H5 Funeral details announced for Scarlett Faulkner's brother Jason
  • H5 Ryanair to close airport check-in and bag-drop 20 minutes earlier
  • H5 John Kiely issues rallying call to Limerick supporters ahead of Cork clash
  • H5 Fun in foreign fields: 14 music festivals to tempt you overseas this summer
  • H5 Gardaí launch inquiry as Defence Forces officer accused of attacking woman with bottle at party
  • H2 News
  • H5 Conviction quashed for shooting range operator over bar without liquor licence skipped
  • H5 Department has no control over school book about tree that doesn't sustain Ireland's ecology
  • H5 By-elections will be referendum on a Government left with little wriggle room
  • H5 Motorist convicted of assaulting cyclist in 'classic road rage' incident in Cork City
  • H2 sport
  • H5 Erling Haaland sends Manchester City top with narrow win over relegated Burnley skipped
  • H5 Ulster U20FC semi-finals round-up: Tyrone and Monaghan to meet in decider
  • H5 Clare finish strong to snatch Munster U20HC victory over 14-man Tipperary
  • H5 Dominant Kerry cruise into Munster U20FC final with nineteen point win over Clare
  • H2 Insight: Must Reads
  • H5 'There was so much hype': Memories of when Michael Jackson came to Cork for two gigs in 1988 skipped
  • H5 Colman Noctor: Given the choice, I would choose life without ADHD
  • H5 From maternity leave to live tour: Doireann Garrihy on balancing motherhood and work
  • H5 Adi Roche on 40 years since Chornobyl disaster and how Cork was first to welcome the children
  • H2 Regular Columnists
  • H5 Sarah Harte: Religion and free speech are often uneasy bedfellows skipped
  • H5 S Fergus Finlay: On both sides of the Irish Sea, political leaders are in trouble
  • H5 Terry Prone: Victims of trolling should follow Dolly Parton’s lead and rise above it
  • H5 Gareth O'Callaghan: The voices you didn’t hear during the protests are the ones that matter most
  • H2 Lifestyle
  • H5 Tom Dunne: Naturally, it was a joy to talk songwriting with Gilbert O'Sullivan skipped
  • H5 Trinity graduate among authors shortlisted for Women’s Prize for Fiction
  • H5 Six supplements you can take to slow the signs of ageing
  • H5 Spa review: I drove from Cork to Belfast to see if this spa resort is as good as it looks on Instagram
  • H2 Viewpoints
  • H5 Contraception is free, but it's not reaching everyone who needs it skipped
  • H5 Seán Kelly: Viktor Orbán's loss is the EU's opportunity for a bold move on foreign policy
  • H5 TP O'Mahony: Link between religion and politics in the US is unique in the West
  • H5 Online abuse of politicians is a profitable business
  • H2 Subscriber
  • H5 S Hurling observations: Tipp v Cork endgame shows thin line between risk and reward skipped
  • H5 S Dalo's Hurling Show Extra: Eyes of the world on another Munster double bill
  • H5 S John Fallon: Grand home stages central to women’s legacy
  • H5 S Donal Lenihan: Munster can't seem to navigate their way out of the storm
  • H2 LISTEN NOW
  • H5 The Deirdre O'Shaugnessy Podcast: Everything you need to know about the Cork Luas skipped
  • H5 S The Gaelic Football Show: Westmeath earn local bragging rights, did Royals get ahead of themselves?
  • H5 S Dalo's Hurling Show: Cork and Clare get the max from their golden spells
  • H5 The Deirdre O'Shaugnessy Podcast: Why Ireland’s drink driving laws are facing renewed pressure
  • H2 Watch Now
  • H5 Watch: A new sculpture dedicated to the Chornobyl nuclear disaster installed at the Marina Park skipped
  • H5 Watch: Lelia Doolan finishes 220km protest walk to Dáil Éireann
  • H5 Watch: Rory McIlroy talks about the challenges of winning the Masters
  • H2 farming
  • H5 Tirlán sales up 10% as milk supply surges skipped
  • H5 Kiwi dairy farmers land €200,000 windfall after €2.7bn Fonterra payout
  • H5 From calving to clover: a busy spring on Kay's organic suckler farm
  • H5 €55m windblow scheme opens for storm-hit forest owners
  • H2 Property
  • H5 €420,000 Douglas walk-in is ideal for young couples skipped
  • H5 Inside RTÉ Home of the Year 2026 — and why it's pick of the bunch
  • H5 Home of the Year: See all 10 finalists in the running for the title
  • H5 The best nesting tables for both design purists and dupe-hunters
  • H2 World
  • H5 Chemical leak at West Virginia plant kills two people skipped
  • H5 EU plans to cut electricity taxes to shield households from Iran war energy crisis
  • H5 ieExplains: What are EU countries doing to counter energy price rises?
  • H5 Iran fires on three ships in Strait of Hormuz derailing US-Iran talks push
  • H2 Sponsored Content
  • H5 Get more heifers in-calf, earlier — with synchronisation and fixed time AI skipped
  • H5 The pension question most people never ask
  • H5 Tail-end calvers have an increased risk of ketosis
  • H5 The pension choices that could give you a €1.5 million boost
  • H2 Latest
  • H2 Most Read
  • H2 We value your privacy
  • H3 We and our partners collect and use data
  • H2 Your Privacy Preferences
  • H3 Manage your settings
  • H4 Strictly Necessary Cookies
  • H4 Functional Cookies
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H4 Social Media Cookies
  • H4 IAB Features 71 partners can use this purpose
  • H5 Match and combine data from other data sources 56 partners can use this feature
  • H5 Link different devices 55 partners can use this feature
  • H5 Identify devices based on information transmitted automatically 52 partners can use this feature
  • H4 IAB Special Purposes 73 partners can use this purpose
  • H5 Ensure security, prevent and detect fraud, and fix errors 57 partners can use this special purpose
  • H5 Deliver and present advertising and content 55 partners can use this special purpose
  • H5 Save and communicate privacy choices 54 partners can use this special purpose
  • H4 Store and/or access information on a device 76 partners can use this purpose
  • H4 Personalised advertising and content, advertising and content measurement, audience research and services development 82 partners can use this purpose
  • H5 Use limited data to select advertising 69 partners can use this purpose
  • H5 Create profiles for personalised advertising 67 partners can use this purpose
  • H5 Use profiles to select personalised advertising 66 partners can use this purpose
  • H5 Create profiles to personalise content 27 partners can use this purpose
  • H5 Use profiles to select personalised content 23 partners can use this purpose
  • H5 Measure advertising performance 78 partners can use this purpose
  • H5 Measure content performance 35 partners can use this purpose
  • H5 Understand audiences through statistics or combinations of data from different sources 58 partners can use this purpose
  • H5 Develop and improve services 72 partners can use this purpose
  • H5 Use limited data to select content 16 partners can use this purpose
  • H4 Use precise geolocation data 30 partners can use this special feature
  • H4 Actively scan device characteristics for identification 13 partners can use this special feature
  • H3 Vendors List

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

F
Alt Text Quality
Action
34 of 101 images have issues
FIX
34 of 101 images have issues
Critical::
31 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
1 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
3 image(s) with filename as alt text
Info::
1 image(s) with alt text over 125 characters
Info::
66 image(s) with good alt text
101 images 66 good alt text 3 generic 31 missing
IssueCount
missing31 image(s)
filename3 image(s)
too long1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: ie=edge,chrome=1
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModePartial Dark Mode
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
Info::
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
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
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 2 <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
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 Page Not Found - Irish Examiner ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA 4 pass AA only
title Irish Examiner
1.68:1
#000000
on
#273544
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Sign in
2.16:1
#000000
on
#3B4552
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Latest21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Most Read21.00:13.0:1
#000000
#FFFFFF
Pass
h2 We value your privac…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Your Privacy Prefere…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We and our partners …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Manage your settings21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Vendors List21.00:13.0:1
#000000
#FFFFFF
Pass
title Irish Examiner1.68:14.5:1
#000000
#273544
Fail
a Sign in2.16:14.5:1
#000000
#3B4552
Fail
a SUBSCRIBE5.24:14.5:1
#000000
#7F7F7F
Pass
p Try from €0.25 / d…5.24:14.5:1
#000000
#7F7F7F
Pass
a SUBSCRIBE5.24:14.5:1
#000000
#7F7F7F
Pass
p Try from €0.25 / d…5.24:14.5:1
#000000
#7F7F7F
Pass
i 12.81:14.5:1
#000000
#CACACA
Pass
i 21.00:14.5:1
#000000
#FFFFFF
Pass
strong Sign in21.00:13.0:1
#000000
#FFFFFF
Pass
strong Subscribe21.00:13.0:1
#000000
#FFFFFF
Pass
a Subscriber21.00:14.5:1
#000000
#FFFFFF
Pass
a news21.00:14.5:1
#000000
#FFFFFF
Pass
i 21.00:14.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.

C
Lighthouse Accessibility Audits
Action
Score 77/100 — 8 failing, 23 passed
REVIEW
77

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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-12 > div.d-flex > div.col-6 div.row > div.col-12 > div.d-flex > div.col-6
div.row > div.col-12 > div.d-flex > div.col-6 div.row > div.col-12 > div.d-flex > div.col-6

These are opportunities to improve the usage of ARIA in your application which 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.redesign-block-1 > h2 > span.headline-category-sport > a section.redesign-block-1 > h2 > span.headline-category-sport > a
WEEKLY CARTOON BY HARRY BURTON div.row > div.col-12 > p > strong
section.redesign-block-1 > h2 > span.headline-category-insight > a section.redesign-block-1 > h2 > span.headline-category-insight > a
section.redesign-block-1 > h2 > span.headline-category-lifestyle > a section.redesign-block-1 > h2 > span.headline-category-lifestyle > a
section.redesign-block-1 > h2 > span.headline-category-farming > a section.redesign-block-1 > h2 > span.headline-category-farming > a
div.col-right > div.sidebar-unit > div.most-read > h2.most-read_headline div.col-right > div.sidebar-unit > div.most-read > h2.most-read_headline

These are opportunities to improve the legibility of your content.

Names and labels

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-wrapper > div.col-left > a > img div.col-wrapper > div.col-left > a > img
div.carousel-item > div.row > div.col-12 > img.img-fluid div.carousel-item > div.row > div.col-12 > img.img-fluid
div.col-12 > div.d-flex > div.col-6 > img.img-fluid div.col-12 > div.d-flex > div.col-6 > img.img-fluid
div.col-12 > div.d-flex > div.col-6 > img.img-fluid div.col-12 > div.d-flex > div.col-6 > img.img-fluid

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-wrapper > div.col-right > div.sidebar-unit > iframe div.col-wrapper > div.col-right > div.sidebar-unit > iframe

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
div.container > div.col-wrapper > div.col-left > a div.container > div.col-wrapper > div.col-left > a

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.

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
Conviction quashed for shooting range operator over bar without liquor licence div.row > div.col-lg-7 > div.card-body > h5.card-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title
div.swiper-wrapper > section.col-25 > a > h5.columnist-title div.swiper-wrapper > section.col-25 > a > h5.columnist-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title
Watch: A new sculpture dedicated to the Chornobyl nuclear disaster installed at… article.video-big-card > a > div > h5.top-main-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title
div.row > div.col-lg-7 > div.card-body > h5.card-title div.row > div.col-lg-7 > div.card-body > h5.card-title

These are opportunities to improve keyboard navigation in your application.

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.redesign-block-1 > h2 > span.headline-category-opinion-columnists > a section.redesign-block-1 > h2 > span.headline-category-opinion-columnists > a
ieExplains: What are EU countries doing to counter energy price rises? div.row > div.col-md-4 > article#article-card-41831798 > a
Iran War div.row > div.col-md-4 > article#article-card-41831801 > a

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●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
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○ARIA IDs are unique
○No form fields have multiple labels
○`<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
○Form elements have associated labels
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○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.
A+
Form Accessibility
All 24 controls labeled
PASS
All 24 controls labeled
Info::
24 control(s) properly labeled
24 controls
24 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
cosearchtextInput phrasearia-label
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0005checkboxSocial Media Cookiesfor/id
#ot-group-id-IAB2V2_1checkboxStore and/or access information on a devicefor/id
#ot-group-id-V2STACK42checkboxPersonalised advertising and content, advertising and content measurement, audience research and services developmentfor/id
#ot-sub-group-id-IAB2V2_2checkboxUse limited data to select advertisingaria-label
#ot-sub-group-id-IAB2V2_3checkboxCreate profiles for personalised advertisingaria-label
#ot-sub-group-id-IAB2V2_4checkboxUse profiles to select personalised advertisingaria-label
#ot-sub-group-id-IAB2V2_5checkboxCreate profiles to personalise contentaria-label
#ot-sub-group-id-IAB2V2_6checkboxUse profiles to select personalised contentaria-label
#ot-sub-group-id-IAB2V2_7checkboxMeasure advertising performancearia-label
#ot-sub-group-id-IAB2V2_8checkboxMeasure content performancearia-label
#ot-sub-group-id-IAB2V2_9checkboxUnderstand audiences through statistics or combinations of data from different sourcesaria-label
#ot-sub-group-id-IAB2V2_10checkboxDevelop and improve servicesaria-label
#ot-sub-group-id-IAB2V2_11checkboxUse limited data to select contentaria-label
#ot-group-id-ISF2V2_1checkboxUse precise geolocation datafor/id
#ot-group-id-ISF2V2_2checkboxActively scan device characteristics for identificationfor/id
#vendor-search-handlertextVendor list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
A
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Irish Examiner
Info::
192x192 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Irish Examiner ✓192×192 icon ✓512×512 icon ✗Start URL https://www.irishexaminer.com/ ✓Display Mode standalone ✓
Name Irish Examiner Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback