Skip to main content

Accessibility

This page describes what's actually shipped today. We have not completed a formal WCAG 2.1 AA audit, do not publish a VPAT, and have not done structured testing with VoiceOver, NVDA, or TalkBack. If you hit a barrier, please report it — see Reporting issues below.

What's in place​

Keyboard navigation​

  • Standard browser focus traversal works throughout the app.
  • Interactive elements (buttons, menu items, links) are reachable via Tab.
  • Modals, dropdowns, and dialogs use the shadcn/ui primitives, which include focus trapping and Esc to close.
  • One global shortcut is wired: Cmd / Ctrl + Shift + P toggles the pin on the currently focused sidebar nav row. See Keyboard shortcuts.

Reduced motion​

GreekManage respects the OS-level prefers-reduced-motion setting. When it's on, page transitions and entrance animations collapse to instant.

There is no in-app toggle for this — set it at the operating-system level:

  • macOS: System Settings → Accessibility → Display → Reduce motion
  • iOS: Settings → Accessibility → Motion → Reduce Motion
  • Windows: Settings → Accessibility → Visual effects → Animation effects (off)
  • Android: Settings → Accessibility → Color and motion → Remove animations

Dark mode and contrast​

A dark theme is available via the theme toggle in the header. Use whichever has better contrast for your eyes. The active palette is documented in the brand style guide.

Text scaling​

Text uses relative units, so browser zoom (Cmd / Ctrl + +) and OS text-size settings both scale the interface.

Captions in events​

Events that include video meetings (Zoom, Google Meet, etc.) inherit those platforms' captioning features. GreekManage does not add captions to external streams.

What's not yet in place​

To set accurate expectations, these are things this page used to claim and that do not currently exist:

  • No Accessibility tab in account settings. The toggles described in earlier versions of this page (reduce motion, high contrast, larger touch targets, disable shortcuts, reading-optimized typography) are not implemented.
  • No published WCAG conformance statement and no VPAT.
  • No structured testing with VoiceOver, NVDA, or TalkBack. Screen readers may work for parts of the app and stumble on others; we have not validated either way.
  • No skip-to-content link in the global header.
  • No accessibility@greekmanage.com mailbox. Use the in-app feedback path described below.

If any of these matters to your chapter or org, let us know — the priority order is driven by real reports.

Mobile​

The native iOS and Android apps are Capacitor wrappers around the same web frontend, so the same caveats apply. iOS VoiceOver and Android TalkBack will read standard web semantics but have not been specifically tuned for.

Biometric unlock (Face ID / Touch ID on iOS, fingerprint on Android) is available as an alternative to typing your password each launch. See Mobile app.

Reporting issues​

The most reliable way to report an accessibility barrier today:

  1. Open the chat widget (bottom-right floating button on any page).
  2. Switch to the Feedback tab.
  3. Describe what you were trying to do, what happened, and the assistive technology you were using (screen reader, magnifier, switch control, etc.) plus your browser and OS.

Platform admins triage feedback and route accessibility reports back to engineering. There is no public-facing accessibility email at this time.

Last verified against v0.62.1 (2026-05-10).