Juicer Social is built to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level A and AA—the international standard most accessibility laws and regulations point to, including the U.S. Department of Justice's ADA Title II rule for state and local government entities. Every feed Juicer Social renders on a customer's website is held to this standard, and the Juicer dashboard is built to the same rigor.
What WCAG 2.1 AA covers
WCAG 2.1 organizes accessibility requirements into four principles. To conform at Level AA, content must satisfy all Level A and Level AA success criteria across each principle:
Perceivable—content is presented in ways users can perceive (text alternatives for images, captions for video, sufficient color contrast, content that adapts to 200% zoom).
Operable—every interaction reachable by mouse must work by keyboard, time limits are adjustable, and no content flashes more than three times per second.
Understandable—page language is identified, navigation is consistent across pages, and errors are described in text.
Robust—content works with assistive technologies (screen readers, voice control) through valid markup and proper ARIA roles and states.
How Juicer Social conforms
Juicer feeds are built and audited internally against WCAG 2.1 Level A and AA, using the same automated accessibility tools many of our customers run on their own pages (such as Siteimprove). Concretely, that means the following:
Screen reader friendly—posts use semantic HTML with proper headings, landmarks, and accessible names so screen readers announce content correctly.
Keyboard navigable—every control in the feed (filters, post links, modal dialogs, pagination) is reachable and operable with the keyboard alone, with a visible focus indicator.
Color and contrast—text and interactive elements meet the required contrast ratios, and we never communicate state through color alone.
Reflow—the feed widget works without horizontal scrolling at viewport widths down to 320 CSS pixels, so it adapts to narrow containers and high zoom levels.
Media—Juicer-rendered videos preserve the source platform's native captions and controls; we don't strip them out.
Alt text—decorative icons are hidden from assistive tech, and post images carry the alt text supplied by the source platform.
We also audit feeds against WCAG 2.0 and WCAG 2.2 at Level A and AA where applicable, since each version builds on the previous one.
⚠️ How to read this report: WCAG defines three conformance levels:
A, AA and AAA.
Juicer Social targets A and AA—the levels accessibility laws reference. Items marked AAA in the screenshot are enhancements above that target, not violations. The S (best practices) item is a Siteimprove advisory; the missing "Skip to main content" link is added by the page that embeds Juicer, not by the Juicer embed itself.
U.S. compliance deadlines (ADA Title II)
If you embed Juicer on a website operated by a U.S. state or local government entity, the U.S. Department of Justice's 2024 ADA Title II rule requires the site to conform to WCAG 2.1 Level AA. On April 20, 2026, the DOJ published an Interim Final Rule extending the original compliance dates by one year. The accessibility standard has not changed—only the timing.
📅 Updated deadlines:
April 26, 2027—public entities serving 50,000 or more people (extended from April 24, 2026).
April 26, 2028—public entities serving fewer than 50,000 people, and special district government entities (extended from April 24, 2027).
For the full text of the rule and the extension, see the 2024 Final Rule and the 2026 Interim Final Rule on the Federal Register.
If you operate outside the United States, your obligations may come from a different framework—such as the European Accessibility Act, EN 301 549, or Section 508 in the U.S. federal context. All of these point at the same WCAG 2.1 Level AA baseline that Juicer is built to meet.
Choosing an accessible feed theme
Every standard layout in the new feed design meets WCAG 2.1 AA, so you can keep the layout your team prefers, including the slider.
Grid, list and masonry—these layouts have no motion, so they need no extra settings.
Slider themes—when Auto Play is on, the slider shows a Pause/Play button in a row below the slides, so visitors can stop the motion at any time. The slider also holds still while a visitor hovers over it or moves keyboard focus inside it. Visitors who have turned on reduced motion in their device settings see no autoplay at all.
Older embed code—the old Juicer embed's slider can be flagged in an accessibility audit for an invalid ARIA role on the feed list and no visible focus outline on the arrows. The new feed design fixes both. To check which one your website runs, open your page's source (right-click the page and choose View Page Source) and search for juicer. The old embed is a script from assets.juicer.io/embed.js, usually with an embed.css stylesheet and a juicer-feed list. The new embed is a single script from www.juicer.io/embed/, ending in embed-code.js. If you find the old one, switch the feed with Switching your feeds to the new Juicer Social design, then replace the code on your site as shown in Feed not loading or not reflecting your changes? Update your embed code.
AI designs—each one is unique to your feed, so it isn't audited like the standard layouts. If your website must comply, check the design before you publish it. See AI feeds: design your Juicer feed by describing it.
If you'd rather have no motion on the page at all, turn off Auto Play in the slider's settings, or choose one of the non-animated themes.
For ready-made designs built for specific uses, see How to use Premium themes in your Juicer feed.
Questions about Juicer Social's accessibility?
If you have a question about how Juicer handles a specific WCAG criterion, please contact us. On request, we can share our internal Voluntary Product Accessibility Template (VPAT).