Skip to content
https://divephotoguide.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
52
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 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
6 of 25 images have issues
FIX
6 of 25 images have issues
Critical::
6 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
6 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
5 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
25 images 14 good alt text 5 decorative 6 missing
IssueCount
missing6 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
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.
D
Lighthouse Accessibility Audits
Action
Score 69/100 — 7 failing, 15 passed
FIX
69

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
div.wrapper > div.header > form.search-form > input#keyword div.wrapper > div.header > form.search-form > input#keyword
PHOTO NEWS div#newsSlider > ul > li > a.category
PHOTO NEWS div#newsSlider > ul > li > a.category
PHOTO NEWS div#newsSlider > ul > li > a.category
DIVING NEWS div#newsSlider > ul > li > a.category
NEWS div.wrapper > ul.content-grid > li > a.type
PHOTOGRAPHER OF THE WEEK div.wrapper > ul.content-grid > li > a.type
TRAVEL div.wrapper > ul.content-grid > li > a.type
CRITTER CORNER div.wrapper > ul.content-grid > li > a.type
TECHNIQUES div.wrapper > ul.content-grid > li > a.type
FRESHWATER ADVENTURES div.wrapper > ul.content-grid > li > a.type
NEWS div.wrapper > ul.content-grid > li > a.type
INTERVIEWS WITH THE PROS div.wrapper > ul.content-grid > li > a.type

These are opportunities to improve the legibility of your content.

Names and labels

Adding discernable and accessible text to input buttons may help screen reader users understand the purpose of the input button. Learn more about input buttons.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wrapper > div.header > form.search-form > input div.wrapper > div.header > form.search-form > input

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
div.wrapper > div.header > form.search-form > input#keyword div.wrapper > div.header > form.search-form > input#keyword

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body > div.wrapper > div.slideshow-wrapper > iframe body > div.wrapper > div.slideshow-wrapper > iframe

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.top-line-outer > div.top-line > div.social-icons > a.instagram div.top-line-outer > div.top-line > div.social-icons > a.instagram
div.top-line-outer > div.top-line > div.social-icons > a.facebook div.top-line-outer > div.top-line > div.social-icons > a.facebook
div.top-line-outer > div.top-line > div.social-icons > a.twitter div.top-line-outer > div.top-line > div.social-icons > a.twitter
div.top-line-outer > div.top-line > div.social-icons > a.threads div.top-line-outer > div.top-line > div.social-icons > a.threads
div.top-line-outer > div.top-line > div.social-icons > a.youtube div.top-line-outer > div.top-line > div.social-icons > a.youtube
div.top-line-outer > div.top-line > div.social-icons > a.rss div.top-line-outer > div.top-line > div.social-icons > a.rss
div.slideshow-wrapper > ul.slideshow > li > a div.slideshow-wrapper > ul.slideshow > li > a
div.slideshow-wrapper > ul.slideshow > li > a div.slideshow-wrapper > ul.slideshow > li > a
div.slideshow-wrapper > ul.slideshow > li > a div.slideshow-wrapper > ul.slideshow > li > a
div.slideshow-wrapper > ul.slideshow > li > a div.slideshow-wrapper > ul.slideshow > li > a

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
div.wrapper > div.header > form.search-form > input div.wrapper > div.header > form.search-form > input
PHOTOGRAPHER OF THE WEEK div.wrapper > ul.content-grid > li > a.type
Photographer of the Week – Aaron Sanders div.wrapper > ul.content-grid > li > a.title
CRITTER CORNER div.wrapper > ul.content-grid > li > a.type
Photographing Batfish div.wrapper > ul.content-grid > li > a.title
FRESHWATER ADVENTURES div.wrapper > ul.content-grid > li > a.type
Photographing Ontario’s Salmon Run div.wrapper > ul.content-grid > li > a.title
NEWS div.wrapper > ul.content-grid > li > a.type
Isotta Announces Housing for the Nikon Z50 II div.wrapper > ul.content-grid > li > a.title
INTERVIEWS WITH THE PROS div.wrapper > ul.content-grid > li > a.type
Interviews with the Pros: Jules Jacobs div.wrapper > ul.content-grid > li > a.title
About Us div.wrapper > ul.bottom-nav > li > a
Contact div.wrapper > ul.bottom-nav > li > a
Advertise div.wrapper > ul.bottom-nav > li > a
Techniques div.wrapper > ul.bottom-nav > li > a
Articles div.wrapper > ul.bottom-nav > li > a
News div.wrapper > ul.bottom-nav > li > a
Travel div.wrapper > ul.bottom-nav > li > a
Galleries div.wrapper > ul.bottom-nav > li > a
Equipment div.wrapper > ul.bottom-nav > li > a
Contests div.wrapper > ul.bottom-nav > li > a
Underwater Competition div.wrapper > ul.bottom-nav > li > a
DPG Expeditions div.wrapper > ul.bottom-nav > li > a
DPG TV div.wrapper > ul.bottom-nav > li > a
Facebook div.wrapper > ul.bottom-nav > li > a
X (Twitter) div.wrapper > ul.bottom-nav > li > a
Threads div.wrapper > ul.bottom-nav > li > a
Instagram div.wrapper > ul.bottom-nav > li > a
Contribute div.wrapper > ul.bottom-nav > li > a
Join the Team div.wrapper > ul.bottom-nav > li > 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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●ARIA attributes are used as specified for the element's role
●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 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
●No element has a `[tabindex]` value greater than 0
●Heading elements appear in a sequentially-descending order
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<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
○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
○`<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.
C
Form Accessibility
Action
5 of 6 controls have issues
REVIEW
5 of 6 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="username" id="username">; <input type="password" name="password" id="password">; <input type="submit" name="button_login" id="button_login">; <input type="text" name="keyword" id="keyword">; <input type="submit">
Info::
1 control(s) properly labeled
6 controls
1 labeled
0 placeholder only
5 unlabeled
ControlTypeLabelMethod
#remember_mecheckboxRemember Mefor/id
#passwordpassword(none)none
#usernametext(none)none
#button_loginsubmit(none)none
#keywordtext(none)none
inputsubmit(none)none

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

<input type="text" name="username" id="username">; <input type="password" name="password" id="password">; <input type="submit" name="button_login" id="button_login">; <input type="text" name="keyword" id="keyword">; <input type="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

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 Underwater Photography & Video Portal ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Info::
Name present: DivePhotoGuide
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name DivePhotoGuide ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Name DivePhotoGuide Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 13 fail WCAG AA
REVIEW

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

7 pass 13 fail WCAG AA
h1 , lighting and work flow). Read latest n…
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · above the fold
h1 . Galleries of professional and amateur …
1.00:1
#000000
on
#000000
needs 3.0:1 (large text)
32px · mid-page
title Underwater Photography & Video: DivePhot…
1.28:1
#000000
on
#221F1F
needs 4.5:1 (normal text)
16px · top of page (header area)
a underwater equipment
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a wide angle
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a macro
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a super macro
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · above the fold
a travel destinations for underwater photo…
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Dive Photo Guide
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Login
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
a Register
1.00:1
#000000
on
#000000
needs 4.5:1 (normal text)
16px · mid-page
div Close
3.66:1
#000000
on
#666666
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
td Password
1.89:1
#000000
on
#003D6D
needs 4.5:1 (normal text)
16px · bottom of viewport

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 DPG is a comprehensi…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 website and communit…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 for popular digital …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 , lighting and work …1.00:13.0:1
#000000
#000000
Fail
h1 . Galleries of profe…1.00:13.0:1
#000000
#000000
Fail
title Underwater Photograp…1.28:14.5:1
#000000
#221F1F
Fail
a underwater photograp…21.00:14.5:1
#000000
#FFFFFF
Pass
a underwater photograp…21.00:14.5:1
#000000
#FFFFFF
Pass
a underwater equipment1.00:14.5:1
#000000
#000000
Fail
a wide angle1.00:14.5:1
#000000
#000000
Fail
a macro1.00:14.5:1
#000000
#000000
Fail
a super macro1.00:14.5:1
#000000
#000000
Fail
a travel destinations …1.00:14.5:1
#000000
#000000
Fail
a Dive Photo Guide1.00:14.5:1
#000000
#000000
Fail
a Login1.00:14.5:1
#000000
#000000
Fail
a Register1.00:14.5:1
#000000
#000000
Fail
div Login17.17:14.5:1
#000000
#E9E8E8
Pass
div Close3.66:14.5:1
#000000
#666666
Fail
td E-mail21.00:14.5:1
#000000
#FFFFFF
Pass
td Password1.89:14.5:1
#000000
#003D6D
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
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 DPG is a comprehensive underwater photography website and community for underwater photographers. Learn underwater photography techniques for popular digital cameras and specialized professional under
A
Favicon & Branding
7 icon(s) detected
PASS
7 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✓ Manifest Icons Present
✓ Multiple Sizes Present
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback