Accessibility on a consumer iPhone is whether a stranger can finish the job when text is large, when they cannot see the icon, or when they cannot hit a 24-point heart. It is not a badge. At Croncode it sits on the same checklist as empty states. Design QA: design QA. This page is the baseline we will not skip for “premium chrome.” Premium UI without this is costume: premium consumer UI.

Consumer iOS accessibility starts with Dynamic Type, VoiceOver labels on icon buttons, contrast on the primary action, and targets a thumb can hit. It is a store-quality bar, not a later add-on.

What is the first-pass list?

1. Dynamic Type two steps up on the first job.
2. VoiceOver names every icon-only control.
3. Primary CTA contrast holds in light and dark.
4. Destructive actions need a confirm a VoiceOver user can find.
5. Reduce Motion respected if you ship large motion.

Empty states must still teach: empty states. Trust: trust patterns. Localization length will break layout first in Turkish: onboarding localization.

Which consumer jobs hide a11y debt?

Catalog: what Croncode builds. Paywalls need labeled purchase and restore: honest paywalls.

When does accessibility block a submission?

When the first job cannot be completed with large text or with VoiceOver on the primary path. When a permission sheet has an empty purpose string. When a sprint demo only works on the engineer’s eyes. Demo: sprint demo. Thin MVP: too thin.

People: Goktug Unver, Yusufhan Sokur, Ozgur Ismet Ozkan. Shipping: Istanbul shipping.

How do we test in a lean week?

One pass with VoiceOver on the first job. One pass at large type on a small phone. Write the build number. Lean hours: small team, multiple products. AI results must be readable when the model fails: fail-safe AI.

What mistakes look like polish?

• Custom fonts that ignore Dynamic Type: pretty and unusable.
• Gesture-only actions: provide a button.
• Green/red only for success and error: add words.
• Push sheets with no VoiceOver title: earn permission.

Quote a11y as part of the increment: what to send. Choose a studio: choose an iOS studio. Hire: hire. Custom: custom software. Contact: contact. Journal: /en/journel/.

How does this meet reviews and support?

Users will write “I cannot read the button.” Treat it as a first-job bug. Reviews: reviews as a team. Support: support email. We will not claim a perfect score. We will claim a list. What we will not ship: a listing screenshot that clips at default type while the binary clips at large type. Will not build.

Onboarding trust includes being able to leave: trust onboarding. Week two still needs a readable home: week two. If a skip control is only an X in the corner, VoiceOver users may never find it. Name it Skip. Put it in the same pass as the primary CTA. A premium consumer app that traps people in a tour is not premium. It is a maze.

Put VoiceOver and large type on the sprint demo script so a client sees the pass, not only a pretty recording. If the increment is a paywall, restore must be reachable without sighted hunting. If the increment is an AI result, the failure sentence must be readable at large type. Those are the same first job, just slower.

Frequently asked questions

Is this only for VoiceOver users?

No. Large text and contrast help many people. VoiceOver is one required pass, not the only one.

Do we need a full audit firm?

Not for version one of a small consumer job. You need the list above and a human who runs it. A firm can come later for a regulated product.

Does Apple require this?

Apple publishes Human Interface guidance and review can reject broken experiences. Treat it as quality, not as a loophole hunt.

What about color themes as a brand?

Brand tokens must still meet contrast. A signature purple that fails on white is a bug.

Who signs the pass at Croncode?

Design signs labels and contrast. Engineering signs Dynamic Type layout. Both names go on the note.