Accessibility

Last reviewed October 3, 2026

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA on madcoolsocial.com. We check it with automated testing (axe-core, WCAG 2.2 AA rules), contrast and touch-target measurements, and a keyboard pass, at desktop and phone widths.

What the latest review covered

• The home, pricing, playbook and live trends pages, the six legal pages and this page, at 1440px and 390px wide, in each of the three display modes the switch in the corner offers: Signal, Still and Mono. The Signal chat panel was checked open.
• Text contrast, including text over images and gradients, measured on the colours actually painted; links inside text that are told apart by more than colour; touch targets of at least 24px; a skip link to the main content; page landmarks and headings; and keyboard focus, including that neither the cookie notice nor the controls fixed in the bottom corners hide what has focus.
• Motion: when your device asks for reduced motion, those pages run no animation. The live trends ticker has a pause button, and the Still and Mono modes stop the background animation and the moving parts of the navigation.
• The page-not-found page, at the same two widths and in the same three display modes, was checked with automated testing (axe-core) only.

Known limitations

• On a phone, in the Signal and Still modes, the small line of text above the home page headline runs over the background artwork, where part of it falls below the contrast requirement.
• In the Mono mode, the sentiment and momentum labels on the live trends page and the text of a selected trends filter fall below the contrast requirement, and so, narrowly, does the email field on the Business plan card.
• On the live trends page, a link in the ticker can sit under the ticker’s pause button when it takes keyboard focus.
• The signed-in app at app.madcoolsocial.com was not part of this review.

Report a barrier

If something on this site is hard to use with your setup, email hello@madcoolsocial.com with the page address and what happened.