How to use the CollectivAlly platform

CollectivAlly is designed to help you understand how disabled and neurodivergent people experience your digital services. Not through checklists or assumptions, but by simulating how someone with a particular set of access needs moves through your service when they are trying to get something done that matters to them.

Getting value from the platform does not require a steep learning curve. It just helps to approach it in the right spirit from the start.

Start with what people are trying to do

The most effective way to use CollectivAlly is to begin with tasks.

When someone lands on your website, they are not thinking about your navigation structure or your design system. They have something they want to get done. Your job is to recreate that as clearly and honestly as possible, and then let the personas attempt it. Each persona will simulate how a real person with their particular access needs might move through that journey.

For example:

• On an ecommerce site: find a blue jumper you like and add it to your basket.
• On a travel website: plan a cruise around the Greek Islands and begin the booking process.
• On an education platform: find a course that supports a career goal, check the entry requirements, and work out how to apply.

These tasks give the journey shape. They let the personas move through your service naturally, step by step, in a way that reflects how people actually behave. That is where the most useful insights tend to appear. You start to see where a persona pauses, gets confused, or simply cannot move forward.

Look at the whole journey

Accessibility issues rarely sit in isolation. A form might meet technical standards but still be a struggle to complete. Navigation might work in theory, but only if you already know how the site is structured. Content might be technically readable but still feel overwhelming in practice.

When you focus on a full journey, these things become much easier to spot. You start to see how smaller issues stack up and combine to create a difficult experience overall.

This is where CollectivAlly shifts the conversation. It helps you move away from asking whether something passes or fails, and towards understanding whether the experience actually works for real people.

Build it into how you work

Right now, CollectivAlly supports testing on live websites. That means you can explore real journeys in real environments without needing a complicated setup to get started.

Over time, this will expand to include staging environments, content behind login areas, and eventually apps. The aim is to make this kind of testing possible at every stage of a project, not just after something has already gone live.

The earlier you bring it in, the more useful the insight becomes. Changes are easier to make, and accessibility starts to feel like part of how things are built rather than something bolted on at the end.

Use conversation to explore further

CollectivAlly also includes a chat function that lets you talk directly with the personas. This opens up a different kind of exploration.

You might want to test a concept before you have built anything. You might want to follow up on something that surfaced during a journey test. Or you might simply want to challenge your own assumptions and see where that takes you.

It gives you a way to go beyond observation and spend more time genuinely understanding what is happening and why.

Make curiosity part of the process

At its heart, CollectivAlly is about helping teams feel confident to explore accessibility more openly.

A lot of teams hold back. They are not sure where to start, or they worry about asking the wrong questions or getting things wrong. Often they do not have access to the people they would need to learn from. That hesitation is completely understandable, and it is exactly what CollectivAlly is here to help with.

This is a place where you can ask questions, test ideas and challenge your assumptions without any of that pressure. A place where curiosity leads the work, not compliance targets.

Better accessibility does not come from having everything figured out before you begin. It comes from being willing to explore, to question, and to keep improving the experience over time.