Skip to content
https://tenor.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
6
REVIEW
6
PASS
1
INFO
0
Checks
13
1 PASS 6 REVIEW 6 FIX
D
Landmark Structure
Action
1 landmarks
FIX
1 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
Info::
No banner (header) landmark
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
BANNER (missing!) NAV MAIN (missing!) CONTENTINFO (missing!)

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

F
Alt Text Quality
Action
41 of 49 images have issues
FIX
41 of 49 images have issues
Critical::
41 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
41 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
8 image(s) with good alt text
49 images 8 good alt text 41 missing
IssueCount
missing41 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Tenor GIF Keyboard
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name Tenor GIF Keyboard ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
Name Tenor GIF Keyboard Icons 1 icon(s)
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.
B
Heading Hierarchy
2 headings
REVIEW
2 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Trending Tenor Searches
  • H2 Featured GIFs

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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 404 Error ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
8 icon(s) detected
REVIEW
8 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

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

20 pass 2 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Trending Tenor Searc…17.14:13.0:1
#000000
#E8E8E8
Pass
h2 Featured GIFs17.14:13.0:1
#000000
#E8E8E8
Pass
title Tenor GIF Keyboard -…21.00:14.5:1
#000000
#FFFFFF
Pass
div We've updated our13.47:14.5:1
#000000
#ABD4F5
Pass
a Terms of Service6.43:14.5:1
#000000
#2E93E6
Pass
span and6.43:14.5:1
#000000
#2E93E6
Pass
a Privacy Policy21.00:14.5:1
#000000
#FFFFFF
Pass
div . By continuing you …21.00:14.5:1
#000000
#FFFFFF
Pass
a Terms of Service21.00:14.5:1
#000000
#FFFFFF
Pass
span and21.00:14.5:1
#000000
#FFFFFF
Pass
a Privacy Policy21.00:14.5:1
#000000
#FFFFFF
Pass
div Tenor.com has been t…21.00:14.5:1
#000000
#FFFFFF
Pass
button here21.00:14.5:1
#000000
#FFFFFF
Pass
a Create21.00:14.5:1
#000000
#FFFFFF
Pass
button SIGN IN21.00:14.5:1
#000000
#FFFFFF
Pass
div Products21.00:14.5:1
#000000
#FFFFFF
Pass
a GIF Keyboard21.00:14.5:1
#000000
#FFFFFF
Pass
a Android21.00:14.5:1
#000000
#FFFFFF
Pass
div Explore21.00:14.5:1
#000000
#FFFFFF
Pass
button Language21.00:14.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.

B
Lighthouse Accessibility Audits
Score 82/100 — 3 failing, 12 passed
REVIEW
82

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
Terms of Service and Privacy Policy div.BaseApp > div.Banner > div.container > span.linkElements
Terms of Service div.Banner > div.container > span.linkElements > a
Privacy Policy div.Banner > div.container > span.linkElements > a
Terms of Service and Privacy Policy div.BaseApp > div.Banner > div.container > span.linkElements
Terms of Service div.Banner > div.container > span.linkElements > a
Privacy Policy div.Banner > div.container > span.linkElements > a
here div.container > div > span.linkElements > button
CREATE div.container > div.nav-buttons > div.account-buttons > a.button
SIGN IN div.container > div.nav-buttons > div.account-buttons > button.white-button

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.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img
div.Carousel > div.TrendsTag > a > img.img div.Carousel > div.TrendsTag > a > img.img

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

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-hidden="true"]` is not present on the document `<body>`
●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-hidden="true"]` elements do not contain focusable descendents
●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.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
○`[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
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[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
○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
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input name="q">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
qinput(Search for GIFs and Stickers)placeholder only

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

<input name="q">

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

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

Send Feedback