Skip to content
https://gimp.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 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::
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 Missing
✓ 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::
1 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 1 <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.
C
Landmark Structure
Action
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
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

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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="tipue_search_input">; <input type="text" name="q" id="tipue_search_input">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#tipue_search_inputtext(Search GIMP.org)placeholder only
#tipue_search_inputtext(Search with DuckDuckGo)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q" id="tipue_search_input">; <input type="text" name="q" id="tipue_search_input">

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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - GIMP ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 5 fail WCAG AA
REVIEW

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

15 pass 5 fail WCAG AA 8 pass AA only
title GIMP - GNU Image Manipulation Program
1.66:1
#000000
on
#333333
needs 4.5:1 (normal text)
16px · top of page (header area)
a GIMP
2.18:1
#000000
on
#3D464E
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Participate
4.41:1
#000000
on
#60758A
needs 4.5:1 (normal text)
16px · above the fold
a GIMP
4.48:1
#000000
on
#657685
needs 4.5:1 (normal text)
16px · above the fold
a Tutorials
3.41:1
#000000
on
#4C647A
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
h2 The Free & Open Sour…19.55:13.0:1
#000000
#F7F7F3
Pass
h2 High Quality Photo M…19.13:13.0:1
#000000
#F6F4F1
Pass
h2 Original Artwork Cre…19.13:13.0:1
#000000
#F6F4F1
Pass
h2 Graphic Design Eleme…19.13:13.0:1
#000000
#F6F4F1
Pass
h2 Programming Algorith…19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Key Component in a D…19.13:13.0:1
#000000
#F6F4F1
Pass
h3 Extensibility & Flex…19.13:13.0:1
#000000
#F6F4F1
Pass
title GIMP - GNU Image Man…1.66:14.5:1
#000000
#333333
Fail
a GIMP2.18:14.5:1
#000000
#3D464E
Fail
a Download4.66:14.5:1
#000000
#63798F
Pass
a News5.01:14.5:1
#000000
#6A7E91
Pass
a About4.94:14.5:1
#000000
#697D90
Pass
a Docs4.65:14.5:1
#000000
#63798D
Pass
a Participate4.41:14.5:1
#000000
#60758A
Fail
a Tutorials4.58:14.5:1
#000000
#63788A
Pass
a Donate4.66:14.5:1
#000000
#65798A
Pass
a GIMP4.48:14.5:1
#000000
#657685
Fail
a News5.14:14.5:1
#000000
#6E808E
Pass
a Docs5.19:14.5:1
#000000
#6D8190
Pass
a Tutorials3.41:14.5:1
#000000
#4C647A
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+
Heading Hierarchy
11 headings
PASS
11 headings
Info::
Single H1 present
  • H1 GIMP
  • H2 The Free & Open Source Image Editor
  • H2 Recent News
  • H2 High Quality Photo Manipulation
  • H2 Original Artwork Creation
  • H2 Graphic Design Elements
  • H2 Programming Algorithms
  • H3 Key Component in a Desktop Publishing Workflow
  • H4 Scribus
  • H4 Inkscape
  • H3 Extensibility & Flexibility
A+
Alt Text Quality
All 10 images OK
PASS
All 10 images OK
Info::
10 image(s) with good alt text
10 images 10 good alt text
All images have appropriate alt text.
A
Lighthouse Accessibility Audits
Score 91/100 — 2 failing, 14 passed
PASS
91

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
GIMP provides top-notch color management features to ensure high-fidelity color… div.container > div.row > div.column > p
Scribus div.row > div.column > p > a
Inkscape div.row > div.column > p > a
Scribus div.row > div.column > h4 > a
Inkscape div.row > div.column > h4 > a
GIMP provides extensibility through integration with many programming languages… div.container > div.row > div.column > p
The result is a high level of customization as demonstrated by the large number… div.container > div.row > div.column > p
Header image: Niagara Rainbow by Ville Pätsi (cba) div.container > div.row > div.column > p#headerImgAttr
Header div.row > div.column > p#headerImgAttr > em
Niagara Rainbow div.row > div.column > p#headerImgAttr > a.headerTitle
Ville Pätsi div.row > div.column > p#headerImgAttr > a.headerAuthor
cba div.column > p#headerImgAttr > a.headerLicense > span.cc
High Quality Photo Manipulation background image by Pat David (cba) div.container > div.row > div.column > p
High Quality Photo Manipulation div.row > div.column > p > em
Pat David div.row > div.column > p > a
cba div.column > p > a > span.cc
Original Artwork Creation background image by David Revoy (cb) div.container > div.row > div.column > p
Original Artwork Creation div.row > div.column > p > em
David Revoy div.row > div.column > p > a
cb div.column > p > a > span.cc
Graphic Design Elements background image by Ollin Bohan (cba) div.container > div.row > div.column > p
Graphic Design Elements div.row > div.column > p > em
Ollin Bohan div.row > div.column > p > a
cba div.column > p > a > span.cc
Unless otherwise noted, GIMP's Website by GIMP's Team is licensed under a Crea… div.row > div.column > p > small
GIMP's Website div.column > p > small > span

These are opportunities to improve the legibility of your content.

Best practices

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>`
●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.
●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.
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[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 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">`
○`<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
○`<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