Add pdf-aam
URL
https://w3c.github.io/pdf-aam/
Rationale
- See repository: w3c/pdf-aam
- Would-be shortname:
pdf-aam
Additional properties
{}
Changes to index.json
This update would trigger the following changes in index.json:
Add spec (1)
{
"url": "https://w3c.github.io/pdf-aam/",
"seriesComposition": "full",
"shortname": "pdf-aam",
"series": {
"shortname": "pdf-aam",
"currentSpecification": "pdf-aam",
"title": "PDF Accessibility API Mappings",
"shortTitle": "PDF Accessibility API Mappings",
"nightlyUrl": "https://w3c.github.io/pdf-aam/"
},
"categories": [],
"organization": "W3C",
"groups": [
{
"name": "Accessible Rich Internet Applications Working Group",
"url": "https://www.w3.org/WAI/about/groups/ariawg/"
},
{
"name": "SVG Accessibility Task Force",
"url": "https://www.w3.org/WAI/PF/svg-a11y-tf/"
}
],
"nightly": {
"url": "https://w3c.github.io/pdf-aam/",
"status": "Editor's Draft",
"alternateUrls": [],
"repository": "https://github.com/w3c/aria",
"sourcePath": "pdf-aam/index.html",
"filename": "index.html"
},
"title": "PDF Accessibility API Mappings 1.0",
"source": "spec",
"shortTitle": "PDF Accessibility API Mappings 1.0",
"standing": "good"
}
Tests
These changes look good! 😎
Crawl results for PDF Accessibility API Mappings 1.0
Crawl summary:
- Title: PDF Accessibility API Mappings 1.0
- Authoring tool: respec
- Date: 23 October 2025
- Canonical URL: https://w3c.github.io/pdf-aam/
- Spec defines:
- Headings: 37 found
- IDs: 90 found
- Links: 22 rawlinks, 2 autolinks
- References: 2 normative, 2 informative
- Terms: 1 explicitly exported
- No Algorithms, CDDL, CSS, Events, Web IDL definitions found
1 explicitly exported term
- PDF-object to be named, type dfn (xref search)
To be added but spec is empty now and defines exported placeholder terms "term 1" and "term 2".
The specification was updated on 2024-12-11 (last reviewed on 2024-11-11).
The specification was updated on 2025-07-30 (last reviewed on 2025-05-01).
The specification was updated on 2025-10-23 (last reviewed on 2025-05-01).
Various sections are still "TBD" but the spec is progressing and no longer defines fake content. Seems worth adding. I was thinking I would remove the "browser" category... but then all browsers have a built-in PDF viewer (at least on desktops) in practice. @dontcallmedom what do you think?
I agree it's not fully clear cut, but I'd still remove the "browser" category - PDF support feels more like an add-on to a browser functionality.
@browser-specs-bot pr