Our commitment
Socialocca LLC builds tools people use to get work done. A tool nobody can operate is not finished, so accessibility is part of building it rather than something added afterwards.
We want everyone to be able to use socialocca.com and the apps we publish — including people who navigate by keyboard, use a screen reader or magnifier, rely on captions, or have asked their device to reduce motion.
The standard we work to
We target Web Content Accessibility Guidelines (WCAG) 2.1, Level AA — the benchmark referenced by the Americans with Disabilities Act in practice, by Section 508, and by the European Accessibility Act through EN 301 549.
This site is partially conformant with WCAG 2.1 Level AA. "Partially conformant" means most of the standard is met and some parts are not yet. We would rather say that plainly than claim otherwise — the specific gaps we know about are listed below.
We do not use an accessibility overlay or widget. Those products do not make a site conformant, and organisations representing blind users have advised against them. We fix the underlying code instead.
What we have done
Measures currently in place across the site:
- A "skip to main content" link, and a single
<main>landmark on every page. - Every image carries alternative text, with decorative artwork explicitly marked as decorative so screen readers pass over it.
- Full keyboard operation — every menu, dialog, filter and app link is reachable and usable without a mouse, with a visible focus indicator at every stop.
- Animation honours your system's "reduce motion" setting. With it on, looping and scroll-driven movement stops.
- Text and interface colours are measured against the backgrounds they actually appear on, not just in theory.
- Form fields have real labels that stay visible while you type, and results are announced rather than silently swapped in.
- Automated accessibility checks run on every change before it ships, so these do not quietly regress.
Known limitations
We are aware of the following and are working on them. If you hit something not on this list, please tell us — see below.
- Some decorative motion still loops. A few background animations run continuously without a pause control. They stop if your system is set to reduce motion.
- The island map is visual. The interactive map is a picture with buttons on it. Every app it shows is also listed as text on the Apps page, which is the fully accessible route to the same content.
- Heading levels skip in places. On a few pages a heading jumps a level, which can make navigating by headings less predictable.
- Some very small text. A handful of labels are set at 10–11px. They scale with browser zoom, but they are smaller than we would like.
- Third-party content. Embedded video players and scheduling tools come from other companies, and we do not control their accessibility. We will always give you another way to reach us.
Tell us about a problem
If something on this site is hard or impossible to use, we want to know. You will get a person, not a ticket queue.
- Use the "Report a bug or fix" button at the bottom of any page. No account needed, and you do not have to leave your name.
- Email team@socialocca.com.
- Text or call (570) 266-8286.
We aim to reply within 5 business days. Please tell us the page, what you were trying to do, and what happened — and, if you can, what you were using (browser, screen reader, phone or computer). Any detail helps; a vague report is still better than silence.
If we cannot fix something quickly, we will tell you when we expect to, and offer another way to get what you needed in the meantime.
How this was assessed
This statement reflects a self-assessment carried out in August 2026. It combined automated testing (axe-core against every key page, running in our build pipeline), static analysis of the code, direct measurement of colour contrast against real rendered backgrounds, and manual keyboard testing.
We have not yet commissioned an independent third-party audit or formal testing with assistive-technology users. Both would tell us things our own testing cannot, and we would rather say so than imply a level of assurance we do not have.