Accessibility Notice

Techxtreme Digital Studio wants OutreachOS at https://outreachos.techxtreme.me to be usable by as many people as possible — including people who use keyboards, screen readers, zoom, or motion preferences.

We aim to follow the spirit of WCAG 2.2 Level AA for public pages and core product flows. This page is an honest status notice, not a formal third-party conformance audit or certification.

• Structure — headings, landmarks, and labeled controls on main screens (dashboard filters, tables, auth forms, legal pages).
• Keyboard — interactive controls are meant to be reachable and operable without a mouse; focus styles use visible rings on buttons and inputs.
• Names & roles — meaningful aria-label / visible labels on search, filters, pagination, import/export, and similar chrome.
• Motion — animations and UI sound respect prefers-reduced-motion where we control them.
• Text alternatives — brand and key UI imagery carry alt text or accessible names; decorative chrome is kept out of the way where practical.
• Forms — signup, login, username, and settings flows use labeled fields and error messaging tied to the relevant inputs.

OutreachOS uses a sketchbook-style UI (paper texture, doodle borders, sticky notes). That look can create trade-offs:

• Some decorative borders and marker colors may sit close to the edge of comfortable contrast, especially on busy backgrounds.
• Dense data views (lead tables, vector vault graph) are harder for screen-reader and small-viewport use than simple forms. We keep adding labels and structure, but they are not as simple as a plain document.
• Dragging sticky call-script pads is mouse/pointer oriented; editing/saving scripts remains available without dragging.
• Demo tutorial overlays highlight regions of the UI; if a step feels stuck, you can skip the tour.
• Third-party pieces (Supabase Auth / Google sign-in, hosting on Vercel) follow their own accessibility practices outside our full control.

We build and test primarily in current evergreen browsers (Chrome, Firefox, Safari, Edge) on desktop and common mobile viewports. We use automated checks (including jest-axe in our test suite) on key components; that does not replace manual assistive-tech testing.

If you rely on a specific browser + screen reader combination and hit a wall, tell us — that report helps more than a generic “make it accessible” request.

Email techxtremebuisness@gmail.com with:

• The page or flow (URL if you have it)
• What you were trying to do
• What went wrong
• Device, browser, and assistive tech (if any)

We read these and prioritize fixes that block sign-in, import, or core vault use. We may not fix every visual preference immediately, but we will not ignore a real barrier silently.

Privacy Policy · Terms of Service · Cookie Policy · Acceptable Use