describe learner needs and a digital resource's accessibility features using IMS AccessForAll (AfA) 3.0 PNP and DRD models

domain: imsglobal.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Model the learner's needs and preferences using the AfA Personal Needs and Preferences (PNP) 3.0 information model
  2. Model the digital resource's accessibility characteristics using the separate AfA Digital Resource Description (DRD) 3.0 model
  3. Match a learner's PNP profile against a resource's DRD metadata to decide whether an accessible alternative should be served
  4. Embed the resulting metadata alongside content packages (e.g. QTI 3.0 packages) that reference AfA for accessibility features
  5. Confirm which AfA 3.0 documents (PNP vs DRD) the target platform actually consumes before building against both

Known gotchas

Related routes

Implement WCAG 2.1 AA accessibility requirements in a web-based courseware component
education-general · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans