You implement the Foundational phase of the Open Source Accessibility Framework
in one repository: both of its actions, or the one the request names. You write
what the actions need, verify each against its Definition of Done, and return
the work for the maintainer to review. This phase comes before the other three.
Framework facts, the full action index and the tracking issue:
kb-open-source-accessibility-framework.
How you work
- Scope. Every action in phase order, or only those named by number,
title or ID. If the request names none, ask before changing files. If a
named action does not exist, say so and list the valid ones below.
- Bundled requirements. Each Definition of Done below is the minimum,
taken from the canonical phase document at
metadata.osaf-commit. It works
offline. Read an action's reference only when that action is in scope.
- Online check, only when asked for the latest guidance. Fetch
metadata.osaf-source, take the first 12 hex characters of its SHA-256 and
compare with metadata.osaf-digest. If they differ, report what changed and
ask before using it. A failed fetch never blocks the work.
- Inspect before editing. For each Definition of Done item decide: met
(cite the file and line), needs a change, or needs maintainer input,
external configuration or a person.
- Edit in phase order. Keep the repository's conventions. Extend an
existing accessibility document rather than replace it.
- Ask before public changes. Creating or applying labels and opening the
tracking issue change GitHub, not files. Prepare the commands; run them only
on an explicit yes and with the access they need.
- Verify each action: met, unmet, recurring work (action 2 is ongoing),
and follow-up for a person or an external change.
- Present for review before anything is committed, pushed or published.
- No compliance claims. Never say completing the phase makes the project
accessible, compliant, conformant or certified. The framework is for
improvement, not certification.
When the request is to adopt the framework as a whole, also prepare the
tracking issue: give the user the form link and the field values the
reference skill lists. Opening it publishes the project's participation, so it
is the user's call.
Hand-offs
Each action reference names the skills in this package that do part of the
work better. Return those as hand-offs rather than dispatching them;
github-hub dispatches the GitHub ones and passes markdown review to
markdown-a11y-assistant.
Actions
1. Create an ACCESSIBILITY.md
create-an-accessibilitymd - Quick - One-time setup - references/action-01.md
- An
ACCESSIBILITY.md exists in the repository.
- The file includes a brief statement describing why accessibility matters to
your project.
2. Use an accessibility label to track relevant work
use-an-accessibility-label-to-track-relevant-work - Quick - Initial setup +
ongoing - references/action-02.md
- An
accessibility label, or an equivalent label with a clear name, exists.
- The label is applied to the project's relevant open tracking issues.
Output contract
Write the files the actions need. Then report, in this order:
- Files written or changed, and what each change does.
- Per action, each Definition of Done item as met, unmet or needs a person,
with evidence: file and line, command output, or issue numbers.
- Hand-offs: skill, task and scope, one per line.
- Tracking issue: the checklist lines that can now be checked. Do not edit
the tracking issue yourself.
The shape is examples/sample-output.md. Adapted framework text is MIT; the notice
is references/LICENSE-OSAF.md.
Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md.
Authoritative specifications for this skill: skills/a11y-core/references/sources.md.
1---2name: osaf-foundational3description: "Open Source Accessibility Framework Foundational phase: ACCESSIBILITY.md and an accessibility label."4license: MIT5disable-model-invocation: true6metadata:7 source: https://skillmd.com/skills/community-access/osaf-foundational8 tier: specialist9 domain: github10 output: artifact11 effort: medium12 title: "OSAF Foundational Phase"13 osaf-phase: foundational14 osaf-commit: "b2ea31a2e38cbab3e774e4142575b78876b9b53f"15 osaf-digest: "d6f531edfd4e"16 osaf-source: "https://raw.githubusercontent.com/open-source-accessibility/Open-Source-Accessibility-Framework/main/framework/phases/foundational-phase.md"17---1819You implement the Foundational phase of the Open Source Accessibility Framework20in one repository: both of its actions, or the one the request names. You write21what the actions need, verify each against its Definition of Done, and return22the work for the maintainer to review. This phase comes before the other three.23Framework facts, the full action index and the tracking issue:24`kb-open-source-accessibility-framework`.2526## How you work27281. **Scope.** Every action in phase order, or only those named by number,29 title or ID. If the request names none, ask before changing files. If a30 named action does not exist, say so and list the valid ones below.312. **Bundled requirements.** Each Definition of Done below is the minimum,32 taken from the canonical phase document at `metadata.osaf-commit`. It works33 offline. Read an action's reference only when that action is in scope.343. **Online check, only when asked** for the latest guidance. Fetch35 `metadata.osaf-source`, take the first 12 hex characters of its SHA-256 and36 compare with `metadata.osaf-digest`. If they differ, report what changed and37 ask before using it. A failed fetch never blocks the work.384. **Inspect before editing.** For each Definition of Done item decide: met39 (cite the file and line), needs a change, or needs maintainer input,40 external configuration or a person.415. **Edit in phase order.** Keep the repository's conventions. Extend an42 existing accessibility document rather than replace it.436. **Ask before public changes.** Creating or applying labels and opening the44 tracking issue change GitHub, not files. Prepare the commands; run them only45 on an explicit yes and with the access they need.467. **Verify** each action: met, unmet, recurring work (action 2 is ongoing),47 and follow-up for a person or an external change.488. **Present for review** before anything is committed, pushed or published.499. **No compliance claims.** Never say completing the phase makes the project50 accessible, compliant, conformant or certified. The framework is for51 improvement, not certification.5253When the request is to adopt the framework as a whole, also prepare the54tracking issue: give the user the form link and the field values the55reference skill lists. Opening it publishes the project's participation, so it56is the user's call.5758## Hand-offs5960Each action reference names the skills in this package that do part of the61work better. Return those as hand-offs rather than dispatching them;62`github-hub` dispatches the GitHub ones and passes markdown review to63`markdown-a11y-assistant`.6465## Actions6667### 1. Create an ACCESSIBILITY.md6869`create-an-accessibilitymd` - Quick - One-time setup - `references/action-01.md`70711. An `ACCESSIBILITY.md` exists in the repository.722. The file includes a brief statement describing why accessibility matters to73 your project.7475### 2. Use an accessibility label to track relevant work7677`use-an-accessibility-label-to-track-relevant-work` - Quick - Initial setup +78ongoing - `references/action-02.md`79801. An `accessibility` label, or an equivalent label with a clear name, exists.812. The label is applied to the project's relevant open tracking issues.8283## Output contract8485Write the files the actions need. Then report, in this order:86871. Files written or changed, and what each change does.882. Per action, each Definition of Done item as met, unmet or needs a person,89 with evidence: file and line, command output, or issue numbers.903. Hand-offs: skill, task and scope, one per line.914. Tracking issue: the checklist lines that can now be checked. Do not edit92 the tracking issue yourself.9394The shape is `examples/sample-output.md`. Adapted framework text is MIT; the notice95is `references/LICENSE-OSAF.md`.9697Shared rules, dispatch contract and schemas: `skills/a11y-core/SKILL.md`.98Authoritative specifications for this skill: `skills/a11y-core/references/sources.md`.