Security settings must not block assistive technology

PDF/UA check DOC_ACCESSIBILITY_PERMISSIONS · Document level · severity Critical · PDF/UA 7.16 Security

↩ Back to the rules index · WCAG cross-reference

Why it matters#

Some PDFs have security settings that block text extraction. This prevents screen readers from accessing the content, making the document completely inaccessible to blind users.

What you will see#

The document is encrypted with permissions that forbid text extraction, which locks screen readers out entirely.

How to fix#

Remove the document's encryption, or re-save it with security settings that permit content extraction for assistive technology. In Acrobat: File > Properties > Security > Security Method > No Security.

Step-by-step guide#

1. Open File > Properties > Security in Acrobat Pro and check the Security Method setting.
2. Set Security Method to No Security (enter the permissions password if prompted) and save the file. Removing encryption entirely is the reliable path: EQChecker flags any document whose trailer contains an Encrypt entry.
3. If organizational policy requires the file to stay encrypted, configure Password Security so content extraction for assistive technology is permitted (check 'Enable text access for screen reader devices for the visually impaired'), which satisfies the accessibility intent of the requirement.
4. If you do not have the permissions password, request an unsecured copy from the document owner or re-export from the source file - do not attempt to strip security you are not authorized to remove.
5. Re-save and redistribute the corrected file; encryption settings live in the file itself, so previously distributed copies remain inaccessible.

Verify: Re-run the EQChecker scan; DOC_ACCESSIBILITY_PERMISSIONS passes when the file trailer has no Encrypt entry. Acrobat's accessibility check 'Accessibility permission flag' should also pass.

Note: The current EQChecker check is conservative: it errors on any encryption, even when the permission bits would allow assistive technology access, so only step 2 guarantees a clean scan. Unencrypted documents always satisfy this rule.

Fixing it in your authoring tool#

WCAG success criteria#

1.3.1 Info and Relationships — Level A#

Structure and relationships conveyed visually (headings, lists, tables, labels, groups) must also be available programmatically.

Understanding 1.3.1

Standards#

This check contributes to the following standards:

PDF/UA WCAG A EN 301 549

References#

• Matterhorn Protocol 1.1 — PDF Association