Skip to content
https://fsc.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
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::
7 navigation landmark(s) detected
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 7 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Info::
7 <nav> landmark(s) found
Warning::
1 of 7 <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 "block-mainnavigation-menu" MAIN CONTENTINFO footer

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

B
Heading Hierarchy
30 headings, 1 skip(s)
REVIEW
30 headings, 1 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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 Main navigation
  • H2 Mobile navigation
  • H2 In search of inspiration?
  • H4 Pagination skipped
  • H4 Pagination
  • H4 Pagination
  • H4 Pagination
  • H2 Strengthening trust across forest supply chains
  • H2 We set the global standard for responsible forest management
  • H2 FSC Certification
  • H2 Trusted worldwide
  • H2 Strengthening trust across forest supply chains
  • H2 We set the global standard for responsible forest management
  • H2 FSC works with different groups to protect forests
  • H3 Business
  • H3 Forest Managers
  • H3 Consumers
  • H3 NGOs
  • H2 Our Global Impact
  • H2 How FSC works in practice
  • H2 Working together for forests
  • H2 Yolanda Ramirez
  • H2 Ava Spoden
  • H2 Arushi Sen
  • H2 FSC standards in action
  • H1 The last candelilleros
  • H1 Safeguarding Romania’s forests duplicate H1
  • H1 From the heart of the Amazon duplicate H1
  • H2 Already part of the FSC system?
  • H2 Become a forest steward

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

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

C
Alt Text Quality
Action
31 of 122 images have issues
REVIEW
31 of 122 images have issues
Warning::
11 image(s) with filename as alt text
Warning::
20 image(s) with generic alt text
Info::
9 decorative image(s) correctly marked
Info::
82 image(s) with good alt text
122 images 82 good alt text 9 decorative 31 generic
IssueCount
filename11 image(s)
generic20 image(s)
C
Form Accessibility
Action
6 of 10 controls have issues
REVIEW
6 of 10 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" name="op" id="edit-submit">
Warning::
5 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="search" id="fsc-search-input">; <input type="text" name="search" id="edit-search">; <input type="text" name="search" id="edit-search--2">; <input type="text" name="search" id="edit-search--3">; <input type="text" name="search" id="edit-search--2">
Info::
4 control(s) properly labeled
10 controls
4 labeled
5 placeholder only
1 unlabeled
ControlTypeLabelMethod
#edit-submit-searchsubmitSearchnone
#edit-submit-search--2submitSearchnone
#edit-submit-search--3submitSearchnone
#edit-submit-search--2submitSearchnone
#edit-searchtext(Search)placeholder only
#edit-search--3text(Search)placeholder only
#fsc-search-inputtext(What are you looking for?)placeholder only
#edit-search--2text(Search)placeholder only
#edit-search--2text(Search)placeholder only
#edit-submitsubmit(none)none

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

<input type="submit" name="op" id="edit-submit">

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="search" id="fsc-search-input">; <input type="text" name="search" id="edit-search">; <input type="text" name="search" id="edit-search--2">; <input type="text" name="search" id="edit-search--3">; <input type="text" name="search" id="edit-search--2">

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | fsc.org ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
9 icon(s) detected
REVIEW
9 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 The last candelilleros
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Safeguarding Romania’s forests
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
32px · bottom of viewport
h1 From the heart of the Amazon
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Main navigation
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mobile navigation
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 In search of inspiration?
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Strengthening trust across forest supply…
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We set the global standard for responsib…
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FSC Certification
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted worldwide
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Strengthening trust across forest supply…
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 We set the global standard for responsib…
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Global Impact
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How FSC works in practice
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Working together for forests
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Yolanda Ramirez
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ava Spoden
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Arushi Sen
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FSC standards in action
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Already part of the FSC system?
2.73:1
#000000
on
#285C4D
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The last candeliller…2.73:13.0:1
#000000
#285C4D
Fail
h1 Safeguarding Romania…2.73:13.0:1
#000000
#285C4D
Fail
h1 From the heart of th…2.73:13.0:1
#000000
#285C4D
Fail
h2 Main navigation2.73:13.0:1
#000000
#285C4D
Fail
h2 Mobile navigation2.73:13.0:1
#000000
#285C4D
Fail
h2 In search of inspira…2.73:13.0:1
#000000
#285C4D
Fail
h2 Strengthening trust …2.73:13.0:1
#000000
#285C4D
Fail
h2 We set the global st…2.73:13.0:1
#000000
#285C4D
Fail
h2 FSC Certification2.73:13.0:1
#000000
#285C4D
Fail
h2 Trusted worldwide2.73:13.0:1
#000000
#285C4D
Fail
h2 Strengthening trust …2.73:13.0:1
#000000
#285C4D
Fail
h2 We set the global st…2.73:13.0:1
#000000
#285C4D
Fail
h2 Our Global Impact2.73:13.0:1
#000000
#285C4D
Fail
h2 How FSC works in pra…2.73:13.0:1
#000000
#285C4D
Fail
h2 Working together for…2.73:13.0:1
#000000
#285C4D
Fail
h2 Yolanda Ramirez2.73:13.0:1
#000000
#285C4D
Fail
h2 Ava Spoden2.73:13.0:1
#000000
#285C4D
Fail
h2 Arushi Sen2.73:13.0:1
#000000
#285C4D
Fail
h2 FSC standards in act…2.73:13.0:1
#000000
#285C4D
Fail
h2 Already part of the …2.73:13.0:1
#000000
#285C4D
Fail

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
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 27 passed
PASS
92

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#page > header#header > div.region > button.mobile-menu--trigger div#page > header#header > div.region > button.mobile-menu--trigger

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Accept all cookies div.cmpboxbtns > span#cmpwelcomebtnyes > a.cmpboxbtn > span#cmpbntyestxt
Accept necessary cookies only div.cmpboxbtns > span#cmpwelcomebtnno > a.cmpboxbtn > span#cmpbntnotxt
Customize cookies div.cmpboxbtns > span#cmpwelcomebtncustom > a.cmpboxbtn > span#cmpbntcustomtxt
Privacy notice div.cmpboxinner > div.cmpboxbtns > div.cmpmore > a.cmpmorelink
Cookie Banner powered by div#cmpbox > div.cmplogo2 > span.cmplogo2hx
Contact Us div.region > div.footer-logo-section > div.contact-us-section > a.contact-us-link
Sign up for our newsletter div.sign-up-section > div.column > div.column-title > a.sign-up-link

These are opportunities to improve the legibility of your content.

○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
●Image elements have `[alt]` attributes
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`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
●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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●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
○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
○Form elements have associated labels
○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.
○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.
○`<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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback