Accessibility

Last updated: October 14, 2026

SFomo (sf-venues-review.pages.dev) is built and operated by whatsupin.ai. We want everyone to be able to find events here, including people who use a keyboard, a screen reader, magnification, voice control or other assistive technology.

Our target

We aim for the site to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. In practice that means:

• every control can be reached and used with a keyboard, with a visible focus ring, and menus, filters and dialogs close with Escape and hand focus back;
• buttons, inputs and icons have names a screen reader can announce, and the page has a sensible heading and landmark structure;
• text meets a 4.5:1 contrast ratio (3:1 for large text and control outlines) in both the light and the dark theme;
• the site works at 200% zoom and on screens as narrow as 320 pixels without sideways scrolling, and animations stop when your system asks for reduced motion.

Each change to the site is checked with automated accessibility tests (axe-core) at desktop and phone sizes in both themes, plus a keyboard check of the menus, filters, event details, share and feedback dialogs, the tour and the map.

Known limitations

We know about these gaps and are working on them:

• Map (beta). The map is a visual extra built on Leaflet and OpenStreetMap. It can be panned and zoomed with the keyboard, but its pins can’t be reached with the keyboard or a screen reader yet. Every event on the map is also in the Cal and List views, which work with both.
• Calendar grid on small screens. The Cal view packs a week into a small space. If it is hard to read at high zoom, the List view shows the same events one per row with larger text.
• Event details come from other sites. Titles, descriptions and links are copied from public listings. We can’t fix the accessibility of the organizer’s own ticket or event pages that each listing links to.
• Event rows hold a button. Each event is a link to its listing with a small “Save or add to calendar” button inside it, so some screen readers read that button’s name as part of the link. A keyboard user reaches the row, then the button, with Tab.
• Emoji as icons. Some labels use emoji (for example 📍 for a place or 🧒 for kids’ events) next to text. Screen readers may read the emoji’s name before the text.

Tell us about a barrier

If something on SFomo doesn’t work for you, or you need an event’s details in another format, contact us at admin@whatsupin.ai. You can also use the anonymous feedback box on the main page (leave an email if you’d like an answer). Please tell us the page, what you were trying to do, and the browser and assistive technology you use, if any.

We read every message, and accessibility problems go to the front of the line. We’ll reply as soon as we can and tell you what we’re doing about it.

Technical details

The site is plain HTML, CSS and JavaScript, built for current versions of Chrome, Edge, Firefox and Safari on desktop and phone; the automated checks run in Chromium. It doesn’t need an account, and nothing about accessibility settings is stored or sent anywhere.