Knowing that a digital public service works does not mean that a screen opens without errors. It means that a person understands the procedure, can complete it with reasonable support, receives an explained response, and keeps an effective route for correcting a problem.
Define what should work#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Look at the full experience#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Recognise warning signs#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Check the information#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Measure accessibility#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Test the human alternative#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Watch deadlines and notices#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Review data and privacy#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Ask about automated decisions#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Record incidents#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Compare improvement with evidence#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Coordinate nearby support#
The first useful sign is specific: the person can identify the responsible body, the purpose of the procedure, and the outcome they expect. A campaign or new application is not enough. Check whether instructions use plain language, requirements appear before starting, and progress can be saved easily. Recording the date, channel, and case number makes it possible to return to the issue without relying on memory or repeating the story to every contact.
Walk through the service as someone with little time, unstable connectivity, an older device, a disability, or limited familiarity with administrative language would do. Identification, document submission, status checking, decision, and appeal are parts of the same right. If one fails, success in the others does not compensate for exclusion. Testing should include alternative formats, in-person or telephone support, and a visible explanation of where help can be requested.
An early warning appears when the system requests data without explaining why, changes a deadline without notice, forces use of one application, or replies with an automated message offering no next step. Rather than giving up, take a screenshot, retain the date, and describe what was attempted. That evidence helps customer support, an association, or a complaint body reproduce the fault and propose a solution that can be checked.
Concrete cases#
Case 1. Marta received an appointment notice with no accessible link or telephone number. She saved it, called support, and received an alternative appointment; the centre corrected the notice. Case 2. Samuel did not understand a rejection. He requested an explanation, supplied the missing document, and received a reviewed decision. Case 3. A library tested a portal with older residents, found a keyboard-invisible button, and the council published a correction and checking date.
Sources and next steps#
To check rights and routes, consult the Spanish Data Protection Agency, the Ministry for Digital Transformation and Public Administration, the Spanish Ombudsman, the Royal Board on Disability, and the competent authority. Confirm deadlines and appeals in official information for the case and retain written replies.
