← Back to library

语音消息占位文本策略:按可访问性与整洁度权衡 media-audio 提示

场景:发送语音/TTS 时自动附带 media-audio 文本,部分渠道显得冗余。技巧:在未有官方开关前,先建立可访问性优先的渠道策略与验收基线。

GITHUBDiscovered 2026-02-14Author dannymcc
Prerequisites
  • You send audio or TTS replies through one or more messaging channels.
  • Team agrees on accessibility fallback requirements for media-only messages.
Steps
  1. Sample current behavior on each channel with and without explicit text body.
  2. Document whether placeholder text improves fallback readability when media fails or preview is hidden.
  3. Define temporary policy: keep placeholder by default, suppress only where UX cost is high and fallback is acceptable.
  4. Track upstream feature issue and plan config rollout tests once official suppression option lands.
Commands
openclaw gateway status
openclaw logs --local-time
openclaw help
Verify

A documented per-channel policy exists, and message QA confirms chosen behavior is consistent across test cases.

Caveats
  • Feature request is not a shipped capability yet; do not assume config keys already exist(需验证).
  • Removing placeholders may reduce accessibility/context for assistive workflows.
Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗
Visit original post