Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure5 landmarksREVIEW
Multiple navigations need aria-label to distinguish them for screen readers.
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.
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
CLink & Button QualityAction8 issue(s) across 121 links and 29 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://www.facebook.com/Alamy/ | Find us on facebook | new tab | Add '(opens in new tab)' to text |
| https://www.youtube.com/user/Alamylimite… | Follow us on Youtube | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/alamyltd/ | Follow us on Instagram | new tab | Add '(opens in new tab)' to text |
| https://www.linkedin.com/company/alamy | Follow us on Linkedin | new tab | Add '(opens in new tab)' to text |
| https://www.pinterest.com/alamy/ | Follow us on Pinterest | new tab | Add '(opens in new tab)' to text |
| https://twitter.com/alamy | Follow us on twitter | new tab | Add '(opens in new tab)' to text |
| https://www.tiktok.com/@alamy.com/ | Follow us on TikTok | new tab | Add '(opens in new tab)' to text |
| /forgot-password/ | Forgotten your password? | new tab | Add '(opens in new tab)' to text |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Add '(opens in new tab)' to link text or aria-label.
https://www.facebook.com/Alamy/; https://www.youtube.com/user/Alamylimited; https://www.instagram.com/alamyltd/; https://www.linkedin.com/company/alamy; https://www.pinterest.com/alamy/; https://twitter.com/alamy; https://www.tiktok.com/@alamy.com/; /forgot-password/
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
Icon-only buttons need an aria-label so screen readers can announce them.
button.fixed (#138 on page); button.fixed (#153 on page); button.fixed (#175 on page); button.h-full (#424 on page); button.fixed (#1016 on page); button.absolute (#1021 on page); button.fixed (#1029 on page); button.absolute (#1034 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
B404 Error PageHTTP 404, custom pageREVIEW
BFavicon & Branding7 icon(s) detectedREVIEW
BWeb ManifestValid manifestREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 10 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
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)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Get great features w… | 1.32:1 | 3.0:1 | #000000 | #121F49 | Fail |
| h2 Our company | 1.32:1 | 3.0:1 | #000000 | #121F49 | Fail |
| h2 Buying from alamy | 1.32:1 | 3.0:1 | #000000 | #121F49 | Fail |
| h2 Sell your content | 1.32:1 | 3.0:1 | #000000 | #121F49 | Fail |
| h2 Support | 1.32:1 | 3.0:1 | #000000 | #121F49 | Fail |
| h2 Legal | 1.32:1 | 3.0:1 | #000000 | #121F49 | Fail |
| title Get creative with st… | 15.59:1 | 4.5:1 | #000000 | #00FF7B | Pass |
| span Create an account to… | 15.59:1 | 4.5:1 | #000000 | #00FF7B | Pass |
| span Lightboxes | 1.00:1 | 4.5:1 | #000000 | #000000 | Fail |
| span Lightboxes | 1.00:1 | 4.5:1 | #000000 | #000000 | Fail |
| span Cart | 6.75:1 | 4.5:1 | #000000 | #929292 | Pass |
| span Sign in | 2.83:1 | 4.5:1 | #000000 | #4A5763 | Fail |
| span Hi there! | 2.28:1 | 4.5:1 | #000000 | #354A5B | Fail |
| span Lightboxes | 19.09:1 | 4.5:1 | #000000 | #F4F4F4 | Pass |
| div Share Alamy images w… | 19.09:1 | 4.5:1 | #000000 | #F4F4F4 | Pass |
| span Create a lightbox … | 19.09:1 | 4.5:1 | #000000 | #F4F4F4 | Pass |
| span Images | 19.09:1 | 4.5:1 | #000000 | #F4F4F4 | Pass |
| a Images homepage | 19.09:1 | 4.5:1 | #000000 | #F4F4F4 | Pass |
| a Photos | 19.09:1 | 4.5:1 | #000000 | #F4F4F4 | Pass |
| a Vectors | 19.09:1 | 4.5:1 | #000000 | #F4F4F4 | 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.
AHeading Hierarchy24 headings, 1 skip(s)PASS
- H1 OVER 400 MILLION IMAGES TO BE DISCOVERED
- H2 CREATIVE
- H2 EDITORIAL
- H2 PHOTOGRAPHY
- H2 ARCHIVES
- H2 Over 18 million new videos to discover
- H2 LIVE NEWS
- H2 VIDEO
- H2 Get Inspired
- H2 CONTRIBUTOR SPOTLIGHT - CHRISTOF GRANDL
- H2 Some of our partners
- H2 ENTERPRISE
- H2 VECTORS
- H2 LATEST COLLECTIONS
- H2 Let's connect
- H2 Get great features with your free account
- H2 Our company
- H2 Buying from alamy
- H2 Sell your content
- H2 Support
- H2 Legal
- H2 Get inspired for your next project!
- H4 Download Confirmation skipped
- H4 Password Confirmation
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
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
A+Alt Text QualityAll 24 images OKPASS
| Issue | Count |
|---|---|
| too long | 1 image(s) |
AForm Accessibility1 of 4 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #qt | text | Search for imagesSearch for stock images, vectors and videos | for/id |
| text | Enter your email address | for/id | |
| #email-footer | text | Email address | for/id |
| password | password | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="password" name="password">
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
ALighthouse Accessibility AuditsScore 93/100 — 2 failing, 25 passedPASS
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
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Informational: a Permissions-Policy directive showing feature -> allowed origins.
Source: MDN Permissions-Policy
| Failing Elements |
|---|
We use essential cookies to make our site work. With your consent, we may also … div#termly-code-snippet-support > div > div.termly-styles-root-f9c495 > div.termly-styles-consent-banner-fa199d |
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.
Contrast
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Search for images div.relative > div.relative > label.absolute > span.2xl:hidden |
Enter your email address div.flex > form.flex > div.relative > label.3xs:text-4xs |
Email address div.md-4:mt-10 > form.flex > div.relative > label.pointer-events-none |
These are opportunities to improve the legibility of your content.