Accessibility Settings Hub & Assistive Features App Store Listing in Simplified Chinese — 辅助功能, Accessibility Shortcut & zh-Hans Copy

Who this is for

Western indie iOS developers — US, UK, EU, Canada, Australia — whose product page prominently markets the Accessibility settings hub and multiple assistive features together:

• Accessibility hub home — Settings → Accessibility screenshot frames showing the feature grid buyers configure before using your app
• Accessibility Shortcut — triple-click Side or Home button to toggle VoiceOver, AssistiveTouch, Reduce Motion, or other assistive features
• Per-App Settings — customize accessibility behavior per installed app, shown on gallery frames when your listing claims app-specific assistive tuning
• AssistiveTouch & Guided Access — floating assistive menu and single-app lock marketed alongside other hub bullets — not as the only lead feature
• Display & Text Size and Reduce Motion — typography and motion settings referenced on screenshots when your app respects system accessibility preferences
• Voice Control & Switch Control as hub bullets — listed on Accessibility hub screenshots when your product page markets hands-free or switch-based input alongside other assistive claims
• Spoken Content entry points — Speak Screen, Speak Selection, Typing Feedback, Announce Calls, or Announce Notifications mentioned as one Accessibility row when your gallery shows the Spoken Content section — not a Speak Screen-first, Typing Feedback-first, Announce Calls-first, or Announce Notifications-first listing

You finished the en-US listing. The zh-Hans row exists or is in progress, but China buyers still see English searchable fields and English Accessibility-themed screenshot captions. You need paste-ready Connect storefront text — not a contractor to implement UIAccessibility APIs or perform App Review accessibility audits.

If your hero story is VoiceOver screen reader support only, see VoiceOver listing (zh-Hans). If you market Magnifier close-up zoom, see Magnifier listing. If users type custom phrases to speak aloud, see Live Speech listing. If Speak Selection selected-text read-aloud is the lead, see Speak Selection listing. If Typing Feedback spoken keyboard feedback is the lead, see Typing Feedback listing. If Announce Calls Siri caller-name speech is the lead, see Announce Calls listing. If Announce Notifications Siri notification read-aloud is the lead, see Announce Notifications listing. If Dim Flashing Lights video flash dimming is the lead, see Dim Flashing Lights listing. If Auto-Play Message Effects iMessage effect autoplay is the lead, see Auto-Play Message Effects listing. If Speak Screen full-page read-aloud is the lead, see Speak Screen listing. If the entire China page is still English on every field, start with China App Store still shows English or the AppLocale product page.

Listing metadata vs accessibility engineering vs screenshot design

Accessibility-aware apps blur three workstreams indie teams merge:

• App Store Connect listing metadata — name, subtitle, keywords, description, promotional text, screenshot overlay captions on the zh-Hans row. AppLocale scope.
• UIKit / SwiftUI accessibility APIs — accessibility labels, traits, hints, VoiceOver rotor order, AXTraits configuration. Engineering scope — not AppLocale.
• Screenshot composition — device frames, Settings → Accessibility hub mockups, re-exporting PNGs with burned-in Accessibility Shortcut headlines. Design scope — AppLocale delivers caption lines you paste or hand to a designer.

This page covers the first bucket for Accessibility hub-centric product pages — the Settings → Accessibility home and multi-feature assistive listing claims, not deep VoiceOver engineering or single-feature Magnifier marketing.

Accessibility hub marketing is not VoiceOver, Magnifier, Live Speech, or Speak Screen

Accessibility-adjacent apps blur several shop guides indie teams conflate. AppLocale covers listing metadata only — hub-level assistive marketing on the product page:

• Accessibility hub & multi-feature assistive claims (this page) — Settings → Accessibility home, Accessibility Shortcut, Per-App Settings, and hub bullets like AssistiveTouch, Guided Access, Display & Text Size, Reduce Motion, Voice Control, Switch Control, and Spoken Content entry points when your gallery markets several surfaces together.
• VoiceOver & screen reader (different) — VoiceOver support, Works with VoiceOver, Accessible for VoiceOver, screen reader navigation badges as the lead story. See VoiceOver listing guide — not hub-grid copy.
• Magnifier & close-up zoom (different) — magnifying glass, reading glass zoom, flashlight magnifier for low vision. See Magnifier listing guide — not Accessibility hub home marketing.
• Live Speech & type-to-speak (different) — Live Speech, type-to-speak, speak typed text aloud in conversations. See Live Speech listing guide — not hub-grid Spoken Content entry points.
• Speak Selection, Speak Screen, Typing Feedback, Announce Calls & Announce Notifications (different) — selected-text speech, full-page read-aloud playback, spoken keyboard feedback while typing, Siri caller-name speech for incoming Phone and FaceTime calls, and Siri notification read-aloud through headphones or CarPlay. See Speak Selection listing guide, Speak Screen listing guide, Typing Feedback listing guide, Announce Calls listing guide, or Announce Notifications listing guide — not Accessibility Shortcut triple-click marketing.
• Dynamic Type only (different) — supports Dynamic Type, larger text, scales with system text size as the sole claim. See Dynamic Type listing guide — not full Display & Text Size hub marketing.
• Reduce Motion only (different) — respects Reduce Motion, fewer animations as the sole claim. See Reduce Motion listing guide — not full Accessibility hub grids.
• Vehicle Motion Cues only (different) — animated edge dots while riding in a moving vehicle, motion sickness cues, reduce car sickness on iPhone as the sole claim. See Vehicle Motion Cues listing guide — not global animation reduction or full Accessibility hub grids.
• Dim Flashing Lights only (different) — on-device detection and dimming of flashing or strobing lights in supported video and media — 调暗闪烁光线 as the sole claim. See Dim Flashing Lights listing guide — video flash dimming, not full Accessibility hub grids.
• Auto-Play Message Effects only (different) — iMessage bubble and full-screen message effect autoplay — 自动播放信息效果 as the sole claim. See Auto-Play Message Effects listing guide — Messages effect autoplay, not full Accessibility hub grids.
• AssistiveTouch-only (different) — floating home button and virtual AssistiveTouch menu as the lead. See AssistiveTouch listing guide — not multi-feature hub screenshots.
• Guided Access-only (different) — single-app lock and kiosk mode as the lead. See Guided Access listing guide — not hub-grid marketing.

Your screenshots may show Accessibility icons alongside Focus pickers or Control Center toggles. Listing copy should name the correct surface per frame — an Accessibility Shortcut sheet is not a VoiceOver rotor demo, not a Magnifier zoom frame, and not a Live Speech type-to-speak keyboard unless that is what the frame shows.

English Accessibility hub phrases China buyers still see

Common en-US marketing lines that leak onto the China product page when zh-Hans caption fields are empty or copy-pasted from the US gallery:

• Accessibility — generic badge on screenshot overlays showing Settings → Accessibility home
• Accessibility Shortcut — triple-click Side button setup left in Latin script on shortcut frames
• Per-App Settings — per-app accessibility tuning callout still English on customization frames
• AssistiveTouch — floating menu row left untranslated on hub grid screenshots
• Guided Access — single-app lock row still English on education or kiosk app galleries
• Display & Text Size — typography settings row left Latin on accessibility preference frames
• Reduce Motion — motion reduction row still English when wellness apps market vestibular-friendly UX
• Voice Control / Switch Control — hands-free or switch input rows left untranslated on hub screenshots
• Spoken Content — read-aloud section entry point still English when Speak Screen appears as one hub bullet

Chinese buyers searching for 辅助功能, 辅助功能快捷键, or 单 App 设置 still land on English-only overlays — that reads as an incomplete localization pass, not a bilingual accessibility-aware app.

EN → zh-Hans listing phrase examples (Accessibility hub scope)

Paste-ready zh-Hans should match how Chinese App Store readers describe iPhone Accessibility on the product page — not a word-for-word mirror of English Settings strings. AppLocale adapts these patterns to your English source:

• Accessibility → 辅助功能 — names the Settings hub buyers recognize (Settings → 设置 → 辅助功能)
• Accessibility Shortcut → 辅助功能快捷键 — triple-click Side or Home button shortcut marketing
• Per-App Settings → 单 App 设置 — per-app accessibility customization on hub or detail frames
• AssistiveTouch → 辅助触控 — floating assistive menu row on hub grid screenshots
• Guided Access → 引导式访问 — single-app lock row on education or kiosk marketing frames
• Display & Text Size → 显示与文字大小 — typography and display settings on preference screenshots
• Reduce Motion → 减少动态效果 — motion reduction row when your app respects system motion settings
• Voice Control → 声音控制 — hands-free voice navigation listed as one hub bullet
• Switch Control → 切换控制 — external switch input listed as one hub bullet
• VoiceOver → 旁白 — screen reader row when VoiceOver appears on hub grids; use the VoiceOver guide when screen reader is the lead story
• Spoken Content → 朗读内容 — Spoken Content section entry when Speak Screen or Speak Selection appears as one hub row

zh-Hans Accessibility captions can differ idiomatically from en-US overlays when the on-screen feature is the same — avoid mirroring comma-heavy English marketing onto tight screenshot art.

Why English Accessibility hub copy hurts on the China storefront

Productivity, education, wellness, and utility apps compete on the China App Store. Buyers evaluate product-page clarity before they configure assistive settings:

• Accessibility value buried in Latin script — English "Accessibility Shortcut" on zh-Hans title/subtitle frames signals the team did not finish China marketing
• Hub rows left untranslated — AssistiveTouch and Guided Access appear as raw English on hub grid screenshots when caption fields are empty
• Description mismatch — zh-Hans body copy mentions 辅助功能 while screenshot overlays still say "Accessibility"
• Search intent gap — subtitle and keywords may miss 辅助功能, 辅助功能快捷键, or 单 App 设置 terms buyers actually type
• Per-App Settings confusion — Per-App Settings left English while competitors show 单 App 设置 on the same frame type
• Voice Control left untranslated — hub bullets still Latin when inclusive-design buyers expect 声音控制
• Competitor contrast — native zh-Hans accessibility-aware apps in the same category show Chinese overlays; English badges look like an import

Better zh-Hans Accessibility hub marketing copy improves product-page clarity for China traffic — it does not replace UIAccessibility engineering, VoiceOver label audits, or Apple review decisions.

Common mistakes on zh-Hans Accessibility hub listings

• Only localizing title and description — screenshot overlays still say "Accessibility Shortcut" and "AssistiveTouch" on every hub frame
• Conflating with VoiceOver-only copy — screen reader paragraphs belong on the VoiceOver guide when VoiceOver is the lead, not generic hub-grid marketing
• Conflating with Magnifier or Live Speech — close-up zoom and type-to-speak badges need their own guides when those are the hero story
• Machine-translating "Per-App Settings" literally — awkward strings instead of idiomatic 单 App 设置 phrasing Chinese reviewers use
• Assuming accessibility-aware app = localized storefront — respecting Accessibility in the binary does not auto-fill Connect overlay fields
• English text burned into PNG exports — Connect caption fields are Chinese but the image file still embeds English Accessibility headlines (a design fix, not a metadata paste)
• Claiming every hub feature when you support one — zh-Hans copy promises Voice Control and Switch Control when your marketing only shows AssistiveTouch
• What's New still English after accessibility launch — see What's New in Simplified Chinese when Accessibility support shipped in a recent version

What good zh-Hans Accessibility hub listing copy looks like

Hub-centric listings name the iPhone Accessibility workflow in plain zh-Hans — not a word-for-word mirror of English brochure lines:

• Subtitle — one clause on assistive value: "支持辅助功能与单 App 设置" or "可通过辅助功能快捷键快速开启" — not vague "更易使用"
• Keywords — mix category terms with Accessibility intent (辅助功能, 辅助触控, 引导式访问); see Simplified Chinese keywords guide
• Description — short paragraphs for Accessibility Shortcut, Per-App Settings, AssistiveTouch, Guided Access, Display & Text Size, and Reduce Motion if you market them — mirror screenshot sequence
• Screenshot overlays — short lines naming what the frame shows: 辅助功能, 辅助功能快捷键, 单 App 设置, 辅助触控, 引导式访问, 显示与文字大小, 减少动态效果 — not "Accessibility Shortcut" pasted through machine translation
• Feature-accurate claims — when your gallery shows AssistiveTouch only, caption sheet lists 辅助触控 — not every row Apple ships in Settings
• Voice match — same 你/您 and punctuation habits as your other zh-Hans fields

For related system-app listing scopes when your gallery mixes surfaces, see contrast guides: Focus modes listing, Watch companion listing, Dynamic Island listing, Control Center listing, VoiceOver listing, and Magnifier listing — each covers a different lead story, not Accessibility hub grid marketing.

Connect checklist before you order Accessibility hub listing copy

1. Open App Store → Chinese (Simplified) — confirm the zh-Hans row exists; note which fields are still English
2. Audit Accessibility screenshot overlays — export English caption text per frame; list lines mentioning Accessibility, Accessibility Shortcut, Per-App Settings, AssistiveTouch, Guided Access, Display & Text Size, Reduce Motion, Voice Control, or Switch Control
3. Verify subtitle and keywords — do they mention Accessibility workflows in Chinese or still mirror en-US?
4. Check description bullets — assistive feature paragraphs may be English-only even when title is zh-Hans
5. Separate hub vs single-feature scope — if frames show VoiceOver rotor UI as the hero, confirm whether you need hub copy or VoiceOver copy (see VoiceOver guide)
6. Separate Magnifier or Live Speech scope — if frames show close-up zoom or type-to-speak keyboards, confirm whether you need hub copy or feature-specific copy
7. Plan re-export if text is burned in — Connect caption fields help only when overlays are editable text layers, not English baked into PNGs
8. Verify China in availability — Pricing and Availability includes China if the storefront should show zh-Hans copy

How this differs from VoiceOver, Magnifier, and engineering guides

Our screenshot captions guide covers overlay copy boundaries for any app gallery. Our VoiceOver guide covers screen reader marketing in depth — not hub-grid copy. Our Magnifier guide covers close-up zoom — not Accessibility home marketing. This page covers Accessibility hub marketing on listing metadata — name, subtitle, keywords, description, and overlay lines that sell Settings → Accessibility, Accessibility Shortcut, Per-App Settings, AssistiveTouch, Guided Access, Display & Text Size, Reduce Motion, Voice Control, Switch Control, and Spoken Content entry points:

• Accessibility hub marketing copy — not UIKit accessibility API or AXTraits engineering
• Multi-feature assistive listing claims — not VoiceOver-only or Magnifier-only deep guides
• Accessibility Shortcut and Per-App Settings vocabulary — not Live Speech type-to-speak or Speak Screen read-aloud lead copy
• Screenshot overlay lines when bundled — not screenshot PNG design or re-export

If the entire China page is still English, start with China App Store still shows English before ordering Accessibility hub-specific copy.

What AppLocale delivers

For one app on the zh-Hans row, paste-ready Simplified Chinese listing copy for Accessibility hub-marketing fields you specify:

• Title, subtitle, keywords, description — zh-Hans rewrite aligned with your English Accessibility hub positioning
• Promotional text — when bundled in your brief
• Screenshot overlay and caption lines — zh-Hans lines for frames showing Accessibility, Accessibility Shortcut, Per-App Settings, AssistiveTouch, Guided Access, Display & Text Size, Reduce Motion, Voice Control, Switch Control, and Spoken Content entry points
• English source alignment — when your en-US Accessibility copy also needs tightening, we note both sides in the deliverable
• 24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake

Human rewrite from your current English listing — not a machine translation dump. Default $79 scope targets listing metadata and Accessibility hub overlay lines; ask if you also need VoiceOver-first copy bundled — see the AppLocale product page.

What AppLocale does not do

• Does not write UIKit, SwiftUI, or React Native accessibility API code or configure AXTraits
• Does not perform VoiceOver audits, WCAG consulting, or App Review accessibility certification
• Does not implement AssistiveTouch overlays, Guided Access locks, or Voice Control handlers in your app
• Does not design, compose, or re-export Accessibility-themed screenshot PNG/JPEG assets
• Does not translate text burned into existing image files — only Connect caption fields and deliverable line sheets for your designer
• Does not localize in-app UI strings, Xcode catalogs, or the app binary
• Does not upload media or click Save for you in App Store Connect
• Does not guarantee App Store rankings, conversion lift, or download growth
• Does not manage Apple Search Ads, review-reply retainers, or ASO retainers
• Is not QuantRadar, not paid ads management, and not investment or legal advice
• Does not invent reviews, ratings, or traffic numbers

How it works

1. Confirm scope — which listing fields and Accessibility hub overlay lines need zh-Hans; whether VoiceOver-first or Magnifier frames are in scope
2. Checkout — pay $79 one-time on Stripe (link below). Seller: Fortune Insight, LLC.
3. Send intake — reply from the email on your Stripe receipt with your App Store listing URL, current English copy (especially Accessibility Shortcut, Per-App Settings, AssistiveTouch, Guided Access, and Display & Text Size lines), target locale (zh-Hans), and frame counts if screenshots are included
4. Receive files — within 24 hours, paste-ready zh-Hans listing copy arrives at your Stripe receipt email
5. Paste in Connect — enter fields on the zh-Hans row; hand overlay lines to your designer if text is burned into PNGs

Need the full listing row from scratch? Start at the AppLocale product page or China localization checklist.

FAQ

Does shipping accessibility support in my app auto-translate Accessibility hub marketing on the China storefront?

No. Accessibility behavior inside your app is an in-app feature — it does not fill App Store Connect localization rows. If zh-Hans fields are empty, the China product page falls back to en-US copy.

Why do Accessibility Shortcut and AssistiveTouch captions still show English on China?

Screenshot overlay lines are per localization. English Accessibility badges on the en-US gallery do not propagate to zh-Hans until you paste Chinese caption text into the Chinese screenshot set.

What do I send after AppLocale payment?

Your live App Store listing URL, current English listing fields, Accessibility hub screenshot overlay lines (Accessibility Shortcut, Per-App Settings, AssistiveTouch, Guided Access, Display & Text Size, Reduce Motion, Voice Control, Switch Control), target locale (zh-Hans), and any frame counts. Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.

How is this different from the VoiceOver, Magnifier, or Live Speech listing pages?

VoiceOver marketing covers screen reader support in depth. Magnifier covers close-up zoom. Live Speech covers type-to-speak. This page covers Settings → Accessibility hub grids and multi-feature assistive listing claims when your gallery markets several assistive surfaces together — not one feature as the sole hero.

How is this different from AssistiveTouch-only or Guided Access-only guides?

AssistiveTouch-only and Guided Access-only guides cover one feature as the lead story. This page covers hub-level marketing when Accessibility Shortcut, Per-App Settings, and multiple hub rows appear on the same product page.

Which zh-Hans terms fit Voice Control and Per-App Settings on screenshots?

Common patterns: 声音控制 for Voice Control hub bullets, 切换控制 for Switch Control, 单 App 设置 for Per-App Settings, and 辅助功能快捷键 for Accessibility Shortcut triple-click marketing. AppLocale matches phrasing to what your English source actually claims.

Can you implement UIAccessibility or VoiceOver engineering for my app?

No. We rewrite Connect listing metadata only. Accessibility API engineering in Xcode is outside AppLocale scope.

Will localized Accessibility hub copy improve Search ranking in China?

We do not guarantee keyword position or download growth. Apple indexes title, subtitle, keywords, and description for Search. Complete zh-Hans Accessibility marketing helps buyers who already landed on your product page understand assistive value.

How much does AppLocale cost?

$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.

What is AppLocale not?

Not UIKit accessibility engineering, not VoiceOver audits, not Magnifier or Live Speech or Speak Screen lead copy, not screenshot design, not ranking guarantees, not QuantRadar, and not investment or legal advice. We do not invent reviews, ratings, or traffic numbers.

AppLocale — zh-Hans Accessibility hub & assistive features listing copy for the China App Store

$79 one-time

Buy AppLocale on Stripe

Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and English Accessibility hub listing copy.
No ranking guarantees. Sold by Fortune Insight, LLC.

AppLocale product page