Skip to content
axintdocs

Accessibility label evidence

An accessibility modifier does not prove an app’s common tasks work with an assistive technology. Axint’s assessment API records task-level evidence and only marks a feature claimable when every applicable task passes or is explicitly not applicable.

  • VoiceOver
  • Voice Control
  • Larger Text
  • Dark Interface
  • Differentiate Without Color Alone
  • Sufficient Contrast
  • Reduced Motion
  • Captions
  • Audio Descriptions

Assessments are separated by iPhone, iPad, Mac, and Apple Vision. Mac excludes the Larger Text declaration because the store matrix differs by device family.

Use the user journeys that matter to the product, not a list of screens:

import {
evaluateAccessibilityNutritionLabels,
renderAccessibilityNutritionLabelReport,
} from "@axint/compiler";
const assessment = evaluateAccessibilityNutritionLabels({
devices: ["iphone", "ipad"],
commonTasks: [
{ id: "first-launch", title: "Complete first launch" },
{ id: "create-project", title: "Create a project" },
{ id: "upgrade", title: "Upgrade the account" },
],
evidence: [
{
taskId: "first-launch",
device: "iphone",
feature: "voiceOver",
status: "pass",
artifact: ".axint/proof/first-launch-voiceover.xcresult",
},
],
});
console.log(renderAccessibilityNutritionLabelReport(assessment));

Missing evidence and failed tasks remain visible in the Markdown report. Axint does not infer a claim from unrelated compiler or UI-test success.

Useful release evidence includes:

  • .xcresult references for focused UI tests
  • screenshots at applicable content-size categories
  • accessibility snapshots or semantic-tree captures
  • short recordings for motion, captions, or audio-description behavior
  • device, runtime, locale, and appearance configuration
  • reviewer identity and review date

Store the evidence with the same commit and release receipt that produced the archive. A declaration should be reproducible by another reviewer.

  1. Select the common tasks for the release.
  2. Run static review and keep all advisory findings visible.
  3. Collect runtime evidence on each supported device family.
  4. Record pass, fail, or not-applicable for every task and feature.
  5. Review the generated claimable set.
  6. Have the app owner approve App Store Connect declarations.

Axint can prepare the evidence packet. It does not automatically make product or legal claims on the owner’s behalf.