Accessibility Zoom & Screen Magnification App Store Listing in Simplified Chinese — 放大 & 屏幕放大 zh-Hans Copy

Who this is for

Western indie iOS and iPadOS developers — US, UK, EU, Canada, Australia — who:

• Already ship or market an app whose buyers use Accessibility Zoom — system screen magnification, window zoom, full-screen zoom, zoom controller UI, follow-focus zoom, hover text, or Settings → Accessibility → Zoom setup walkthroughs on screenshots
• Market screen magnification, window zoom, full-screen zoom, zoom controller, follow-focus, hover text, or 放大 / 辅助功能放大 / 屏幕放大 / 窗口放大 / 全屏放大 / 放大控制器 / 跟随焦点放大 / 悬停文字 on the en-US product page and in screenshot galleries
• Finished zoom or magnification UX in the binary — not looking for UIAccessibility zoom plumbing, zoom controller implementation, follow-focus engineering, or Settings deep-link help here
• Enabled the China App Store but the zh-Hans row is empty, machine-translated, or still English on Zoom gallery frames
• Need paste-ready Connect text — not an engineer for zoom APIs, not a designer to re-export every screenshot from scratch

If your lead feature is Magnifier close-up camera zoom for reading physical objects — not on-screen UI magnification — see Magnifier listing (zh-Hans). If you market larger text and Dynamic Type rather than screen zoom overlays, see Dynamic Type listing (zh-Hans). If the entire China page is still English on every field, start with China App Store still shows English or the AppLocale product page.

Zoom engineering vs zh-Hans listing copy — two different jobs

Teams assume screen-magnification capability covers storefront language. iOS, UIAccessibility, and Connect actually separate zoom UI in the app from product-page copy:

• UIAccessibility zoom & magnification overlays — in-app or system-adjacent code that enlarges UI regions, renders zoom windows, or mirrors Accessibility Zoom behavior. Controls how magnification renders — does not generate Chinese listing text.
• Zoom controller & follow-focus implementation — engineering work for draggable zoom handles, focus tracking, and hover text popovers. Separate from the zh-Hans description paragraph that explains screen magnification value to buyers.
• Settings deep links & onboarding UI — custom flows that point users to Settings → Accessibility → Zoom. Listing copy should match what your gallery shows — a zoom controller demo is not a Magnifier camera viewfinder unless that is what the screenshot depicts.
• 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 zoom features in the app.

Working Accessibility Zoom flows in the binary and a localized China listing are both required when you sell on the China storefront — neither replaces the other. AppLocale covers how you describe screen magnification, window zoom, and zoom controller workflows on the product page in zh-Hans, not how you implement UIAccessibility zoom or Magnifier camera pipelines.

The Accessibility Zoom family on one product page — five related workflows

Low-vision and accessibility apps often mention one or more Zoom workflows on the same US product page. AppLocale covers all five on this single guide — paste-ready zh-Hans copy for whichever your screenshots and description already claim:

• Window zoom (窗口放大) — a movable magnification window that enlarges a region of the screen while the rest stays at normal scale. Gallery frames may show the zoom lens, resize handles, or "Window zoom" badges.
• Full-screen zoom (全屏放大) — entire screen scales up for low-vision reading. Screenshot overlays often show full-screen magnification demos or "Full-screen zoom" toggles.
• Zoom controller (放大控制器) — the on-screen handle users drag to pan the magnified view. Marketing art may highlight the controller pill, drag affordance, or zoom level slider.
• Follow-focus zoom (跟随焦点放大) — magnification tracks keyboard focus, text fields, or VoiceOver cursor position automatically. Caption lines may reference follow-focus behavior when your gallery shows it.
• Hover text (悬停文字) — enlarged text popover when the user holds on a label or link. Only include in zh-Hans copy when your English listing and screenshots already claim hover text — AppLocale does not invent features your US page does not show.

Your gallery may lead with a window-zoom demo on one frame and a zoom controller on the next. zh-Hans caption lines should name the correct workflow per frame — a magnification window is not a Magnifier camera feed, and follow-focus zoom is not Dynamic Type font scaling unless that is what the screenshot shows.

Accessibility Zoom listing copy is not Magnifier, Display Accommodations, Dynamic Type, or other accessibility surfaces

Accessibility apps blur several visual-assist surfaces indie teams conflate. AppLocale covers listing metadata only — Accessibility Zoom and screen magnification marketing on the product page:

• Accessibility Zoom & screen magnification (this page) — Accessibility Zoom, system screen magnification, window zoom, full-screen zoom, zoom controller, follow-focus zoom, hover text, and 放大 / 辅助功能放大 / 屏幕放大 on gallery frames and in description paragraphs.
• Magnifier & close-up camera zoom (different) — Magnifier, magnifying glass, reading glass zoom, near-distance camera magnification for reading physical objects. See Magnifier listing guide — camera viewfinder zoom is not on-screen UI magnification.
• Display Accommodations & color filters (different — contrast only) — color filters, invert colors, smart invert, and display zoom presets under Accessibility display settings. AppLocale does not maintain a Display Accommodations shop guide — do not conflate color-filter marketing with Accessibility Zoom screen magnification.
• Dynamic Type & larger text (different) — supports Dynamic Type, adjustable font size, scales with system text size. See Dynamic Type listing guide — typography scaling is not zoom overlay magnification.
• Reduce Motion (different) — respects Reduce Motion, fewer animations, motion-sensitive accessibility. See Reduce Motion listing guide — not screen magnification marketing.
• VoiceOver, Voice Control, Switch Control & Assistive Access (different) — screen reader navigation, spoken commands, external switch hardware, cognitive accessibility mode. See VoiceOver listing guide, Voice Control listing guide, or Switch Control listing guide — not visual zoom overlay copy.
• Music Haptics, Background Sounds & Hearing Devices (different — contrast only) — haptic music playback, ambient focus audio loops, MFi hearing-aid pairing. Not screen magnification marketing — each has its own shop guide when that is the lead story.

Your screenshots may show multiple accessibility surfaces in one gallery. Listing copy should name each claim accurately per frame — a zoom controller handle is not a Magnifier torch toggle, not a color-filter picker, not a Dynamic Type font-size slider, and not a VoiceOver rotor unless that is what the frame shows.

Apple system Accessibility Zoom vs your app's zoom story — listing honesty

Apple ships Accessibility Zoom in iOS Settings → Accessibility → Zoom that lets users magnify the screen with window zoom, full-screen zoom, a zoom controller, follow-focus tracking, and hover text. Third-party accessibility apps may offer companion demos, custom zoom workflows, or tutorials for enabling Zoom. AppLocale rewrites listing copy from what your US page already claims:

• If your app complements iOS Accessibility Zoom — zh-Hans copy can describe zoom setup walkthroughs, magnification demos, or works-with-Zoom badges your binary actually ships without claiming to replace Settings → Accessibility → Zoom unless your English listing already states that accurately.
• If your app ships custom magnification UI — description and screenshot overlays should name the zoom modes you deliver (窗口放大, 全屏放大, 放大控制器) in commerce-idiomatic Chinese, not generic "accessibility does everything" overclaims.
• Separate Zoom from Magnifier in copy — Magnifier uses the camera for close-up reading; Accessibility Zoom enlarges on-screen UI. Listing vocabulary must follow your English lead feature and gallery frames.
• If your US page overclaims — AppLocale aligns zh-Hans strings to your English source; we do not invent broader zoom scope than your screenshots and description support.

Clear zh-Hans copy helps low-vision buyers understand whether your app supports screen magnification, window zoom, or zoom controller workflows before install. It does not replace zoom implementation, UIAccessibility plumbing, or Apple's review decisions.

What China buyers see when zh-Hans Accessibility Zoom copy is missing

Accessibility apps often lead marketing screenshots with zoom overlays, magnification windows, controller handles, or follow-focus demos — surfaces where English marketing text appears beside zoom UI:

• Screenshot overlay badges — "Zoom", "Screen magnification", "Window zoom", "Full-screen zoom", "Zoom controller", "Follow focus", "Hover text" on gallery frames
• Description paragraphs — English value props ("Magnify any screen", "Built for low vision") that China readers skim past
• Subtitle and keywords — English-only rows miss China Search intent for 放大, 辅助功能放大, 屏幕放大, 窗口放大, or 全屏放大 when buyers filter for magnification apps
• Promotional text — 170-character field still pitching zoom in English above the description
• Mixed page — Chinese description pasted once but Zoom screenshot captions and subtitle still English — reads unfinished next to localized competitors
• Formal machine translation — stiff 翻译腔 that conflates 放大 (Accessibility Zoom) with 放大镜 (Magnifier camera) or 缩放 (pinch UI zoom) on store pages

Better zh-Hans listing copy helps low-vision purchasers understand your screen magnification story before install. It does not replace zoom code, controller UI implementation, or Apple's review decisions.

What AppLocale delivers for Accessibility Zoom apps on zh-Hans

This SKU is a listing rewrite scoped to Accessibility Zoom and screen magnification marketing — paste-ready fields you copy into App Store Connect:

• Name (title) — zh-Hans app name within Connect character limits when your English title does not signal 放大 or 屏幕放大 to China searchers
• Subtitle — concise benefit line that can reference screen magnification or zoom controller without stuffing raw English badge text
• Keywords — zh-Hans search terms buyers use for 放大, 辅助功能放大, 屏幕放大, 窗口放大, 全屏放大, 放大控制器, and 跟随焦点放大 in your category
• Description — long listing body with clear zh-Hans paragraphs on window zoom, full-screen zoom, zoom controller, follow-focus, and hover text features you already ship — without English-only Zoom jargon
• Promotional text — when you include the 170-character promo field in scope
• Screenshot overlay / caption lines — short zh-Hans text on gallery images that show zoom UI ("屏幕放大", "窗口放大", "放大控制器", "跟随焦点放大")
• English alignment — matching en-US field notes when both storefronts must stay consistent on magnification promises

We map deliverables to the fields you actually use. Send every English overlay line and description paragraph that mentions Accessibility Zoom, screen magnification, or zoom controller — we deliver counted strings that fit Connect limits. We rewrite what you already claim on the US page; we do not invent zoom features your app does not ship.

Accessibility Zoom-specific listing vocabulary — what translates differently

Screen magnification marketing on App Store pages uses vocabulary general utility guides rarely cover. zh-Hans copy should reflect how Chinese buyers describe Accessibility Zoom — not a literal paste of US marketing:

Accessibility Zoom vs Magnifier vs pinch zoom

US pages use "Zoom", "Screen magnification", or "Window zoom." China storefront copy often uses 放大, 辅助功能放大, 屏幕放大, 窗口放大, or 全屏放大 for system screen magnification — distinct from 放大镜 (Magnifier camera) and 缩放 (pinch-to-zoom in photo or map apps). AppLocale aligns phrasing with your actual feature scope.

Zoom controller vs generic magnifier language

Screenshot galleries often label the draggable zoom handle: "Zoom controller", "Drag to pan", or controller pill art. zh-Hans overlay lines may use 放大控制器 or 拖动控制器平移 — matching what your English gallery actually shows, not Magnifier torch or filter vocabulary.

Follow-focus and hover text

When your app or marketing claims follow-focus zoom or hover text, listing copy can reference 跟随焦点放大 or 悬停文字 — only on frames and in description paragraphs where those features are real. Do not keyword-stuff hover text if your gallery only shows manual window zoom.

Subtitle and keyword packing

The 30-character subtitle and 100-character keyword field need magnification search terms Chinese buyers type — see Simplified Chinese keywords & subtitle for field mechanics. Terms like 屏幕放大, 窗口放大, and 全屏放大 each signal different intent from Magnifier or Dynamic Type keywords.

Caption lines vs burned-in badges

Marketing screenshot overlays you control — "Screen magnification for low vision" headlines on gallery frames — are separate caption fields or burned-in PNG text. See Screenshot captions in Simplified Chinese for caption-field mechanics when overlays are editable in Connect.

Before / after — Accessibility Zoom listing phrases (en-US → zh-Hans)

Concrete examples AppLocale rewrites from your English source — not Magnifier camera, Dynamic Type, or VoiceOver copy:

• Screenshot caption — Before: Window zoom → After: 窗口放大
• Description line — Before: Magnify any part of the screen with Accessibility Zoom → After: 辅助功能放大，屏幕任意区域可放大查看
• Subtitle (30 chars) — Before: Screen magnification made easy → After: 屏幕放大，低视力更易用
• Screenshot caption — Before: Zoom controller — drag to pan → After: 放大控制器，拖动平移视图
• Keyword field — Before: Zoom,screen magnification,window zoom,low vision → After: 放大,屏幕放大,窗口放大,全屏放大,辅助功能放大
• Promotional text — Before: New follow-focus zoom tracks your cursor → After: 新增跟随焦点放大，自动跟踪焦点区域

Final phrasing depends on your English claims, zoom surfaces on gallery frames, and Connect character caps. See Promotional text in Simplified Chinese when your magnification pitch lives in promo text rather than the long description.

Why English-only Accessibility Zoom copy hurts China storefront conversion

Low-vision purchasers browsing the China App Store evaluate magnification claims in the first scroll. Common failure modes when only en-US is filled:

• Trust gap — Chinese word-of-mouth recommends a "screen zoom app"; buyer taps through and sees English "Window zoom" with no zh-Hans context
• Localized listing, English badges — description promises Chinese magnification; screenshot overlays still "Zoom" at the worst moment
• Search intent miss — buyers search 屏幕放大 or 辅助功能放大; English-only keywords miss intent even when zoom works in the app
• Competitor contrast — rivals with native zh-Hans zoom copy look more serious about China low-vision buyers
• Magnifier confusion in translation — machine-translated copy that says 放大镜 when you mean Accessibility Zoom screen magnification, not Magnifier camera

Clearer zh-Hans zoom marketing reduces confusion on the product page. It does not replace zoom code, controller UI, or in-app accessibility settings.

Why machine-translated Accessibility Zoom copy fails

• Literal "Zoom" → untranslated English badge on zh-Hans screenshots instead of commerce-idiomatic 放大 or 屏幕放大
• Generic "magnify" → 放大镜 (Magnifier camera sense) instead of 屏幕放大 (UI magnification sense buyers expect)
• English badge headlines preserved on zh-Hans screenshots — "Full-screen zoom" with no Chinese benefit line beside it
• Overlay text overflow — long English zoom marketing lines pasted into short screenshot callout zones truncate on device
• Conflating Accessibility Zoom with Display Accommodations color filters or Dynamic Type font scaling in one keyword field
• Inconsistent vocabulary between listing description, promotional text, and screenshot captions when all three mention zoom features

Machine translation is fine for internal drafts. Finished Accessibility Zoom strings need idiomatic zh-Hans that states what screen magnification you ship — while keeping accurate scope and clear separation from Magnifier camera marketing. AppLocale rewrites by hand; we do not deliver raw Google Translate or LLM output as finished copy.

What good zh-Hans Accessibility Zoom listing copy looks like

Zoom copy appears on screenshot galleries and in description skims. Strong Chinese strings lead with the benefit and state scope plainly — paste-ready examples for Connect fields:

• Subtitle (example) — 屏幕放大，低视力更易查看 — magnification benefit within the ~30-character cap
• Keywords (example) — 放大,屏幕放大,窗口放大,全屏放大,辅助功能放大 — only when accurate to your feature set
• Screenshot overlay (example) — 窗口放大，拖动控制器自由平移 — zoom controller frame with clear benefit line
• Description paragraph (example) — plain zh-Hans list of zoom modes you ship — window zoom, full-screen zoom, zoom controller, follow-focus — matching what you actually implemented
• Honest scope — do not claim full iOS Accessibility Zoom replacement in Chinese if your app only ships a limited magnification demo

zh-Hans and en-US strings can differ in length and structure when the underlying zoom story is the same — avoid mirroring English comma-heavy promo lines character-for-character.

What you send

• Your live App Store listing URL
• Current English listing copy — name, subtitle, keywords, description, promotional text if used
• Screenshot overlay text that mentions Accessibility Zoom, screen magnification, window zoom, full-screen zoom, zoom controller, follow-focus, or hover text
• Brief note on which zoom modes your app ships today — window zoom, full-screen zoom, controller, follow-focus, hover text — so zh-Hans copy stays accurate
• Target locales (e.g. zh-Hans for China storefront)
• Your deadline if aligning with a zoom feature launch or App Store update
• Reply from the email address on your Stripe receipt after checkout

What you get

• Simplified Chinese (zh-Hans) — listing fields and screenshot overlay lines scoped to Accessibility Zoom and screen magnification marketing, paste-ready for Connect
• English (en-US) — aligned listing strings when both locales need the same promise in native phrasing
• Character-count notes — which strings fit Connect limits and what to trim
• Paste-ready delivery — formatted copy mapped to each field you sent
• 24-hour turnaround — delivered to the email on your Stripe receipt

What we do not promise

• No guarantee that zoom quality, controller responsiveness, or follow-focus accuracy improves — listing rewrite describes what you already ship
• No UIAccessibility zoom, zoom controller, follow-focus, hover text, or Settings deep-link engineering
• No claim that your app replaces Apple Accessibility Zoom in Settings unless your English listing already states that accurately — and even then, AppLocale does not certify system parity
• No guaranteed App Store ranking, keyword position, download growth, or low-vision certification outcomes
• No fabricated social proof, review quotes, ratings, or traffic numbers
• No binary localization, in-app string translation, or Connect configuration on your behalf
• No screenshot design, PNG re-export, Apple Search Ads, or review-reply retainers
• Not QuantRadar · not investment advice · not legal review

AppLocale FAQ

What Accessibility Zoom listing copy does AppLocale cover?

Paste-ready Simplified Chinese (zh-Hans) for App Store Connect listing fields you specify: title, subtitle, keywords, description, promotional text when included, and screenshot overlay or caption lines that mention Accessibility Zoom, system screen magnification, window zoom, full-screen zoom, zoom controller, follow-focus zoom, hover text, or Settings → Accessibility → Zoom — rewritten from your English originals with terms like 放大, 屏幕放大, 窗口放大, and 放大控制器 where accurate.

How is this different from Magnifier?

Accessibility Zoom listing copy covers on-screen UI magnification — window zoom, full-screen zoom, zoom controller, follow-focus, and hover text. Magnifier listing copy covers camera-based close-up magnification for reading physical objects — magnifying glass, reading zoom, torch-assisted reading. Zoom enlarges the UI overlay; Magnifier uses the camera viewfinder. See our Magnifier listing guide for camera zoom marketing.

Is this Display Accommodations or Dynamic Type?

No. Display Accommodations covers color filters, invert colors, and display zoom presets — not Accessibility Zoom screen magnification overlays. Dynamic Type covers adjustable font size and typography scaling in the app interface. This page covers Accessibility Zoom marketing only.

How is this different from VoiceOver or Voice Control?

Accessibility Zoom listing copy markets visual screen magnification on the product page. VoiceOver covers screen reader navigation. Voice Control covers spoken commands. Switch Control covers external switch hardware. Those are separate scopes with different screenshot vocabulary.

Does AppLocale implement zoom or Magnifier code?

No. We deliver Connect listing metadata copy only. UIAccessibility zoom plumbing, zoom controller UI, follow-focus behavior, hover text rendering, Magnifier camera pipelines, and Settings deep-link engineering are outside AppLocale scope.

Does shipping zoom auto-translate my China listing?

No. Screen magnification UI in the app does not create or fill a Simplified Chinese localization row. Empty or English zh-Hans fields mean China buyers see en-US fallback on the product page.

What do I send after payment?

Your live App Store listing URL, current English listing copy, screenshot overlay lines mentioning Accessibility Zoom or screen magnification (with frame order noted), which zoom modes you ship, target locales (e.g. zh-Hans), and deadline. Reply from the email address on your Stripe receipt.

Is this machine translation?

No. We rewrite Accessibility Zoom and screen magnification listing copy by hand. We do not paste Google Translate or ChatGPT output into deliverables.

How fast is delivery?

Within 24 hours after your Stripe receipt. Send your App Store URL, English listing and overlay copy, target locales, and deadline from the email on your receipt.

Do you guarantee conversion lift or App Store rankings?

No. We improve clarity from your existing copy. We do not promise keyword position, search rank, or download growth.

How much does AppLocale cost?

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

What is AppLocale not?

Not UIAccessibility zoom or Magnifier camera engineering, not Display Accommodations listing copy, not Dynamic Type or Reduce Motion listing copy, not VoiceOver, Voice Control, Switch Control, or Assistive Access listing copy, not Music Haptics, Background Sounds, or Hearing Devices listing copy, not Settings deep-link implementation, not screenshot design, not binary localization, not Connect configuration, not ranking guarantees, not review-reply retainers, not QuantRadar, and not investment advice. We do not invent reviews, ratings, or traffic numbers.

AppLocale — Accessibility Zoom & screen magnification listing copy in Simplified Chinese

$79 one-time

Buy on Stripe

After checkout, reply from your Stripe receipt email with your App Store URL, English listing and Zoom overlay copy, target locales, and deadline. Delivery within 24 hours.
No ranking guarantees. Sold by Fortune Insight, LLC.