Skip to content
https://rferl.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
4
REVIEW
3
PASS
6
INFO
0
Checks
13
6 PASS 3 REVIEW 4 FIX
F
Heading Hierarchy
Action
59 headings, 6 skip(s)
FIX
59 headings, 6 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 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Accessibility links
  • H5 Follow Us skipped
  • H4 Trump Extends Cease-Fire Amid Uncertainty Over Iran's Position; Blockade To Remain
  • H4 LIVE Qalibaf Spokesman Calls Cease-Fire Extension 'Ploy To Buy Time'
  • H4 Rachel Ehrenfeld: Why Targeting Iran's 'Shadow Economy' Hits The IRGC Where It Hurts
  • H4 Internet Shutdown Adds To The Costs Of War For Iranians
  • H4 Iran Parades Pink Weapons To Coerce Women Into Militancy, Says Rights Expert
  • H4 Hormuz Crisis Has Supercharged The Middle Corridor Trade Route
  • H4 Entangled In Russia's Faltering Economy: The Fate Of Its Respected Central Banker
  • H4 In Donetsk, Ukrainian Drone Pilots Target Russians On Horseback
  • H5 Faces behind the numbers: PEOPLE KILLED IN IRAN'S PROTESTS
  • H2 Washington On Iran
  • H4 US Lawmaker Wilson Flags Western Chips Still Flowing Into Russian, Iranian Drones skipped
  • H4 Azeem Ibrahim: Iran Conflict Will Be Decided By Who Can 'Endure The Most'
  • H2 Don't Miss
  • H4 Funding Feud Over Russia's Return To The Venice Biennale skipped
  • H4 Germany Tells Russia Threats Are 'Unacceptable' After Arms Makers List Published
  • H4 US Lawmakers Move To Target Chinese, Russian Influence In Georgia
  • H4 Ukrainian Drones Hit Russian Black Sea Oil Hub For Second Time In 4 Days
  • H4 'Is He Alive?': Searching For Ukrainian Children Taken By Russia
  • H4 Thomas De Waal: Iran War Could Complicate Trump's Caucasus Corridor Plan
  • H4 Ukrainian Drone Hunter Units Keep Busy In Donetsk Day And Night
  • H4 Life Of Jailed Iranian Nobel Peace Prize Winner Narges Mohammadi 'In Serious Danger'
  • H4 Ryan Kirkley: From Oil To Bitcoin, Markets Shift With Strait Of Hormuz News
  • H4 The 'Decommunization' Of Dushanbe
  • H4 What Is HAYI, The Shadowy Islamist Group Claiming Attacks Across Europe?
  • H4 Journalist In Kyiv Escapes Deadly Air Strike On Apartment Building
  • H2 Visuals
  • H4 Why Is Iran Parading Pink Weapons? To Coerce Women Into Militancy, Says Rights Expert skipped
  • H4 Ukrainian Drones Hit Russian Black Sea Oil Hub For Second Time In 4 Days
  • H4 'Is He Alive?': Searching For Ukrainian Children Taken By Russia
  • H4 Shooter Kills Six In Daylight Incident In Kyiv
  • H4 Ukrainian Drone Hunter Units Keep Busy In Donetsk Day And Night
  • H4 Journalist In Kyiv Escapes Deadly Air Strike On Apartment Building
  • H4 Russia Hits Ukraine Overnight With Deadly Drone And Missile Attack
  • H4 Chernobyl Dust Leak Would Be 'Catastrophic,' Warns Greenpeace Ahead Of Disaster Anniversary
  • H4 Hundreds Of Russian Drones Target Ukraine In Overnight Strikes
  • H4 Iranians Express Relief, Concern Amid Fragile Truce
  • H4 Touting US Oil Reserves, Trump Says 'We Don't Need The Strait' As Blockade Begins
  • H4 Amid Fragile Truce, One Tehran Resident Tries To Find 'Hope For Tomorrow'
  • H4 Ukraine Observes Easter As Short Truce With Russia Fails To Hold
  • H4 Veterans Of 1980s 'Tanker War' See Parallels In Current Hormuz Crisis
  • H4 Thousands Evacuated After Dam Bursts In Russia's Daghestan Region
  • H4 The Route That Could Change Asian Energy Flows
  • H4 Strikes Hit Tehran As US Deadline To Target Power Plants Nears
  • H4 Alleged Pipeline Sabotage Attempt In Serbia Provokes Accusations Across Borders
  • H4 In Photos: Week Five Of The Iran War
  • H2 Sign Up For Our Newsletters
  • H4 Wider Europe Briefing: The EU's First-Ever Armenia Summit skipped
  • H4 Wider Europe Briefing: What Now For NATO?
  • H4 Wider Europe Briefing: The EU's First-Ever Armenia Summit
  • H4 Wider Europe Briefing: What Now For NATO?
  • H2 Most Popular
  • H4 Czechs Demand Explanation After Russia's Medvedev Threatens Europe's Drone Factories skipped
  • H4 Germany Tells Russia Threats Are 'Unacceptable' After Arms Makers List Published
  • H4 Qalibaf Spokesman Calls Cease-Fire Extension 'Ploy To Buy Time'
  • H4 Iran Sentences Four More To Death Over Mass Protests, Rights Groups Say
  • H4 Azeem Ibrahim: Iran Conflict Will Be Decided By Who Can 'Endure The Most'
  • H2 Follow Us

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

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
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 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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN (missing!) ASIDE 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

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 17 passed
REVIEW
86

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.

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
More News div#wrowblock-60683_52 > div#wrowblock-60683_54 > div#wrowblock-60683_56 > a.link-more
More div#wrowblock-59682_10 > div#wrowblock-59682_11 > div#wrowblock-59682_12 > a.link-more
More div#wrowblock-61378_10 > div#wrowblock-61378_11 > div#wrowblock-61378_12 > a.link-more
WIDER EUROPE div.carousel__inner > div.media-block > div.media-block__content > a.category

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
FOLLOW US div.menu-pnl > div.menu-pnl__inner > div.menu-pnl__item > h5.menu-pnl__sub-head
US Lawmaker Wilson Flags Western Chips Still Flowing Into Russian, Iranian Dron… div.media-block > div.media-block__content > a > h4.media-block__title
Funding Feud Over Russia's Return To The Venice Biennale div.media-block > div.media-block__content > a > h4.media-block__title
Why Is Iran Parading Pink Weapons? To Coerce Women Into Militancy, Says Rights … div.media-block > div.media-block__content > a > h4.media-block__title
Wider Europe Briefing: The EU's First-Ever Armenia Summit div.media-block > div.media-block__content > a > h4.media-block__title
Czechs Demand Explanation After Russia's Medvedev Threatens Europe's Drone Fact… div.row > a.col-xs-12 > span.trends-wg__item-inner > h4.trends-wg__item-txt

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
More News div#wrowblock-60683_52 > div#wrowblock-60683_54 > div#wrowblock-60683_56 > a.link-more
More div#wrowblock-59682_10 > div#wrowblock-59682_11 > div#wrowblock-59682_12 > a.link-more
More div#wrowblock-61378_10 > div#wrowblock-61378_11 > div#wrowblock-61378_12 > a.link-more

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.js html.js

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[accesskey]` values are unique
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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
Alt Text Quality
All 39 images OK
PASS
All 39 images OK
Info::
8 image(s) with alt text over 125 characters
Info::
31 image(s) with good alt text
39 images 31 good alt text
IssueCount
too long8 image(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#txtHeaderSearchtextSearchfor/id
#txtSearchsearchSearchfor/id
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page doesn't exist ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Favicon & Branding
15 icon(s) detected
PASS
15 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Radio Free Europe/Radio Liberty
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Radio Free Europe/Radio Liberty ✓192×192 icon ✓512×512 icon ✓Start URL https://www.rferl.org/?utm_medium=app&utm_campaign=prog-app&utm_source=rferl-english&utm_content=english ✓Display Mode standalone ✓
Name Radio Free Europe/Radio Liberty Display Mode standalone Theme Color #FA5420 Background Color #FFFFFF Icons 6 icon(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Accessibility links21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Sign Up For Our News…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Most Popular21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Follow Us21.00:13.0:1
#000000
#FFFFFF
Pass
title Radio Free Europe/Ra…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main content21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to main Navigat…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to Search21.00:14.5:1
#000000
#FFFFFF
Pass
div Link has been copied…21.00:14.5:1
#000000
#FFFFFF
Pass
span MORE21.00:14.5:1
#000000
#FFFFFF
Pass
a To Readers In Russia21.00:14.5:1
#000000
#FFFFFF
Pass
label Russia21.00:14.5:1
#000000
#FFFFFF
Pass
a Russia21.00:14.5:1
#000000
#FFFFFF
Pass
a Tatar-Bashkir21.00:14.5:1
#000000
#FFFFFF
Pass
a North Caucasus21.00:14.5:1
#000000
#FFFFFF
Pass
a Iran21.00:14.5:1
#000000
#FFFFFF
Pass
label Central Asia21.00:14.5:1
#000000
#FFFFFF
Pass
a Kazakhstan21.00:14.5:1
#000000
#FFFFFF
Pass
a Kyrgyzstan21.00:14.5:1
#000000
#FFFFFF
Pass
a Tajikistan21.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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback