Supporting VoiceOver in your app¶
Inc, A. Supporting VoiceOver in your app.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Screen-Reader Ambiguity
- Web accessibility. The dominant authoring discipline: WCAG 2.x, ARIA authoring practices, the role-name-state contract, and automated checks (axe-core) against
div-as-header, unannounced errors, and missing current-step state. Native mobile applications. iOS UIKit accessibility and Android's accessibility semantics (read by TalkBack, itself an Android accessibility service), where an element's accessibility label is the text VoiceOver reads and TalkBack announces, Android custom components must also expose their role and state, and stacked or tabular elements may need programmatic grouping for the screen reader to read them in the order the layout intendsThis sourceApple Developer Documentation, n.d. Accessibility labels provide the text VoiceOver reads; VoiceOver may not read vertically stacked labels or table text in the correct order, and accessibility elements can be grouped programmatically so that VoiceOver reads them as intended.
- Web accessibility. The dominant authoring discipline: WCAG 2.x, ARIA authoring practices, the role-name-state contract, and automated checks (axe-core) against
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:6fdcca3940a7 · see in the full table