Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 5 REVIEW 5 FIX

Link & Button Quality

Action

9 issue(s) across 69 links and 8 buttons

FIX

9 issue(s) across 69 links and 8 buttons

9 link(s) with no accessible text

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

Got: https://modefestival.com/; https://modefestival.com/; https://www.facebook.com/SmugMug; https://www.instagram.com/smugmug/; https://www.youtube.com/user/SmugMugFilms; https://www.tugboatinstitute.com/certified-evergreen/; https://www.greatplacetowork.com/certified-company/7051750; https://www.climateneutral.org/brand/smugmug; https://www.conservationalliance.com

8 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="/"]; a[data-testid="footer_product"]; a[data-testid="footer_company"]; a[data-testid="footer_community"]; a[data-testid="footer_apps"]; a[data-testid="footer_support"]; a[data-testid="footer_support"]; a[data-testid="footer_support"]

9 link(s) open in new tab without warning

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

Got: https://www.smugmug.com/about/privacy; https://www.smugmug.com/about/privacy; http://modefestival.com/terms; https://www.smugmug.com/stories/heidi-anderson; https://www.smugmug.com/development-lab/posts/smugmug-spotlight-erika-seress; https://www.smugmug.com/development-lab/posts/smugmug-spotlight-richard-burley; https://help.smugmug.com/; https://secure.smugmug.com/help/contact; https://feedback.smugmug.com/

43 link(s) with descriptive text

69 links

9 empty

0 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.smugmug.com/about/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://www.smugmug.com/about/privacy	you agree to our use of cookie…	new tab	Add '(opens in new tab)' to text
https://modefestival.com/	(empty)	empty	Add link text or aria-label
https://modefestival.com/	(empty)	empty	Add link text or aria-label
/	home	img no alt	Add alt attribute to the image
http://modefestival.com/terms	www.modefestival.com/terms	new tab	Add '(opens in new tab)' to text
https://www.smugmug.com/stories/heidi-an…	Legacy Livestock Imaging	new tab	Add '(opens in new tab)' to text
https://www.smugmug.com/development-lab/…	The Pod photo	new tab	Add '(opens in new tab)' to text
https://www.smugmug.com/development-lab/…	Epic Action Imagery	new tab	Add '(opens in new tab)' to text
#	product	img no alt	Add alt attribute to the image
#	company	img no alt	Add alt attribute to the image
#	community	img no alt	Add alt attribute to the image
#	Support	img no alt	Add alt attribute to the image
https://help.smugmug.com/	Support Center	new tab	Add '(opens in new tab)' to text
https://secure.smugmug.com/help/contact	Contact A Hero	new tab	Add '(opens in new tab)' to text
https://feedback.smugmug.com/	Product Feedback	new tab	Add '(opens in new tab)' to text
#	Storage	img no alt	Add alt attribute to the image
#	Sharing	img no alt	Add alt attribute to the image
#	Selling	img no alt	Add alt attribute to the image
https://www.facebook.com/SmugMug	(empty)	empty	Add link text or aria-label
https://www.instagram.com/smugmug/	(empty)	empty	Add link text or aria-label
https://www.youtube.com/user/SmugMugFilm…	(empty)	empty	Add link text or aria-label
https://www.tugboatinstitute.com/certifi…	(empty)	empty	Add link text or aria-label
https://www.greatplacetowork.com/certifi…	(empty)	empty	Add link text or aria-label
https://www.climateneutral.org/brand/smu…	(empty)	empty	Add link text or aria-label
https://www.conservationalliance.com	(empty)	empty	Add link text or aria-label

51 links and buttons have descriptive text

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

https://modefestival.com/; https://modefestival.com/; https://www.facebook.com/SmugMug; https://www.instagram.com/smugmug/; https://www.youtube.com/user/SmugMugFilms; https://www.tugboatinstitute.com/certified-evergreen/; https://www.greatplacetowork.com/certified-company/7051750; https://www.climateneutral.org/brand/smugmug; https://www.conservationalliance.com

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="/"]; a[data-testid="footer_product"]; a[data-testid="footer_company"]; a[data-testid="footer_community"]; a[data-testid="footer_apps"]; a[data-testid="footer_support"]; a[data-testid="footer_support"]; a[data-testid="footer_support"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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

https://www.smugmug.com/about/privacy; https://www.smugmug.com/about/privacy; http://modefestival.com/terms; https://www.smugmug.com/stories/heidi-anderson; https://www.smugmug.com/development-lab/posts/smugmug-spotlight-erika-seress; https://www.smugmug.com/development-lab/posts/smugmug-spotlight-richard-burley; https://help.smugmug.com/; https://secure.smugmug.com/help/contact; https://feedback.smugmug.com/

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

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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

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)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Heading Hierarchy

12 headings, 1 skip(s)

REVIEW

12 headings, 1 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Privacy Preferences
H2 Privacy and Cookie Policy
H1 SMUGMUG x MODE FESTIVAL PROMOTION OFFICIAL TERMS AND CONDITIONS
H1 Success starts here. duplicate H1
H2 Get more done better.
H2 Zero-stress support for every style and subject.
H4 HEIDI ANDERSON skipped
H4 ERIKA SERESS
H4 RICHARD BURLEY
H3 Don’t just take their words for it. Find a plan that fits your vision.
H2 Show off with gorgeous drag-and-drop site templates.
H2 Grow with the flow.

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

Form Accessibility

2 of 4 controls have issues

REVIEW

2 of 4 controls have issues

1 control(s) without accessible label

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

Got: <input type="submit">

1 control(s) rely on placeholder only

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

Got: <input type="email" name="Email" id="Email">

2 control(s) properly labeled

4 controls

2 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#ccpa-sharing-toggle	checkbox		none
input	checkbox		none
#Email	email	(Enter Email Address)	placeholder only
input	submit	(none)	none

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

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.

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Photo Sharing. Your Photos Look Better Here. ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

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

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

h1 Success starts here.

1.00:1

#000000

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Get more done better.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Zero-stress support for every style and …

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Show off with gorgeous drag-and-drop sit…

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Grow with the flow.

1.00:1

#000000

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Don’t just take their words for it. …

1.00:1

#000000

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Success starts here.	1.00:1	3.0:1	#000000	#000000	Fail
h2 Get more done better…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Zero-stress support …	1.00:1	3.0:1	#000000	#000000	Fail
h2 Show off with gorgeo…	1.00:1	3.0:1	#000000	#000000	Fail
h2 Grow with the flow.	1.00:1	3.0:1	#000000	#000000	Fail
h3 Don’t just take th…	1.00:1	3.0:1	#000000	#000000	Fail
title SmugMug \| Create. St…	14.10:1	4.5:1	#000000	#CFDE00	Pass
div The World’s Photog…	12.44:1	4.5:1	#000000	#C3D100	Pass
div September 18-20, 202…	14.10:1	4.5:1	#000000	#CFDE00	Pass
div Minneapolis, Minneso…	17.48:1	4.5:1	#000000	#EAEBE2	Pass
div Free	17.48:1	4.5:1	#000000	#EAEBE2	Pass
span MODE	17.48:1	4.5:1	#000000	#EAEBE2	Pass
div Festival™ passes f…	17.48:1	4.5:1	#000000	#EAEBE2	Pass
div Terms and conditions	17.48:1	4.5:1	#000000	#EAEBE2	Pass
div Start Trial	17.48:1	4.5:1	#000000	#EAEBE2	Pass
div The World’s Photog…	17.48:1	4.5:1	#000000	#EAEBE2	Pass
div September 18-20, 202…	17.48:1	4.5:1	#000000	#EAEBE2	Pass
div Minneapolis, Minneso…	17.48:1	4.5:1	#000000	#EAEBE2	Pass
div Free	17.48:1	4.5:1	#000000	#EAEBE2	Pass
span MODE	17.48:1	4.5:1	#000000	#EAEBE2	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

9 landmarks

PASS

9 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+

Alt Text Quality

All 41 images OK

PASS

All 41 images OK

37 decorative image(s) correctly marked

4 image(s) with good alt text

41 images 4 good alt text 37 decorative

All images have appropriate alt text.

Lighthouse Accessibility Audits

Score 92/100 — 3 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.

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
HEIDI ANDERSON `div#w-node-c2de7a50-4b4d-ae7a-3133-b4d9bbcf58be-3e6f824f > div#w-node-c2de7a50-4b4d-ae7a-3133-b4d9bbcf58bf-3e6f824f > div.testimonials_info > h4.heading-style-h4`

These are opportunities to improve keyboard navigation in your application.

Names and labels

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.marquee_track > div.marquee_content > div.banner_festival-info > a.marquee_mode-logo `div.marquee_track > div.marquee_content > div.banner_festival-info > a.marquee_mode-logo`
div.marquee_track > div.marquee_content > div.banner_festival-info > a.marquee_mode-logo `div.marquee_track > div.marquee_content > div.banner_festival-info > a.marquee_mode-logo`
div.container-large > div.newsletter-wrapper > div.social-buttons > a.social-icon `div.container-large > div.newsletter-wrapper > div.social-buttons > a.social-icon`
div.container-large > div.newsletter-wrapper > div.social-buttons > a.social-icon `div.container-large > div.newsletter-wrapper > div.social-buttons > a.social-icon`
div.container-large > div.newsletter-wrapper > div.social-buttons > a.social-icon `div.container-large > div.newsletter-wrapper > div.social-buttons > a.social-icon`
div.footer-btm > div.footer_icon-wrap > div.tall-icons > a.link-block-12 `div.footer-btm > div.footer_icon-wrap > div.tall-icons > a.link-block-12`
div.footer-btm > div.footer_icon-wrap > div.tall-icons > a.link-block-13 `div.footer-btm > div.footer_icon-wrap > div.tall-icons > a.link-block-13`
div.footer-btm > div.footer_icon-wrap > div.horizontal-icons > a.link-block-14 `div.footer-btm > div.footer_icon-wrap > div.horizontal-icons > a.link-block-14`
div.footer-btm > div.footer_icon-wrap > div.horizontal-icons > a.link-block-15 `div.footer-btm > div.footer_icon-wrap > div.horizontal-icons > a.link-block-15`

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.footer-btm > div.footer_icon-wrap > div.tall-icons > a.link-block-12 `div.footer-btm > div.footer_icon-wrap > div.tall-icons > a.link-block-12`

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

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

●Input buttons have discernible text.

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

●`button`, `link`, and `menuitem` elements have accessible names

●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

●Background and foreground colors have a sufficient contrast ratio

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

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

●No element has a `[tabindex]` value greater than 0

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○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

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

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

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○`<input type="image">` elements have `[alt]` text

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

○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

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.