Skip to content
https://shinyapps.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
48
GRADE
F
FIX
9
REVIEW
2
PASS
2
INFO
0
Checks
13
2 PASS 2 REVIEW 9 FIX
D
Landmark Structure
Action
13 landmarks
FIX
13 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark 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 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

F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title 404: Not Found ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 68/100 — 6 failing, 13 passed
FIX
68

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.row > div.navbar-header > button.navbar-toggle div.container > div.row > div.navbar-header > button.navbar-toggle

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
body > footer.footer > a.social body > footer.footer > a.social
body > footer.footer > a.social body > footer.footer > a.social
body > footer.footer > a.social body > footer.footer > a.social
body > footer.footer > a.social body > footer.footer > a.social

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.

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
Important Platform Update: At the end of 2026, all shinyapps.io users will be m… body > header.header > div#announcement-banner
shinyapps.io div.row > div.navbar-header > div.navbar-brand > a
by Posit div.row > div.navbar-header > div.navbar-brand > span.less-emphasis
Posit div.navbar-header > div.navbar-brand > span.less-emphasis > a
Share your Shiny Applications Online div.row > div.col-md-offset-2 > div.hero-text > h2
Deploy your Shiny applications on the Web in minutes div.row > div.col-md-offset-2 > div.hero-text > p
Sign Up div.row > div.col-md-offset-2 > div.hero-action > a.btn
/month div.pricing-body > div.pricing-price > strong > sub
New to Shiny? Deploy your applications for FREE. section.pricing-table > div.pricing-body > div.pricing-price > p.subtitle
Sign Up Now div.grid5 > section.pricing-table > footer > a.btn
/month div.pricing-body > div.pricing-price > strong > sub
More applications. More active hours! section.pricing-table > div.pricing-body > div.pricing-price > p.subtitle
Sign Up Now div.grid5 > section.pricing-table > footer > a.btn
BASIC div.row > div.grid5 > section.pricing-table > header
/month div.pricing-body > div.pricing-price > strong > sub
Take your users to the next level! section.pricing-table > div.pricing-body > div.pricing-price > p.subtitle
Unlimited Applications section.pricing-table > div.pricing-body > ul > li
Unlimited div.pricing-body > ul > li > strong
500 div.pricing-body > ul > li > strong
Active Hours div.pricing-body > ul > li > a.info
Performance Boost div.pricing-body > ul > li > a.info
Premium Email Support section.pricing-table > div.pricing-body > ul > li
/month div.pricing-body > div.pricing-price > strong > sub
Password protection? Authenticate your users! section.pricing-table > div.pricing-body > div.pricing-price > p.subtitle
Sign Up Now div.grid5 > section.pricing-table > footer > a.btn
/month div.pricing-body > div.pricing-price > strong > sub
Professional has it all! Personalize your domains. section.pricing-table > div.pricing-body > div.pricing-price > p.subtitle
Sign Up Now div.grid5 > section.pricing-table > footer > a.btn
Terms of Use footer.fineprint > p > small > a
shinyapps.io user guide div.bullet > div.bullet-content > p > a
Shiny Dev Center div.bullet > div.bullet-content > p > a
shinyapps.io category on Posit Community div.bullet > div.bullet-content > p > a
Posit Support site div.bullet > div.bullet-content > p > a
© Copyright 2022 Posit Software, PBC | All Rights Reserved |       | Terms … body > footer.footer
Terms and Conditions body > footer.footer > a
Privacy Policy body > footer.footer > a

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
shinyapps.io user guide div.bullet > div.bullet-content > p > a
Shiny Dev Center div.bullet > div.bullet-content > p > a
shinyapps.io category on Posit Community div.bullet > div.bullet-content > p > a
Posit Support site div.bullet > div.bullet-content > p > a
Terms and Conditions body > footer.footer > a
Privacy Policy body > footer.footer > a

These are opportunities to improve the legibility of your content.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.no-js html.no-js

These are opportunities to improve the interpretation of your content by users in different locales.

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.no-js html.no-js

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>`
●`[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.
●Document has a `<title>` element
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○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 a valid value for its `[lang]` attribute
○`<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.
○Uses ARIA roles only on compatible elements
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
B
Heading Hierarchy
10 headings
REVIEW
10 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H2 Share your Shiny Applications Online
  • H3 Easy To Use
  • H3 Secure
  • H3 Scalable
  • H2 Easy to Use
  • H2 Secure
  • H2 Scalable
  • H3 Documentation
  • H3 Community Support
  • H3 Premium Email Support

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
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 5 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Share your Shiny App…6.19:13.0:1
#000000
#5B90BF
Pass
h2 Easy to Use6.19:13.0:1
#000000
#5B90BF
Pass
h2 Secure6.19:13.0:1
#000000
#5B90BF
Pass
h2 Scalable6.19:13.0:1
#000000
#5B90BF
Pass
h3 Easy To Use6.19:13.0:1
#000000
#5B90BF
Pass
h3 Secure6.19:13.0:1
#000000
#5B90BF
Pass
h3 Scalable6.19:13.0:1
#000000
#5B90BF
Pass
h3 Documentation6.19:13.0:1
#000000
#5B90BF
Pass
h3 Community Support6.19:13.0:1
#000000
#5B90BF
Pass
h3 Premium Email Suppor…6.19:13.0:1
#000000
#5B90BF
Pass
title shinyapps.io18.75:14.5:1
#000000
#E9F7D7
Pass
span Important Platform U…18.75:14.5:1
#000000
#E9F7D7
Pass
div At the end of 2026, …18.75:14.5:1
#000000
#E9F7D7
Pass
a docs21.00:14.5:1
#000000
#FFFFFF
Pass
div for more information…13.61:14.5:1
#000000
#BDD3E5
Pass
a shinyapps.io6.19:14.5:1
#000000
#5B90BF
Pass
a Posit6.19:14.5:1
#000000
#5B90BF
Pass
a Home6.19:14.5:1
#000000
#5B90BF
Pass
a Features6.19:14.5:1
#000000
#5B90BF
Pass
a Pricing6.19:14.5:1
#000000
#5B90BF
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.

A
Alt Text Quality
3 of 4 images have issues
PASS
3 of 4 images have issues
Warning::
3 image(s) with filename as alt text
Info::
1 image(s) with good alt text
4 images 1 good alt text 3 generic
IssueCount
filename3 image(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback