How Should an Accessibility Consultant in Spain Show Audits and Private Remediation Work?

An accessibility consultant should turn each approved engagement into a focused case that describes the user barrier, evaluation scope, personal contribution, remediation, and a safe current proof link.

A raw audit report is usually the wrong portfolio artifact: it can expose client systems, user information, and unresolved issues, while a public site may have changed since the engagement. A concise case gives reviewers useful context and keeps the claim bounded to work you can support.

What evidence belongs in an accessibility portfolio?

Include approved cases, public components or fixes, testing tools, educational resources, and open-source contributions that show how you identify and remove barriers.

For a client case, state what surface you evaluated, the kinds of barriers addressed, the methods you personally used, and what was delivered. Do not upload the report itself unless the client has explicitly made it public.

For public work, link to the artifact that remains understandable without access: documentation, a repository, an article, or an approved case study. A homepage alone may not prove the specific remediation you performed.

What is the fast way to build the accessibility portfolio with IndieShow?

The fast way is to add one IndieShow card per case, tool, or public contribution and group each item by whether it is shipped, active, in progress, or archived.

Use the tag for the kind of work—such as audit, remediation, design systems, or testing—and the description for the barrier, scope, and your role. Link to one safe artifact and leave the optional metric blank unless the client approved a defensible number.

The profile bio can state your accessibility focus and location, while the single page keeps client work, resources, and tools together without mixing their evidence.

Build your IndieShow pageClaim your handle, organise the evidence in the editor, then review the $15 one-year and $30 lifetime publishing options in the dashboard.

How should a before-and-after case be described?

Describe the original barrier and the implemented change in words, then link an approved artifact that demonstrates the result without exposing affected users or private reports.

Do not rely on two unexplained screenshots. Explain which interaction was difficult, how you evaluated it, what changed, and which part you owned.

Avoid permanent compliance claims based on a past engagement because the site and its content may change. Date the case in its destination when relevant and limit the description to the tested scope.

What should stay out of a private accessibility case?

Keep client identities without permission, user-session material, raw issue trackers, private designs, and unresolved vulnerability-like details out of the public portfolio.

An anonymised case still needs a useful boundary, such as the type of product and flow assessed. Generic claims about ‘improving accessibility’ offer less evidence than a narrow description that respects confidentiality.

When no public proof is permitted, the project may have a text-only card or be omitted. Your judgement about sensitive material is part of the professional signal.

Related IndieShow guidance: writing confidential consulting cases · archiving evidence honestly

How does IndieShow keep accessibility evidence accurate?

IndieShow keeps it accurate by making project status, descriptions, links, and optional metrics easy to revise from one dashboard as sites and engagements change.

Recheck destinations and archive cases whose evidence no longer exists. If a client site has changed, update the card so it describes the historical engagement instead of implying you maintain the current experience.

A maintained IndieShow page gives prospective clients one place to review approved cases, public resources, and active work without overstating what was tested.