Karsenics Accessibility Statement
Effective Date: October 21, 2026 · Last Updated: October 21, 2026
Karsenics builds software for Pride organizations, civic festival committees, and community groups. The people who register through it include disabled exhibitors, disabled volunteers, and disabled parade participants. Accessibility is not a compliance item for this company, it is the audience.
1. What we are working toward
Karsenics works toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA across karsenics.com and the Karsenics platform. That includes participant registration, volunteer signup, the document portal, the public event map, check-in, and the administrative console organizations use to run their events.
2. Where we are
In October 2026 we tested the platform and this website ourselves, against every WCAG 2.2 Level A and AA success criterion. This was our own testing, not an independent audit. We plan to add an outside review, and we will update this statement when we do.
Here is what we found. The platform fully meets most of the criteria. Four are only partly met, and all four are in one place: the map editors organizers use to lay out booths and the parade. Those editors still need a mouse, a trackpad or touch for a few drawing steps (see section 5). Nothing participants use is affected. On karsenics.com, our testing found no remaining WCAG 2.2 Level AA failures.
Every result, criterion by criterion, is in our Accessibility Conformance Report, written in the industry's standard VPAT format. You can read it on the web or download it as a PDF.
3. How we tested
- Automated checks on every release. Every public page and every part of the administrative console is checked against the WCAG 2.2 Level A and AA rules before a release can ship. The same checks run on karsenics.com.
- Keyboard. Every screen was used with a keyboard alone, with no mouse.
- Screen reader. We worked through a 45-step script with VoiceOver on a Mac, covering registration, the booth map, the public pages, the administrative console, and this website. No problems were found.
- Contrast, zoom, and spacing. We measured text contrast from the screen, zoomed pages to 200 percent, narrowed them to phone width, and widened letter, word, and line spacing to the levels WCAG sets. We fixed every place where text was cut off.
- Problems fixed first. Everything our testing found was fixed before we published our results, except the map editor steps in section 5.
4. What we build for
- Keyboard access. Every interactive element reachable and operable without a mouse, with a visible focus indicator, and a "Skip to main content" link on every page.
- Screen readers. Semantic headings and landmarks, labeled form fields, errors tied to the field they are about, and announced status changes such as "Saved."
- Color and contrast. Text meeting WCAG AA contrast ratios, and no information conveyed by color alone. Booth status on every map is shown with a pattern and a word as well as a color.
- Maps. Every booth map has a List view that gives every booth, its status, and a full-size button to choose it, so nobody has to use the picture.
- Text sizing and spacing. Content usable at 200 percent zoom and with wider text spacing, without loss of content.
- Forms. Clear labels, a note saying which fields are required, inline error messages tied to their field, and no reliance on placeholder text as a label.
- Motion. Respect for the reduced-motion browser setting, and a pause button on any clip that plays on its own.
- Time limits. No session timeout that would cause a registrant to lose a partly completed registration.
5. Known limitations
| Area | Limitation | Workaround | Target |
|---|---|---|---|
| Organizer map editors | Placing a new booth or place pin, drawing a zone, a grid of booths, or the parade route and lanes, setting the map's scale, and measuring still need a mouse, a trackpad or touch. The booth editor's pins are smaller than 24 pixels. | Karsenics draws an organization's maps for it on request. Once a map is drawn, everything on it can be selected, moved, and edited from the keyboard. | Q2 2027 |
| Payment and e-signature pages | Card and bank payments are entered on Stripe's own page, and electronic signatures, where an organization uses them, on BoldSign. Karsenics does not control those pages. | If you cannot complete one of these steps, contact us and we will help you finish your registration another way. | Ongoing |
| Organization-supplied content | Map artwork, uploaded PDFs, logos, and the wording of custom questions are supplied by the organization and are outside Karsenics' control. | Every booth map has a text List view. Ask the organization for a document in another format, or ask us and we will help. | Ongoing |
| Printed packets and reports | Packets, rosters, signs, and printed reports are built for paper and were not tested as web pages. | Ask the organization, or us, for the same information in another format. | Ongoing |
6. The Accessibility button
Every page of the platform and of this website has an Accessibility button in its header. It lets you make text larger, raise contrast, widen spacing, underline every link, switch to an easier-to-read font, stop animations, and show a stronger focus outline. Your choices are saved in your browser on that device.
The button is an extra for comfort, not a compliance tool. It does not make anything conform to WCAG, it does not replace the screen reader, magnifier, or browser settings you already use, and none of the results in section 2 depend on it. Our pages are built to work without it.
7. What organizations are responsible for
Karsenics supplies the software. The organization running an event is responsible for the accessibility of its own content and of the event itself, including the artwork it uploads, the wording of its custom questions, any PDF it links, and the physical accessibility of its venue. Organizations that receive public funding may have their own legal obligations, including under the Americans with Disabilities Act and Section 504. Karsenics does not assess or advise on those.
8. Tell us when something does not work
This is the part that matters most. If any part of karsenics.com or the platform is not usable for you, email hello@karsenics.com with the subject line "Accessibility." Tell us the page, what you were trying to do, and what assistive technology you were using if you know it.
Our commitment: we acknowledge within two business days, tell you within ten business days what we found and when we expect to fix it, and offer an alternative way to complete what you were doing in the meantime. If you are trying to register for an event and cannot, tell us and we will get you registered while we fix the underlying problem.
9. Formal complaints
If you are not satisfied with our response, email legal@karsenics.com and it will be reviewed by the company's president. We do not require you to exhaust this step before pursuing any other remedy.
Karsenics PBC · hello@karsenics.com · 3120 Southwest Fwy, Ste 101, PMB #803188, Houston, TX 77098-4520
© 2026 Karsenics PBC. All rights reserved.
