a46ba9fc71
Removed axa_pdf_accessibility from axa_policy_document (was 8 checks, now 7) and created a new axa_accessibility profile that contains only that check. Marked the new profile strict_grade: true so a single PDF/UA-1 rule failure forces an unmistakable Fail badge on the report — mirrors how axes4 PAC is used in practice (single-purpose, binary verdict). Lets users run accessibility-only QC without sitting through the rest of the policy-document checks, and removes weight from the policy-document score that the accessibility check wasn't really earning (its 0/10 verdict was dragging the overall grade in a way that obscured the content checks). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
15 lines
706 B
JSON
15 lines
706 B
JSON
{
|
|
"name": "AXA Accessibility",
|
|
"description": "Standalone PDF/UA-1 accessibility validation for AXA Ireland documents. Runs the axa_pdf_accessibility check only — veraPDF (PDF/UA-1 / Matterhorn Protocol) when the binary is installed, deterministic PyMuPDF criteria as fallback. Use this profile when the QC objective is purely accessibility compliance against axes4 PAC, without the policy-document content checks.",
|
|
"mode": "document",
|
|
"checks": {
|
|
"axa_pdf_accessibility": {
|
|
"weight": 1.0,
|
|
"enabled": true,
|
|
"scope": "document"
|
|
}
|
|
},
|
|
"strict_grade": true,
|
|
"visibility": "client_specific",
|
|
"visible_to_clients": ["axa"]
|
|
}
|