Skip to content
https://sil.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
F
Heading Hierarchy
Action
19 headings, 7 skip(s)
FIX
19 headings, 7 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
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: H3 → H6 (missing H4)
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: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Life in everylanguage.
  • H4 Global Mission. Local Approach. skipped
  • H2 Why Language?
  • H3 Because language connects us to what matters most.
  • H3 Stories & News
  • H2 Stories
  • H4 Learning’s Next Chapter skipped
  • H2 Stories
  • H4 Fair Start skipped
  • H2 Stories
  • H4 The Path to Something New skipped
  • H2 Our Impact
  • H3 Founded in 1934 with two students.Today, our impact involves:
  • H6 staff & Volunteers skipped
  • H6 Language Communities
  • H6 Countries
  • H2 Where We Work
  • H4 We are a global community rooted in local realities. Our activities in each place are guided by the cultures, priorities, and partnerships of the people we serve. skipped
  • H6 DR. Johnstone ndunde, SIL Global Executive Director skipped

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
8 of 16 images have issues
FIX
8 of 16 images have issues
Critical::
8 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::
3 decorative image(s) correctly marked
Info::
5 image(s) with good alt text
16 images 5 good alt text 3 decorative 8 missing
IssueCount
missing8 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

F
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Attention Required! | Cloudflare ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 12 pass AA only
title SIL Global – Life in Every Language
1.52:1
#000000
on
#003049
needs 4.5:1 (normal text)
16px · top of page (header area)
span Looking for SIL language services or tec…
1.52:1
#000000
on
#003049
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
2.38:1
#000000
on
#634424
needs 4.5:1 (normal text)
16px · above the fold
div No results
3.16:1
#000000
on
#6B5A41
needs 4.5:1 (normal text)
16px · above the fold
div No results
2.65:1
#000000
on
#5C4F42
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Why Language?
3.37:1
#000000
on
#6C5F4A
needs 4.5:1 (normal text)
16px · above the fold

1 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
h1 in every3.82:13.0:1
#000000
#6F685E
Pass
h1 language.3.82:13.0:1
#000000
#6F685E
Pass
h2 Why Language?3.82:13.0:1
#000000
#6F685E
Pass
h2 Stories3.82:13.0:1
#000000
#6F685E
Pass
h2 Stories3.82:13.0:1
#000000
#6F685E
Pass
h2 Stories3.82:13.0:1
#000000
#6F685E
Pass
h2 Our Impact3.82:13.0:1
#000000
#6F685E
Pass
h2 Where We Work3.82:13.0:1
#000000
#6F685E
Pass
h3 Because language con…3.82:13.0:1
#000000
#6F685E
Pass
h3 Stories & News3.82:13.0:1
#000000
#6F685E
Pass
h3 Founded in 1934 with…3.82:13.0:1
#000000
#6F685E
Pass
h3 Today, our impact in…3.82:13.0:1
#000000
#6F685E
Pass
title SIL Global – Life …1.52:14.5:1
#000000
#003049
Fail
span Looking for SIL lang…1.52:14.5:1
#000000
#003049
Fail
a here21.00:14.5:1
#000000
#FFFFFF
Pass
button ✕21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content2.38:14.5:1
#000000
#634424
Fail
div No results3.16:14.5:1
#000000
#6B5A41
Fail
div No results2.65:14.5:1
#000000
#5C4F42
Fail
a Why Language?3.37:14.5:1
#000000
#6C5F4A
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 25 passed
REVIEW
84

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
EXPLORE OUR WORK div.stk-row > div.wp-block-stackable-button > a.stk-link > span.stk-button__inner-text
Why Language? div.stk-column-wrapper > div.stk-block-content > div#why-language > h2.stk-block-heading__text
Spiritual Growth div.stk-block-tab-labels__wrapper > button#stk-block-tab-label-6fb3da3-1 > div.stk-block-tab-labels__text > span
Stories div.wp-block-columns > div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > h2.stk-block-heading__text
Stories div.wp-block-columns > div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > h2.stk-block-heading__text
Stories div.wp-block-columns > div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > h2.stk-block-heading__text
VIEW ALL STORIES & NEWS div.stk-row > div.wp-block-stackable-button > a.stk-link > span.stk-button__inner-text
Where We Work article#post-734 > div.entry-content > div#where-we-work > h2.stk-block-heading__text
AMERICAS ul.region-list > li.region > a.btn > span
AFRICA ul.region-list > li.region > a.btn > span
EURASIA ul.region-list > li.region > a.btn > span
ASIA ul.region-list > li.region > a.btn > span
PACIFIC ul.region-list > li.region > a.btn > span
SIGN LANGUAGES ul.region-list > li.region > a.btn > span

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
here div#simple-banner > div.simple-banner-text > span > a

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
Global Mission. Local Approach. div.stk-column-wrapper > div.stk-block-content > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > h4.stk-block-heading__text
Learning’s Next Chapter div.wp-block-columns > div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > h4.stk-block-heading__text
Fair Start div.wp-block-columns > div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > h4.stk-block-heading__text
The Path to Something New div.wp-block-columns > div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > h4.stk-block-heading__text
STAFF & VOLUNTEERS div.stk-column-wrapper > div.stk-block-content > div#staff-amp-volunteers > h6.stk-block-heading__text
We are a global community rooted in local realities. Our activities in each pla… article#post-734 > div.entry-content > div#we-are-a-global-community-rooted-in-local-realities-our-activities-in-each-place-are-guided-by-the-cultures-priorities-and-partnerships-of-the-people-we-serve > h4.stk-block-heading__text
DR. JOHNSTONE NDUNDE, SIL GLOBAL EXECUTIVE DIRECTOR div.stk-column-wrapper > div.stk-block-content > div#span-style-color-var-theme-palette-color-6-f-9-fafb-class-stk-highlight-dr-johnstone-ndunde-sil-global-executive-director-span > h6.stk-block-heading__text

These are opportunities to improve keyboard navigation in your application.

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.wp-block-stackable-image > figure > span.stk-img-wrapper > img.stk-img div.wp-block-stackable-image > figure > span.stk-img-wrapper > img.stk-img
article#post-1866 > div.entry-content > section#region-list-block_dea550943e42457be84288d23bb9723c > img.region-list__map article#post-1866 > div.entry-content > section#region-list-block_dea550943e42457be84288d23bb9723c > img.region-list__map
div.wp-block-stackable-image > figure > span.stk-img-wrapper > img.stk-img div.wp-block-stackable-image > figure > span.stk-img-wrapper > img.stk-img
figure > a.stk-link > span.stk-img-wrapper > img.stk-img figure > a.stk-link > span.stk-img-wrapper > img.stk-img
figure > a.stk-link > span.stk-img-wrapper > img.stk-img figure > a.stk-link > span.stk-img-wrapper > img.stk-img
figure > a.stk-link > span.stk-img-wrapper > img.stk-img figure > a.stk-link > span.stk-img-wrapper > img.stk-img

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.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > figure > a.stk-link div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > figure > a.stk-link
div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > figure > a.stk-link div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > figure > a.stk-link
div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > figure > a.stk-link div.wp-block-column > div#span-data-stk-dynamic-current-page-post-title-with-link-true-contenteditable-false-class-stk-dynamic-content-language-preservation-in-bangladesh-span > figure > a.stk-link
div.stk-block-content > div.wp-block-stackable-image > figure > a.stk-link div.stk-block-content > div.wp-block-stackable-image > figure > a.stk-link
div.stk-block-content > div.wp-block-stackable-image > figure > a.stk-link div.stk-block-content > div.wp-block-stackable-image > figure > a.stk-link
div.stk-block-content > div.wp-block-stackable-image > figure > a.stk-link div.stk-block-content > div.wp-block-stackable-image > figure > a.stk-link

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.

○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
●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
●`[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
●`[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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○`<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
○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
○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.
○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+
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Mobile Menu" MAIN ASIDE CONTENTINFO footer
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
ssearchSearch for...aria-label
ssearchSearch for...aria-label
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback