App Store Accessibility Nutrition Labels Listing in Simplified Chinese — zh-Hans Support for Accessibility Features Copy
Your iOS app already has Accessibility Nutrition Labels declared in App Store Connect — maybe a Support for Accessibility Features panel showing VoiceOver, Voice Control, Larger Text, Sufficient Contrast, Captions, Audio Descriptions, Reduced Motion, or related badges — and the US product page tells that story on screenshots and in the description.
Open the same app on the China storefront and buyers still land on an English product page: name, subtitle, keywords, description, and screenshot captions that read "VoiceOver support", "Works with VoiceOver", "Accessible", or "Built for accessibility" in Latin script.
Filing accessibility nutrition labels does not auto-fill a Simplified Chinese (zh-Hans) localization row.
AppLocale writes paste-ready zh-Hans listing copy for those Connect fields — aligned with what your Accessibility Nutrition Labels already disclose, without over-claiming "fully accessible" or WCAG certification on the storefront.
Operator guidance only — no ranking guarantee, not legal advice, not investment advice. Seller: Fortune Insight, LLC.
Western indie iOS developers — US, UK, EU, Canada, Australia — who:
Already completed the Support for Accessibility Features questionnaire and have accurate Accessibility Nutrition Labels showing in Connect — not looking for label filing help here
Market accessibility support, VoiceOver compatibility, inclusive design, or Support for Accessibility Features badges on the en-US product page and screenshot gallery
Ship a China-facing listing but the zh-Hans row is empty, machine-translated, or still English on accessibility-themed frames
Need paste-ready Connect storefront text — not a VoiceOver engineer, not a consultant to re-file accessibility labels, not a designer to re-export every screenshot from scratch
Accessibility Nutrition Labels vs zh-Hans listing copy — two different jobs
Teams assume filing accessibility nutrition labels covers storefront language. Connect actually separates compliance disclosures from marketing copy:
Support for Accessibility Features & Accessibility Nutrition Labels — structured accessibility-feature disclosures Apple renders in the Support for Accessibility Features section on the product page. You file these in App Store Connect under App Accessibility. They do not generate Chinese listing text.
In-app accessibility implementation — VoiceOver labels, Dynamic Type, contrast ratios, captions, and reduced-motion handling inside the binary. Engineering work — outside AppLocale scope.
Pricing and Availability → China — makes the app downloadable on the China App Store. Separate from language rows.
App Store tab → Chinese (Simplified) localization — independent row for title, subtitle, keywords, description, promotional text, screenshots, and caption lines. Empty or English here means China buyers see English fallback regardless of accessibility-label accuracy.
Accurate Accessibility Nutrition Labels and a localized China listing are both required when you sell on the China storefront — neither replaces the other. AppLocale covers how you describe accessibility on the product page in zh-Hans, not how you file the questionnaire or implement features in code.
Accessibility nutrition labels are not Privacy labels, VoiceOver guides, or single-feature pages
Accessibility-aware apps blur several shop guides indie teams conflate. AppLocale covers listing metadata only — accessibility marketing on the product page:
Accessibility Nutrition Labels & Support for Accessibility Features marketing (this page) — disclosure badges on the product page, accessibility summary overlays, and description lines about VoiceOver, Larger Text, Captions, Reduced Motion, and related features aligned with your filed labels.
App Privacy nutrition labels & data collection (different) — Privacy Details panel, data types collected, tracking disclosures. See Privacy nutrition labels listing guide — not accessibility-feature badges.
VoiceOver screen-reader listing copy (different) — marketing VoiceOver support, Works with VoiceOver overlays, and screen-reader buyer intent. See VoiceOver listing guide — focused on VoiceOver feature marketing, not the Connect Accessibility Nutrition Label filing system.
Individual accessibility feature guides (different) — Switch Control, Voice Control, AssistiveTouch, Larger Text, Hover Text, Assistive Access, Guided Access, Closed Captions, Audio Descriptions, Reduce Motion, Dim Flashing Lights each have dedicated listing guides for that single feature's marketing copy — not the App Store Connect Accessibility Nutrition Label disclosure panel.
Kids category / Made for Kids (different) — age-band phrasing and parental messaging. See Kids category listing guide — not general accessibility marketing.
HealthKit / Apple Health (different) — health data sync and metric labels. See HealthKit listing guide — not accessibility-badge copy on utility apps.
Incomplete localization rejection (different) — review rejection when zh-Hans fields are blank. See Incomplete zh-Hans rejection guide — diagnostic, not accessibility-specific copy.
Your screenshots may show accessibility settings UI alongside other features. Listing copy should name accessibility claims accurately per frame — a Support for Accessibility Features panel is not a Privacy Details mockup and not a Kids age badge.
What China buyers see when zh-Hans accessibility copy is missing
Accessibility-forward apps often lead marketing screenshots with Support for Accessibility Features panels, VoiceOver badges, or inclusive-design blurbs — surfaces where English system chrome and your marketing lines appear together:
English title and subtitle — app name and tagline still Latin script while competitors show native Chinese accessibility positioning
Untranslated accessibility badges — overlay lines like "VoiceOver support", "Works with VoiceOver", "Accessible", "Built for accessibility", or "Screen reader friendly" remain English on zh-Hans gallery frames
Accessibility value in English — description opens with US accessibility marketing ("Fully accessible with VoiceOver") that China readers skim past or misread
Keyword field still en-US — buyers search 旁白, 无障碍, 视障友好, or 辅助功能; an English-only keyword row misses China Search intent
Mixed page — Chinese description pasted once but screenshot captions and subtitle still English — reads unfinished next to localized competitors
Over-claiming in machine translation — stiff 翻译腔 that guarantees "100% accessible" or "WCAG AAA certified" when your Accessibility Nutrition Labels list partial support only
Better zh-Hans listing copy helps accessibility-conscious buyers understand your support claims before install. It does not replace accurate Accessibility Nutrition Label disclosures, in-app accessibility implementation, or Apple's review decisions.
Accessibility-specific listing copy — what translates differently
Accessibility-forward listings use vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese App Store readers evaluate support claims — not a literal paste of US marketing:
Product page vs Support for Accessibility Features panel
Your listing can summarize accessibility in buyer-friendly language — 支持旁白, 兼容更大字体, 提供字幕, 减少动态效果 — but must stay consistent with what Apple's Support for Accessibility Features section already shows from your Accessibility Nutrition Labels. AppLocale aligns storefront phrasing with your English claims and stated feature support; we do not contradict filed disclosures.
Avoiding "fully accessible" over-claims
US pages sometimes use "fully accessible", "WCAG AAA certified", or "100% VoiceOver compatible" when Accessibility Nutrition Labels still list partial or unsupported features. Chinese copy should use factual, defensible phrasing — not superlatives that invite review scrutiny or mislead buyers who compare listing text to the Support for Accessibility Features panel.
Subtitle and keyword packing
The 30-character subtitle and 100-character keyword field need accessibility-relevant search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 旁白, 无障碍, and 辅助功能 each signal different intent from generic productivity keywords.
Screenshot captions on accessibility frames
Gallery frames that show Support for Accessibility Features panels, VoiceOver badges, or inclusive-design blurbs need one-line zh-Hans captions — "支持旁白与更大字体" not "VoiceOver support" burned into the product page story.
Common mistakes on accessibility-themed zh-Hans listings
Assuming Accessibility Nutrition Labels localize automatically — Support for Accessibility Features filed in Connect; zh-Hans row never added or left blank
Only translating the description — subtitle, keywords, and VoiceOver screenshot caption lines still English
Contradicting filed Accessibility Nutrition Labels — listing says "fully VoiceOver accessible" when Connect shows VoiceOver as unsupported or partial
Promising WCAG certification in zh-Hans — absolute claims that do not match Support for Accessibility Features or invite App Review questions
Conflating listing copy with in-app accessibility engineering — description paragraphs are marketing copy, not substitutes for VoiceOver labels inside the binary
English accessibility badges on zh-Hans screenshots — Connect caption fields are Chinese but burned-in trust badges on PNG exports are still Latin
Expecting AppLocale to file Accessibility Nutrition Labels — questionnaire completion and label submission are outside listing rewrite scope
Confusing with Privacy Nutrition Labels — App Privacy data-collection disclosures are a separate Connect system; see Privacy nutrition labels guide
What's New still English after accessibility launch — see What's New in Simplified Chinese when accessibility features shipped in a recent version
Connect checklist before you order accessibility listing copy
Confirm China under Pricing and Availability — storefront enabled if you intend to sell there
Confirm Accessibility Nutrition Labels are filed — note which features Connect shows in Support for Accessibility Features; we align listing phrasing with your disclosures, we do not re-file labels for you
Open App Store → Chinese (Simplified) — note whether the zh-Hans row exists and which text fields are empty vs English placeholder
Export English accessibility marketing copy — current en-US title, subtitle, keywords, description, promotional text, and every screenshot overlay line ("VoiceOver support", "Works with VoiceOver", "Accessible", "Larger Text", "Captions")
List screenshot frames that show accessibility UI — note which gallery images show Support for Accessibility Features panels, VoiceOver badges, or inclusive-design blurbs so caption lines match frame order
Separate listing from in-app accessibility engineering — listing rewrite does not cover VoiceOver labels, UIKit accessibility APIs, or WCAG audit reports inside the binary
Plan caption re-export if text is burned into PNGs — Connect caption fields help when overlays are editable; English baked into image files needs design rework outside AppLocale
Paste-ready Simplified Chinese listing metadata rewritten from your English App Store copy, with Accessibility Nutrition Label-aware phrasing:
App name — up to 30 characters on the zh-Hans row
Subtitle — up to 30 characters; visible under the name in Search
Keywords — up to 100 characters in the hidden keyword field
Description — long listing body explaining accessibility support for China buyers
Screenshot caption lines — overlay text for frames showcasing Support for Accessibility Features panels, VoiceOver badges, or inclusive-design blurbs (send frame count and current English lines)
English alignment — voice consistent with your en-US page; we note both sides when English also needs tightening on accessibility claims
24-hour turnaround — delivered to the email on your Stripe receipt after checkout and intake
Human rewrite — not a machine translation dump. Character counts verified before delivery.
What AppLocale does not do
Does not file, submit, or update Accessibility Nutrition Labels or the Support for Accessibility Features questionnaire
Does not perform VoiceOver audits, edit UIKit or SwiftUI accessibility APIs, or implement accessibility in the binary
Does not provide WCAG consulting, accessibility certification, or compliance retainers
Does not file App Privacy nutrition labels or draft privacy-policy legal text
Does not advise on medical claims, HIPAA programs, or clinical data handling
Does not write Kids category or HealthKit listing copy — see those dedicated guides for category-specific scope
Does not design or re-export screenshot PNG/JPEG assets — caption line sheets only
Does not localize in-app accessibility strings, VoiceOver labels, or settings UI inside the app binary
Does not manage Apple Search Ads, Custom Product Pages, or ad campaigns
Does not write App Review replies or ongoing ASO retainers
Does not guarantee App Store ranking, accessibility-badge outcomes, or download growth in China or elsewhere
Is not QuantRadar, not paid ads management, and not investment or legal advice
Does not invent reviews, ratings, or traffic numbers
How it works
Confirm scope — zh-Hans listing fields plus accessibility-themed screenshot captions; Accessibility Nutrition Label filing stays on your side
Send intake — reply from the email on your Stripe receipt with your App Store listing URL, current English name/subtitle/keywords/description, screenshot caption lines (note which frames show accessibility UI), summary of which Accessibility Nutrition Labels you declared, and target locale (zh-Hans)
Receive files — within 24 hours, paste-ready zh-Hans fields arrive at your Stripe receipt email
Paste in Connect — App Store → Chinese (Simplified) → save → submit with your next version if needed
Does filing Accessibility Nutrition Labels auto-translate my China listing?
No. Accessibility Nutrition Labels and the Support for Accessibility Features panel control what Apple shows on the product page — they do not create or fill a Simplified Chinese localization row. Empty or English zh-Hans fields mean China buyers see en-US fallback.
What can zh-Hans listing copy say about accessibility vs what the nutrition label already shows?
Listing copy should summarize accessibility support in plain language aligned with your filed disclosures — without contradicting Connect or implying WCAG certification Apple does not grant. AppLocale rewrites from your English claims and stated feature support; we do not invent accessibility behavior.
Does AppLocale file or submit Accessibility Nutrition Labels?
No. We deliver Connect listing metadata copy only — name, subtitle, keywords, description, promotional text when included, and screenshot caption lines. Questionnaire filing, label submission, VoiceOver engineering, and WCAG consulting are outside scope.
How should zh-Hans listing copy avoid over-claiming accessibility?
Avoid absolute claims like fully accessible or WCAG AAA certified unless they match your Accessibility Nutrition Labels and actual product behavior. Use factual phrasing — 支持旁白, 兼容更大字体, 提供字幕 — that mirrors what buyers read in Support for Accessibility Features.
What character limits apply to zh-Hans accessibility listing fields?
App name and subtitle are each up to 30 characters on the zh-Hans row. The keyword field allows up to 100 characters. Description and screenshot caption lines have longer limits but accessibility claims should stay concise — especially subtitle and overlay lines on accessibility-themed frames.
What do I send after AppLocale payment?
Your live App Store listing URL, current English listing copy, screenshot overlay lines that mention accessibility (with frame order noted), a brief summary of which Accessibility Nutrition Labels you declared, and target locale (zh-Hans). Reply from the email address on your Stripe receipt — we deliver to that Stripe email within 24 hours.
Will zh-Hans accessibility copy improve China rankings?
We do not guarantee ranking, browse placement, or download lift. Complete zh-Hans metadata helps users who already find your page understand accessibility claims in their language — it is not a placement hack.
How much does AppLocale cost?
$79 one-time via Stripe checkout. No subscription. Seller is Fortune Insight, LLC.
What is AppLocale not?
Not Accessibility Nutrition Label filing, not VoiceOver engineering, not WCAG consulting, not App Privacy nutrition-label filing, not privacy-policy legal drafting, not Kids/HealthKit listing copy, not screenshot design, not binary localization, not Apple Search Ads, not ranking guarantees, not QuantRadar, and not investment or legal advice. We do not invent reviews, ratings, or traffic numbers.
AppLocale — zh-Hans listing copy for Accessibility Nutrition Label & Support for Accessibility Features apps
Delivered within 24 hours after Stripe payment. After checkout, reply from your Stripe receipt email with your App Store URL and English listing copy. No ranking guarantees. Sold by Fortune Insight, LLC.