Accessibility & Inclusivity

Overview

Accessibility and inclusivity are foundational to trustworthy AI experiences.

All AI-driven interactions within OneDesign must be usable, understandable, and respectful for people with diverse abilities, languages, and needs.

Accessibility is not an add‑on — it is a core requirement at every stage of AI design.

This section defines the minimum accessibility and inclusivity standards for AI features across OneDesign.

Principles

Contrast ratio: WCAG AA minimum
Keyboard navigation for all AI actions
Screen reader labels for AI-generated content
Localization support for tone and phrasing

01 - Contrast ratio

Standard: WCAG 2.1 AA minimum contrast requirements.

Guidelines

  • Text and essential UI elements must meet 4.5:1 contrast against background colors.
  • Large text (≥18pt or ≥14pt bold) may use 3:1 contrast, but higher contrast is preferred.
  • AI indicators (badges, highlights, warnings) must remain legible in light and dark themes.

Design implication

  • Avoid low-contrast pastel backgrounds for AI panels.
  • Use neutral, high-contrast styles for AI-generated content indicators.

Example:

✅ AI summary text on a white or dark neutral background with sufficient contrast

❌ Light gray text on a light background that reduces readability

02 - Keyboard navigation

Goal: Ensure full operability without a mouse.

Guidelines

All AI actions must be keyboard-accessible, including:

  • Opening AI panels or widgets
  • Sending prompts
  • Navigating suggestions and responses
  • Providing feedback (thumbs up/down, report issue)

Maintain a logical and predictable focus order. Visible focus states must be clearly distinguishable.

Design implication

  • Do not rely on hover-only interactions.
  • Input fields, buttons, and links must be reachable via Tab, Enter, and arrow keys.

Example:

✅ User can open the AI assistant, submit a prompt, and give feedback using only the keyboard

❌ Feedback buttons only accessible via mouse click

03 - Screen reader support

Goal: Make AI-generated content understandable with assistive technologies.

Guidelines

  • Clearly label AI-generated content (e.g., "AI-generated response").
  • Use ARIA live regions to announce:
    • New AI messages
    • Streaming content updates
    • Error or warning messages
  • Provide text alternatives for non-text outputs (charts, visual summaries).

Design Implication

  • AI responses should be announced without interrupting user navigation.
  • System messages must be distinguishable from user or AI messages.

Example:

✅ Screen reader announces "AI response received" before reading content

❌ AI output appears silently and is not detected by assistive tools

04 - Localization & inclusive language

Goal: Ensure AI communication respects linguistic and cultural diversity.

Guidelines

Support localization for:

  • Language
  • Date and number formats
  • Tone and phrasing

Avoid culturally specific metaphors or idioms unless localized properly. Ensure tone guidance (politeness, formality) adapts across regions.

Design implication

  • AI tone should feel natural and respectful in all supported languages.
  • Avoid assuming cultural context or professional norms.

Example:

✅ Localized AI messages that align with regional language expectations

❌ Literal translations that sound unnatural or exclusionary

Do / don't summary

Do

  • Design every AI interaction to be usable without vision, mouse, or hearing.
  • Clearly identify AI-generated content for assistive technologies.
  • Test AI features with screen readers and keyboard-only flows.

Don't

  • Use color alone to communicate AI state or importance.
  • Hide AI functionality behind hover or gesture-only actions.
  • Assume one tone or language suits every user.

Why this matters

  • Builds trust with a broader user base
  • Reduces frustration and cognitive load
  • Ensures compliance with accessibility standards
  • Reflects One's commitment to responsible, human-centered AI