https://panoramio.com
Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.SCORE
58
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
136 PASS 2 REVIEW 5 FIX
FFavicon & BrandingActionNo icons detectedFIX
Favicon & Branding
ActionNo icons detected
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
DWeb ManifestActionNot foundFIX
Web Manifest
ActionNot found
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.
DDark Mode SupportActionNo dark mode signalsFIX
Dark Mode Support
ActionNo dark mode signals
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.
DPrint StylesheetActionNo print stylesFIX
Print Stylesheet
ActionNo print styles
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 ✗
BLandmark Structure2 landmarksREVIEW
Landmark Structure
2 landmarks
2 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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.
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
C404 Error PageActionHTTP 404, custom pageREVIEW
404 Error Page
ActionHTTP 404, custom page
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Error 404 (Not Found)!!1 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
A+Heading Hierarchy6 headingsPASS
Heading Hierarchy
6 headings
6 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
- H1 (empty)
- H2 Thank you for stopping by.
- H3 Frequently-asked questions
- H4 What happened to my Panoramio data?
- H4 Will my Panoramio photos continue to appear in Google Earth and Google Maps?
- H4 Is there any way to keep posting photos to Google Earth and Google Maps?
Empty headings appear in the document outline but provide no information.
Why this matters
Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.
Source: WCAG 2.4.6
A+Alt Text QualityAll 1 images OKPASS
Alt Text Quality
All 1 images OK
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A+Form AccessibilityNo form controlsPASS
Form Accessibility
No form controls
No form controls
Info::
No form controls on this page
No form controls found.
A+Link & Button Quality6 links, 0 buttons — all OKPASS
Link & Button Quality
6 links, 0 buttons — all OK
6 links, 0 buttons — all OK
Info::
6 link(s) with descriptive text
6 links
0 empty
0 generic text
0 new tab
0 empty buttons
All links and buttons have descriptive accessible text.
6 links and buttons have descriptive text
A+Color Contrast (Screenshot)19 text elements analyzed, 0 fail WCAG AAPASS
Color Contrast (Screenshot)
19 text elements analyzed, 0 fail WCAG AA
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
19 pass
Show all checked elements (19)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Thank you for stoppi… | 19.77:1 | 3.0:1 | #000000 | #F8F8F8 | Pass |
| h3 Frequently-asked que… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Panoramio is no long… | 19.77:1 | 4.5:1 | #000000 | #F8F8F8 | Pass |
| p Panoramio has been d… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p Sincerely, | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p The Panoramio team | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| h4 What happened to my … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| p If your Panoramio pr… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| h4 Will my Panoramio ph… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| p If your Panoramio ph… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Contributions screen | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p from the main menu. | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| h4 Is there any way to … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| p Yes - to keep adding… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a join the Local Guide… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| p . You can earn point… | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Google | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a About Google | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a Privacy & Terms | 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.
ALighthouse Accessibility AuditsScore 94/100 — 1 failing, 16 passedPASS
Lighthouse Accessibility Audits
Score 94/100 — 1 failing, 16 passed
94
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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
Why this matters
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Contributions screen ol > li > p > a |
join the Local Guides program ol > li > p > a |
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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●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.
●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 have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○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
○Elements use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<frame>` or `<iframe>` elements have a title
○`<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.
○No element has a `[tabindex]` value greater than 0
○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.