Accessibility Policy

Last reviewed October 1, 2026

Our Commitment

simpler.social is meant for everyone, including people who use screen readers, keyboards, voice control, magnification, or any other tool to get around the web.

Our goal is to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Those guidelines are the most widely used standard for making websites work for people with disabilities.

We're a small team and we won't get everything right. When we miss something, we want to hear about it, and we'll fix it.

What We Do

We build accessibility into the site from the start instead of patching it on later. That means:

• Keyboard access. You can sign up, log in, reset your password, pick your tags, change your settings and delete your account without a mouse. You can always see where your keyboard focus is, and a "Skip to Content" link lets you jump past the navigation.
• Screen reader support. Pages use proper headings, labels and landmarks, so assistive technology can describe what's on the screen and how to move through it. When you pick or remove a tag, it's announced as saved or removed.
• Readable text. Text and background colors meet WCAG contrast levels in both light and dark mode, and so do the edges of form fields. Pages reflow to fit narrow screens and high zoom without sideways scrolling.
• Image descriptions. Images that carry meaning have text alternatives, and decorative ones are hidden from screen readers. When photo uploads arrive, we'll ask members to describe their photos.
• Clear forms. Every field has a label. Error messages say what went wrong and how to fix it, they're linked to the field they're about, and focus moves to the first problem when a form comes back with errors.
• Nothing that relies on color alone. Selected tags show a check mark, errors are written out, and tags waiting for review are labeled for screen readers as well as shown with a dashed border.
• Less motion. If your device is set to reduce motion, we turn off animations and transitions. The small saving indicator still spins, slowly, so you can tell something is happening.
• Works on small screens. The layout adjusts to phones and tablets, in either orientation.
• Light and dark mode. The site follows your device's setting, and you can switch with the button at the top of every page.

Where We Fall Short

Some parts of the site aren't where we want them yet, and we'd rather say so up front.

• Screen reader testing. We've tested every page with automated checks and by keyboard, but we haven't yet finished hands-on testing with VoiceOver and NVDA. Until we do, there may be rough spots we haven't found.
• The date of birth field. It uses your browser's built-in date picker, which some screen readers handle awkwardly. You can type the date instead of using the calendar.
• Adding your own tag. When you add a tag that isn't on the list, the page reloads and the confirmation appears at the top of the page, away from where you typed.
• What members post. As posting and photos arrive, we won't be able to guarantee that every photo has a description, or that every link and video members share is accessible. We'll prompt for descriptions and look for ways to do more.
• Outside services. Cloudflare protects the site from automated attacks and may occasionally show a "checking your browser" page. We don't control how that page is built.

If one of these gets in your way, tell us. We'll find another way to get you what you need while we work on a fix.

Tell Us If Something Doesn't Work

If you hit a barrier on simpler.social, email [email protected]. A real person reads that inbox, and we'll reply within 5 business days.

It helps if you can tell us:

• The page or feature where you ran into trouble
• What you were trying to do
• The device, browser and any assistive technology you were using

You don't need all of that to write in. "I couldn't do X" is enough for us to start.

If you need something from the site in the meantime, like help setting up your account or changing your tags, say so in your email and we'll take care of it for you.

How We Check Our Work

We test the site with automated tools (axe), by hand with a keyboard, and at narrow screen widths, in both light and dark mode. Hands-on screen reader testing is next. We run these checks before we release a new feature and again every 6 months.

When someone reports a problem, it goes on our fix list with everything else we're building. Barriers that stop someone from using a core feature go to the top.

This policy was last reviewed on October 1, 2026.