Accessibility is part of the product

We target WCAG 2.2 AA practices for new experiences and prioritize the workflows that affect account access, purchasing, selling, payments, support, and safety. Accessibility is reviewed during feature design, implementation, and release validation.

• Keyboard navigation and visible focus states for interactive controls.
• Semantic headings, landmarks, labels, status messages, and accessible names.
• Responsive layouts that remain usable with zoom and smaller screens.
• Meaningful alternative text for informative images and captions or transcripts where media supports them.
• Color is not the only signal for status, errors, required fields, or actions.

Use your browser or operating-system preferences for zoom, reduced motion, contrast, text size, screen readers, and captions. Within the app, use Settings to review notification, media, language, and display preferences where available. Some third-party integrations may expose their own accessibility controls.

If a page, document, integration, or workflow creates a barrier, tell us what you were trying to do, the page or feature, your assistive technology or browser if relevant, and a way to follow up. We will route the request to product support and prioritize blockers that prevent access to essential services.

accessibility@kingsideaconnections.org · We aim to acknowledge accessibility reports within two business days.

Some externally hosted payment, identity, map, video, and Microsoft experiences are provided by third parties and may have separate accessibility behavior. We document and address issues within our control, provide an alternate route where practical, and welcome specific reports so we can improve the integration experience.