Skip to content
https://flagcounter.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
42
GRADE
F
FIX
10
REVIEW
2
PASS
1
INFO
0
Checks
13
1 PASS 2 REVIEW 10 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

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

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
Alt Text Quality
Action
14 of 15 images have issues
FIX
14 of 15 images have issues
Critical::
14 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with good alt text
15 images 1 good alt text 14 missing
IssueCount
missing14 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
Form Accessibility
Action
15 of 25 controls have issues
FIX
15 of 25 controls have issues
Critical::
14 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select name="flags_from" id="flags_from">; <select name="max" id="max">; <select name="size" id="size">; <select name="flags" id="flags">; <select name="columns" id="columns">; <select name="viewers" id="viewers">; <input type="text" name="customlabel" id="customlabelinput">; <input type="text" name="bg" id="bg">; <input type="text" name="text" id="text">; <input type="text" name="border" id="border"> (+4 more)
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="useremail" id="useremail">
Info::
10 control(s) properly labeled
25 controls
10 labeled
1 placeholder only
14 unlabeled
ControlTypeLabelMethod
#topcountriesradionone
#flagmapradionone
#usflagsradionone
#miniradionone
#recentradionone
#flagsxlcheckboxUse Large Flagsfor/id
#labelscheckboxShow Flag Labelsfor/id
#pageviewscheckboxShow Pageview Countfor/id
#percentselectShow Visitors Asfor/id
#flag_numcheckboxShow Number of Flagsfor/id
#useremailtext(optional)placeholder only
#customlabelinputtext(none)none
#bgtext(none)none
#texttext(none)none
#bordertext(none)none
#flags_fromselect(none)none
#maxselect(none)none
#sizeselect(none)none
#flagsselect(none)none
#columnsselect(none)none
#newsizeselect(none)none
#viewersselect(none)none
#g-recaptcha-responsetextarea(none)none
inputsubmit(none)none
inputsubmit(none)none

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

<select name="flags_from" id="flags_from">; <select name="max" id="max">; <select name="size" id="size">; <select name="flags" id="flags">; <select name="columns" id="columns">; <select name="viewers" id="viewers">; <input type="text" name="customlabel" id="customlabelinput">; <input type="text" name="bg" id="bg">; <input type="text" name="text" id="text">; <input type="text" name="border" id="border"> (+4 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.

<input type="text" name="useremail" id="useremail">

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
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404 Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
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
Info::
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
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
No navigation patterns
FIX
No navigation patterns
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
F
Lighthouse Accessibility Audits
Action
Score 47/100 — 7 failing, 7 passed
FIX
47

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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.double-column > div.shortcolumn > p > img div.double-column > div.shortcolumn > p > img
h3 > font > a > img h3 > font > a > img
div.right > div.get-counter > a.thickbox > img div.right > div.get-counter > a.thickbox > img

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form#counterform > div.left-wide > div#bgcolor > input#bg form#counterform > div.left-wide > div#bgcolor > input#bg
div.customization > form#counterform > div.left-wide > input#text div.customization > form#counterform > div.left-wide > input#text
div.customization > form#counterform > div.left-wide > input#border div.customization > form#counterform > div.left-wide > input#border

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 3… form#counterform > div.left > div#maxflags > select#max
1 2 3 4 5 6 7 8 form#counterform > div.left > div#columnsflags > select#columns
none Visitors » custom form#counterform > div.left > div#counterlabel > select#viewers
Small Medium Large form#counterform > div.right > div#flagsize > select#newsize

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
body > div.shell > a body > div.shell > a
form#counterform > div.right > div.get-counter > a.thickbox form#counterform > div.right > div.get-counter > a.thickbox

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

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 choices» form#counterform > div > span#morechoiceslink > a

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 html

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>`
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●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
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[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
○`[role]` values are valid
○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
○Buttons have an accessible name
○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 a valid value for its `[lang]` attribute
○`<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">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○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
○`<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
○Image elements do not have `[alt]` attributes that are redundant text.
○Identical links have the same purpose.
○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.
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 1 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Flag Counter!16.03:13.0:1
#000000
#E0E1E1
Pass
h2 Testimonial21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Instantly Create You…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Customize your count…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Preview your selecti…3.77:13.0:1
#000000
#266BAA
Pass
title Flag Counter - Free …11.52:14.5:1
#000000
#A8C3DD
Pass
a Flag Counter20.62:14.5:1
#000000
#FCFDFE
Pass
a Contact19.62:14.5:1
#000000
#F2F8FD
Pass
a Country List17.94:14.5:1
#000000
#EDEDED
Pass
a FAQ21.00:14.5:1
#000000
#FFFFFF
Pass
a Forum21.00:14.5:1
#000000
#FFFFFF
Pass
span Welcome to19.95:14.5:1
#000000
#F9F9F9
Pass
p Add our20.12:14.5:1
#000000
#FAFAFA
Pass
b free counter21.00:13.0:1
#000000
#FFFFFF
Pass
p to any webpage and c…21.00:14.5:1
#000000
#FFFFFF
Pass
p "...I check my homep…21.00:14.5:1
#000000
#FFFFFF
Pass
span - Bob H.21.00:14.5:1
#000000
#FFFFFF
Pass
p - West Virginia21.00:14.5:1
#000000
#FFFFFF
Pass
span When you're finished…21.00:14.5:1
#000000
#FFFFFF
Pass
u Reset21.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.

A
Heading Hierarchy
7 headings
PASS
7 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 Flag Counter
  • H2 Welcome to Flag Counter!
  • H2 Testimonial
  • H2 Instantly Create Your Free Counter
  • H3 Customize your counter here. When you're finished, click the orange button. | Reset
  • H3 Preview your selections on our sample Flag Counter:
  • H1 Flag Counter duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Send Feedback