Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

4 PASS 5 REVIEW 4 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-c17n38

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #000000

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 ModePartial Dark Mode

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

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

Landmark Structure

Action

11 landmarks

REVIEW

11 landmarks

<main> landmark present

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

5 <nav> landmark(s) found

5 of 5 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Link & Button Quality

1 issue(s) across 45 links and 9 buttons

REVIEW

1 issue(s) across 45 links and 9 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /offer/app ("Learn More")

16 link(s) open in new tab without warning

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

Got: https://blog.photobucket.com/the-advantages-of-centralizing-photos-and-videos…; https://blog.photobucket.com/new-group-buckets-takes-the-pain-out-of-group-sh…; https://blog.photobucket.com/image-hosting-how-and-when-to-host-images; https://my.photobucket.com/storageplan-ps-pp-0; https://blog.photobucket.com/photobucket-guarantees-the-digital-quality-of-yo…; https://blog.photobucket.com/photobucket-has-a-life-long-commitment-to-our-cu…; https://facebook.com/photobucket?utm_medium=web&utm_source=footer&utm_content…; https://instagram.com/photobucket?utm_medium=web&utm_source=footer&utm_conten…; https://pinterest.com/photobucket?utm_medium=web&utm_source=footer&utm_conten…; https://twitter.com/photobucket?utm_medium=web&utm_source=footer&utm_content=… (+6 more)

28 link(s) with descriptive text

45 links

0 empty

1 generic text

16 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/offer/app	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: App
https://blog.photobucket.com/the-advanta…	consolidate	new tab	Add '(opens in new tab)' to text
https://blog.photobucket.com/new-group-b…	group sharing	new tab	Add '(opens in new tab)' to text
https://blog.photobucket.com/image-hosti…	hosting	new tab	Add '(opens in new tab)' to text
https://my.photobucket.com/storageplan-p…	Hosting Plan	new tab	Add '(opens in new tab)' to text
https://blog.photobucket.com/photobucket…	guarantee	new tab	Add '(opens in new tab)' to text
https://blog.photobucket.com/photobucket…	carbon-neutral memory manageme…	new tab	Add '(opens in new tab)' to text
https://facebook.com/photobucket?utm_med…	Facebook	new tab	Add '(opens in new tab)' to text
https://instagram.com/photobucket?utm_me…	Instagram	new tab	Add '(opens in new tab)' to text
https://pinterest.com/photobucket?utm_me…	Pinterest	new tab	Add '(opens in new tab)' to text
https://twitter.com/photobucket?utm_medi…	Twitter	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UC8dQwMW…	Youtube	new tab	Add '(opens in new tab)' to text
https://www.printshoplab.com/products/ca…	Canvas Prints	new tab	Add '(opens in new tab)' to text
https://www.printshoplab.com/prints-and-…	Enlargements	new tab	Add '(opens in new tab)' to text
https://www.printshoplab.com/products/ph…	Greeting Cards	new tab	Add '(opens in new tab)' to text
https://www.printshoplab.com/products/ph…	Photo Books	new tab	Add '(opens in new tab)' to text
https://www.printshoplab.com/gifts?utm_m…	Photo Gifts	new tab	Add '(opens in new tab)' to text

37 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

/offer/app ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://blog.photobucket.com/the-advantages-of-centralizing-photos-and-videos…; https://blog.photobucket.com/new-group-buckets-takes-the-pain-out-of-group-sh…; https://blog.photobucket.com/image-hosting-how-and-when-to-host-images; https://my.photobucket.com/storageplan-ps-pp-0; https://blog.photobucket.com/photobucket-guarantees-the-digital-quality-of-yo…; https://blog.photobucket.com/photobucket-has-a-life-long-commitment-to-our-cu…; https://facebook.com/photobucket?utm_medium=web&utm_source=footer&utm_content…; https://instagram.com/photobucket?utm_medium=web&utm_source=footer&utm_conten…; https://pinterest.com/photobucket?utm_medium=web&utm_source=footer&utm_conten…; https://twitter.com/photobucket?utm_medium=web&utm_source=footer&utm_content=… (+6 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

6 icon(s) detected

REVIEW

6 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

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

span •

2.00:1

#89BBF7

#FFFFFF

needs 4.5:1 (normal text)

16px · above the fold

span •

2.00:1

#89BBF7

#FFFFFF

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Say hello to our new	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Say hello to our new	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Step 2	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Services	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get Help	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Discounts	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Resources	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Download the app & b…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Photobucket \| Photo …	16.94:1	4.5:1	#000000	#E4E7EC	Pass
a Sign In	18.56:1	4.5:1	#000000	#EFF1F4	Pass
a Sign Up	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span •	7.47:1	4.5:1	#1C47CB	#FFFFFF	Pass
span •	2.00:1	4.5:1	#89BBF7	#FFFFFF	Fail
span •	2.00:1	4.5:1	#89BBF7	#FFFFFF	Fail
span Take Photobucket eve…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Your memories don’…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Free Plan!	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p The best memories ar…	19.95:1	4.5:1	#000000	#F9F9F9	Pass
b Free Plan	21.00:1	3.0:1	#000000	#FFFFFF	Pass
p makes it easy to upl…	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.

Lighthouse Accessibility Audits

Score 84/100 — 5 failing, 26 passed

REVIEW

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Essential Always on These cookies are necessary for the website to function an… `div.dg-app > div.dg-main > div.dg-main-content > div.dg-collapsible`
These cookies are necessary for the website to function and cannot be switched … `div.dg-collapsible > div.dg-main-content-policies > div.dg-main-content-policy-option > div.dg-collapsible`
These cookies allow us to count visits and traffic sources so we can measure an… `div.dg-collapsible > div.dg-main-content-policies > div.dg-main-content-policy-option > div.dg-collapsible`
These cookies may be set through our site by our advertising partners. They may… `div.dg-collapsible > div.dg-main-content-policies > div.dg-main-content-policy-option > div.dg-collapsible`

When a `progressbar` element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to label `progressbar` elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#root > div > div > span.MuiCircularProgress-root `div#root > div > div > span.MuiCircularProgress-root`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
••• `section.css-16w6850 > div.carousel-root > div.carousel > ul.control-dots`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
View Plan Details `div.MuiBox-root > div.MuiBox-root > div.MuiPaper-root > button.MuiButtonBase-root`
View Plan Details `div.MuiBox-root > div.MuiBox-root > div.MuiPaper-root > button.MuiButtonBase-root`
View Plan Details `div.MuiBox-root > div.MuiBox-root > div.MuiPaper-root > button.MuiButtonBase-root`

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

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

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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●Identical links have the same purpose.

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

○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

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

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

Heading Hierarchy

11 headings

PASS

11 headings

Multiple H1 headings (5 found)

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

H1 Take Photobucket everywhere
H1 Say hello to our new Free Plan! duplicate H1
H1 Sync your WhatsApp images with Photobucket duplicate H1
H1 Take Photobucket everywhere duplicate H1
H1 Say hello to our new Free Plan! duplicate H1
H2 Step 2
H3 Download the app & back up
H2 Services
H2 Get Help
H2 Discounts
H2 Resources

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

A+

Alt Text Quality

All 19 images OK

PASS

All 19 images OK

2 decorative image(s) correctly marked

17 image(s) with good alt text

19 images 17 good alt text 2 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Photobucket

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Photobucket ✓192×192 icon ✓512×512 icon ✓Start URL . ✓Display Mode standalone ✓

Name Photobucket Display Mode standalone Theme Color #0672cb Background Color #ffffff Icons 3 icon(s)

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