Skip to content
https://fineartamerica.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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 Present
PNG Icons Missing
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 Navigation" 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

C
Alt Text Quality
Action
36 of 540 images have issues
REVIEW
36 of 540 images have issues
Critical::
36 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
504 image(s) with good alt text
540 images 504 good alt text 36 missing
IssueCount
missing36 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

B
Form Accessibility
2 of 4 controls have issues
REVIEW
2 of 4 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="searchtag" id="searchFormHeaderInput">; <input type="text" name="searchtag" id="mobileNavigationSearchInput">
Info::
2 control(s) properly labeled
4 controls
2 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
#currencyselectfooterselectCurrencyfor/id
#unitsselectfooterselectUnitsfor/id
#searchFormHeaderInputtext(Search)placeholder only
#mobileNavigationSearchInputtext(Search)placeholder only

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

<input type="text" name="searchtag" id="searchFormHeaderInput">; <input type="text" name="searchtag" id="mobileNavigationSearchInput">

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 Page Not Found | Fine Art America Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Art You'll Love
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Shop by Style
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop by Department
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop by Room
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured Collections
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Shop by Art Medium
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Curated Collections
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Create Your Own Art
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Iconic Brands
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Meet the Artists
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Independent Artists | Together
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fine Art America
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Our Company
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Art
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Shop
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Create
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 SELLERS
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Contact
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Stay Connected
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Location Settings
1.25:1
#000000
on
#1D1D1D
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Art You'll Love1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Shop by Style1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Shop by Department1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Shop by Room1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Featured Collections1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Shop by Art Medium1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Curated Collections1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Create Your Own Art1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Iconic Brands1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Meet the Artists1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Independent Artists …1.25:13.0:1
#000000
#1D1D1D
Fail
h2 Fine Art America1.25:13.0:1
#000000
#1D1D1D
Fail
h3 Our Company1.25:13.0:1
#000000
#1D1D1D
Fail
h3 Art1.25:13.0:1
#000000
#1D1D1D
Fail
h3 Shop1.25:13.0:1
#000000
#1D1D1D
Fail
h3 Create1.25:13.0:1
#000000
#1D1D1D
Fail
h3 SELLERS1.25:13.0:1
#000000
#1D1D1D
Fail
h3 Contact1.25:13.0:1
#000000
#1D1D1D
Fail
h3 Stay Connected1.25:13.0:1
#000000
#1D1D1D
Fail
h3 Location Settings1.25:13.0:1
#000000
#1D1D1D
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.

B
Lighthouse Accessibility Audits
Score 85/100 — 5 failing, 27 passed
REVIEW
85

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
Toggle Mobile Navigation Menu ul.navigationmenu > li#menuTopThreeLines > button#buttonTopThreeLines > div
Featured Collections div.fullWidthDiv > div.container > div#collectionGroupTabContainerDiv > button#collectionGroupTab-1
1445 DESIGNS div#collectionHomepageGroupDivLarge > a.collectionHomepageContainerDiv > div > p
105 DESIGNS div#collectionHomepageGroupDivLarge > a.collectionHomepageContainerDiv > div > p
80 DESIGNS div#collectionHomepageGroupDivLarge > a.collectionHomepageContainerDiv > div > p
170 DESIGNS div#collectionHomepageGroupDivLarge > a.collectionHomepageContainerDiv > div > p
53 DESIGNS div#collectionHomepageGroupDivLarge > a.collectionHomepageContainerDiv > div > p
14529 DESIGNS div#collectionHomepageGroupDivLarge > a.collectionHomepageContainerDiv > div > p
Sign up for our newsletter for exclusive deals, discount codes, and more. div#footer > div > div > p

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#animationProductDiv > div.cube > div.cubeFace > img.ls-is-cached div#animationProductDiv > div.cube > div.cubeFace > img.ls-is-cached
div#animationProductDiv > div.cube > div.cubeFace > img.ls-is-cached div#animationProductDiv > div.cube > div.cubeFace > img.ls-is-cached
div > div > a > img div > div > a > img

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 > div > div > a div > div > div > 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
Press div > div > p > a
Reviews div > div > p > a
Blog div > div > p > a
Videos div > div > p > a
Sell Merch Online div > div > p > a
Famous Paintings div > div > p > a
Thomas Kinkade Prints div > div > p > a
CartoonStock Print Store div > div > p > a
Paintings div > div > p > a
Photographs div > div > p > a
Drawings div > div > p > a
Digital Art div > div > p > a
Mixed Media div > div > p > a
Wall Art div > div > p > a
Posters div > div > p > a
Tapestries div > div > p > a
Home Decor div > div > p > a
Metal Posters div > div > p > a
Movie Posters div > div > p > a
Cartoon Wall Art div > div > p > a
Apparel div > div > p > a
Gift Cards div > div > p > a
Mail & Frame div > div > p > a
Print NFTs div > div > p > a
NFT Merch div > div > p > a
Print AI Art div > div > p > a
Take a Tour div > div > p > a
Sell Your Art div > div > p > a
Instagram Merchandise div > div > p > a
YouTube Merchandise div > div > p > a
Terms of Use div > div > p > a
Privacy Policy div > div > p > a
Currency: EUR (€) div > div > p > button#footerButtonChangeCurrency
Units: Centimeters div > div > p > button#footerButtonChangeMeasurementUnits

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>`
`[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
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
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.
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.
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
Deprecated ARIA roles were not used
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.
`[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 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
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
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.
A+
Heading Hierarchy
20 headings
PASS
20 headings
Info::
Single H1 present
  • H1 Art You'll Love
  • H2 Shop by Style
  • H2 Shop by Department
  • H2 Shop by Room
  • H2 Featured Collections
  • H2 Shop by Art Medium
  • H2 Curated Collections
  • H2 Create Your Own Art
  • H2 Iconic Brands
  • H2 Meet the Artists
  • H2 Independent Artists | Together
  • H2 Fine Art America
  • H3 Our Company
  • H3 Art
  • H3 Shop
  • H3 Create
  • H3 SELLERS
  • H3 Contact
  • H3 Stay Connected
  • H3 Location Settings
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback