Cognitive Accessibility for Customer Documents: A 90-Day Readiness Plan Before Spain’s 2027 Rules

Cognitive Accessibility for Customer Documents Before Spain’s 2027 Rules

A document can be technically accessible and still fail the person who receives it. A customer may be able to open a letter, navigate its headings and hear it through text-to-speech, yet still miss the action required, misunderstand a deadline or abandon a form. That gap between access and understanding is now an operational concern for more European organizations.

Spain’s Royal Decree 707/2026 was published on 3 September 2026 and takes effect on 2 January 2027. It establishes basic conditions for cognitive accessibility across defined areas of public and economic life. The detailed duties vary by context, so organizations need legal advice on applicability. The direction is nonetheless clear: important information and procedures must be easier for people with cognitive difficulties to understand and use. [1] [2]

For leaders responsible for customer communications, the immediate task is not to rewrite every document. It is to identify the communications where misunderstanding carries the highest consequence, define what successful understanding looks like, and create a controlled process for producing and validating accessible versions.

What Spain’s New Rules Change

The decree applies throughout Spain in the fields referenced by the country’s general disability law. It covers a wide range of settings, including goods and services, public administration, justice, employment, elections, culture, buildings and transport. The obligations are not identical across those settings. [1]

For providers of goods and services in covered contexts, Article 9 addresses transparency and clarity in commercial information. It calls for basic consumer information in simple language and, where possible, visual supports. It also requires a complaint form in Easy Read. Article 10 places more specific requirements on public administrations, including clear documentation and Easy Read versions of forms, applications and procedural guides. Other sections address judicial communications, employment information and public participation. [1]

This matters to more than Spanish government departments. Financial institutions, insurers, utilities, healthcare organizations, employers, transport providers and nonprofit foundations may produce communications touched by the decree or by the broader expectation it represents. Each organization should map its legal role and document obligations with qualified counsel rather than treating the decree as a universal rule for all content.

Technical Accessibility and Understanding Are Different Tests

Traditional document accessibility work often starts with technical requirements: reading order, headings, alternative text, contrast, keyboard access, document tags and compatibility with assistive technology. Those controls remain essential. Cognitive accessibility asks a different question: can the intended person understand the message and complete the task?

W3C’s guidance for people with cognitive and learning disabilities is explicitly supplemental to WCAG 2.x. It recommends clear words, short sentences and blocks of text, familiar patterns, summaries for long material, support for users who make mistakes, and direct involvement of people with cognitive and learning disabilities in design and testing. W3C also warns that automated accessibility testing often cannot determine whether a person with a cognitive disability can use the content. [3]

Plain language and Easy Read are related but not interchangeable. ISO 24495-1 defines principles for creating plain-language documents intended to help readers find, understand and use information. Spain’s decree describes Easy Read as a method that includes writing, design, layout and validation of understandability for people with reading-comprehension difficulties. An organization may need a standard version, a plain-language version and an Easy Read version for different audiences or tasks. [1] [5]

A 90 Day Cognitive Accessibility Readiness Plan

Days 1 to 30 Find Risk and Define Success

Start with the consequence of misunderstanding. A renewal notice, benefit determination, consent form, claims decision, complaint process or safety instruction deserves more attention than a low-risk marketing update. Build a document register that records the audience, purpose, required action, deadline, channel, language, owner and legal basis for each communication.

Rank each document against four factors: the harm caused by misunderstanding, the cognitive load of the content, the needs of the audience and the frequency or scale of delivery. Include complaints, call drivers, abandonment points and requests for explanation. These signals often reveal documents that are technically complete but operationally unclear.

Then define acceptance criteria in observable terms. “Readable” is too vague. A useful test might ask whether a participant can identify the decision, explain the main consequence, find the deadline, state the next action and locate help without prompting. Keep the legal meaning and required disclosures fixed while testing how wording, order, layout and support options affect understanding.

Days 31 to 60 Build Controlled Variants

Treat the approved meaning as a controlled source. Separate mandatory facts and legal clauses from the presentation layer so teams can change sentence structure, summaries, visual hierarchy or supporting images without silently changing the underlying decision. Assign named owners for legal accuracy, accessibility, content design and business approval.

Create reusable patterns for common communication tasks. Put the purpose and required action near the beginning. Use short, descriptive headings. Explain unfamiliar terms when they first appear. Break multi-step instructions into a visible sequence. Offer a clear route to human help. For complex numerical information, provide a guided explanation rather than assuming that a table alone communicates the result.

Build an approval path that preserves version history and records why each change was made. If a rule selects different content for different customers, test every material branch. A plain-language or Easy Read variant must carry the same decision, rights, obligations, dates and amounts as the source document. Translation adds another validation layer; do not assume that a successful English or Spanish test transfers automatically to every language.

Days 61 to 90 Test and Operationalize

Test with people who reflect the intended audience, including people with different cognitive and learning disabilities. Ask participants to use the document in a realistic task. Observe whether they can find information, explain it in their own words and complete the next step. Avoid coaching that hides the document’s weaknesses.

Combine qualitative observation with simple measures: task completion, critical-message recall, time to find the next action, error rate, requests for assistance and confidence. Review complaints, call transcripts and journey abandonment after release. The FCA’s 2026 review recommends testing communications before and after changes, using comprehension checks and evidence from frontline interactions, then documenting what changed and whether it improved understanding. [4]

Finish the first 90 days with a controlled release of the highest-risk templates, not a declaration that the entire estate is compliant. Record the audience tested, the tasks used, the issues found, the changes approved and the residual risks. Use that evidence to decide which document families should move next.

Executive Approval Checklist

Where Document Automation Helps

A customer communication management platform can make this program easier to control. Reusable sections can keep mandatory content consistent. Business rules can select the right variant for a known audience or service context. Workflow controls can route a change through content, legal and accessibility review. Multichannel generation can reduce divergence between a letter, email and portal message. Versioning and monitoring can provide evidence that approved content was used.

Automation also has limits. A readability score cannot establish that a person understands a benefits decision. An AI rewrite may remove a legal qualification or change the emphasis of a risk. A template checker may identify a long sentence without knowing whether a visual explanation is culturally appropriate. Human review and user testing remain necessary for high-consequence communications.

Perfect Doc Studio states that business users can build visual templates, apply conditional rules, manage workflows and approvals, deliver across channels, and use an AI Template Optimizer that reviews templates for accessibility, compliance and readability. Its capabilities page also describes embedded pre-send review and role-based template access. Those features can support a governed cognitive-accessibility workflow, but they should be evaluated against your own legal scope, acceptance criteria and user-testing evidence. [6] [7]

Start With a Small High Consequence Portfolio

The most credible first milestone is a small portfolio of documents that people must understand to protect a right, receive a service, make a payment, give consent or challenge a decision. Select five to ten templates, define the intended audiences and required actions, create controlled variants, and test them with real users. That work produces evidence the organization can use to scale rather than a checklist that merely records activity.

Recommended next step: Review Perfect Doc Studio as a customer communication management platform for a focused cognitive-accessibility pilot. Use the demo to test template governance, approval evidence, conditional variants, multichannel output and pre-send review against your own acceptance criteria.

Frequently Asked Questions

What are cognitive accessibility documents

They are documents designed so people with cognitive and learning disabilities can understand the information and complete the intended task. The work may involve language, structure, layout, visual support, alternative formats and testing with intended users.

Does WCAG compliance make a document cognitively accessible

Not by itself. WCAG conformance addresses important accessibility requirements, but W3C describes its cognitive-accessibility patterns as supplemental guidance. Organizations still need to test whether intended users can understand and use the content. [3]

Is Easy Read the same as plain language

No. Plain language aims to help intended readers find, understand and use information. Easy Read is a more specific method that combines writing, design, layout and validation for people with comprehension difficulties. The right format depends on the audience, task and applicable requirement.

Can AI generate compliant Easy Read documents

AI can help propose simpler wording or flag potential issues, but it can also change meaning, omit qualifications or produce content that has not been validated with users. High-consequence documents require controlled source content, expert review and user testing. A platform feature should be treated as workflow support, not proof of compliance.