Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

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 ✗

Web Manifest

Action

Not found

FIX

Not found

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

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.

Link & Button Quality

Action

2 issue(s) across 91 links and 3 buttons

REVIEW

2 issue(s) across 91 links and 3 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a#features; a#community

14 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://github.com/ImageMagick/ImageMagick/discussions; http://tarr.uspto.gov/servlet/tarr?regser=serial&entry=78333969; https://github.com/ImageMagick/ImageMagick; https://legacy.imagemagick.org; https://usage.imagemagick.org; http://www.fmwconcepts.com/imagemagick/; https://im.snibgo.com/; https://github.com/dlemstra/Magick.NET; http://im.snibgo.com/; https://github.com/ImageMagick/ImageMagick/discussions (+4 more)

75 link(s) with descriptive text

91 links

2 empty

0 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://github.com/ImageMagick/ImageMagi…	Community	new tab	Add '(opens in new tab)' to text
http://tarr.uspto.gov/servlet/tarr?regse…	®	new tab	Add '(opens in new tab)' to text
https://github.com/ImageMagick/ImageMagi…	repository	new tab	Add '(opens in new tab)' to text
https://legacy.imagemagick.org	version 6	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://usage.imagemagick.org	Examples of ImageMagick Usage	new tab	Add '(opens in new tab)' to text
http://www.fmwconcepts.com/imagemagick/	Fred's ImageMagick Scripts	new tab	Add '(opens in new tab)' to text
https://im.snibgo.com/	Snibgo's ImageMagick Scripts	new tab	Add '(opens in new tab)' to text
https://github.com/dlemstra/Magick.NET	Magick.NET	new tab	Add '(opens in new tab)' to text
http://im.snibgo.com/	Cookbook	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label
https://github.com/ImageMagick/ImageMagi…	discussion	new tab	Add '(opens in new tab)' to text
https://github.com/ImageMagick/ImageMagi…	issue	new tab	Add '(opens in new tab)' to text
/image/wizard.png	The Tao of the Spiritual Warri…	new tab	Add '(opens in new tab)' to text
https://github.com/imagemagick/imagemagi…	GitHub	new tab	Add '(opens in new tab)' to text
https://twitter.com/imagemagick	Twitter	new tab	Add '(opens in new tab)' to text

78 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a#features; a#community

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://github.com/ImageMagick/ImageMagick/discussions; http://tarr.uspto.gov/servlet/tarr?regser=serial&entry=78333969; https://github.com/ImageMagick/ImageMagick; https://legacy.imagemagick.org; https://usage.imagemagick.org; http://www.fmwconcepts.com/imagemagick/; https://im.snibgo.com/; https://github.com/dlemstra/Magick.NET; http://im.snibgo.com/; https://github.com/ImageMagick/ImageMagick/discussions (+4 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color #000000 ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

title ImageMagick | Mastering Digital Image Al…

1.36:1

#000000

#212529

needs 4.5:1 (normal text)

16px · top of page (header area)

a ImageMagick

1.36:1

#000000

#212529

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Mastering Digital Im…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 ImageMagick	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Features and Capabil…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Community	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title ImageMagick \| Master…	1.36:1	4.5:1	#000000	#212529	Fail
a ImageMagick	1.36:1	4.5:1	#000000	#212529	Fail
a Download	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Tools	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a CLI	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Develop	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Community	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span 🌓	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a ☀️ Light	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 🌙 Dark	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 🌓 Auto	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p ImageMagick	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p is a free,	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a open-source	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p software suite, used…	21.00:1	4.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.

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

A+

Heading Hierarchy

4 headings

PASS

4 headings

Single H1 present

H1 Mastering Digital Image Alchemy
H2 ImageMagick
H3 Features and Capabilities
H3 Community

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
q	text	Search	aria-label
#gsc-i-id1	text	search	aria-label

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 25 passed

PASS

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
About ImageMagick `body > div.col-lg-8 > main.container > a.btn`

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

●Buttons have an accessible name

●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.

●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

●`<frame>` or `<iframe>` elements have a title

●`<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

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`[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 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

○ARIA IDs are unique

○No form fields have multiple labels

○`<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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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

○`<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.

○`<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.