# Supporting Participants With Limited Digital Access

> Digital access varies widely, so a digital-only process quietly excludes people. Here is how to keep staff-assisted and shared-device paths open for everyone.

Published: 2026-07-08  
Author: Julian (OpenCommunity Team)

## Key takeaways

- Digital access varies widely, so a digital-only process quietly excludes some participants.
- Always keep a staff-assisted or shared-device path alongside any self-service option.
- Simple design and patient help matter more than any single feature.

## Why digital access varies

It is easy to assume everyone has a smartphone, an email address, and the confidence to use them. In reality, access varies a great deal. Some participants share one device with a whole family, some have older phones or limited data, some have no reliable internet, and some are simply not comfortable with technology. None of this should stand between a person and a community program.

Designing for this range is not a special accommodation. It is ordinary good practice in community work.

## Never make digital the only path

The most important principle is simple: digital self-service can be an option, but it should never be the only way in. Whenever there is a screen, there should also be a person. If a process quietly requires a device, an email, or digital confidence, it excludes the very people community organizations often most want to reach.

## Offer staff-assisted options

A staff-assisted approach keeps the door open for everyone.

- Let a staff member or volunteer sign someone in or register them.
- Use a shared device at the desk, so no one needs their own.
- Keep a simple paper option available as a fallback.
- Never require a personal email address to take part.

The trade-offs between shared-device and paper approaches are covered in [paper sign-in versus digital sign-in](https://opencommunity.ca/blog/paper-vs-digital-sign-in-sheets/index.md).

## Design for simplicity

When digital tools are used, simpler is kinder. Fewer steps, larger text, and plain language help everyone, not only those with limited access. Ask for the minimum, avoid unnecessary logins, and make it hard to get stuck. If you describe accessibility features, describe only what you have actually confirmed, rather than promising conformance you have not verified.

## Meet people where they are

In the end, supporting people with limited digital access is about attitude as much as tools: patience, no assumptions, and a genuine willingness to help. That same spirit runs through [welcoming newcomers into community programs](https://opencommunity.ca/blog/how-to-welcome-newcomers-community-programs/index.md). Meet people where they are, and technology stays a helper rather than a gatekeeper.

## Questions and answers

### How do we support participants with limited digital access?

Keep a staff-assisted or shared-device path alongside any digital option, use a shared device at the desk, keep a paper fallback, and never require a personal email. Simple design and patient help matter most.

### Should everyone use self-service sign-in?

No. Self-service can be offered, but it should never be the only way in. Whenever there is a screen, there should also be a person able to help, so no one is excluded by a device or a login.

### What about participants without an email address?

Do not require one. Plenty of people do not have or use email. A good process lets someone take part with help from staff or a volunteer, without a personal email or device of their own.

### How do we make digital steps easier?

Keep them short, use larger text and plain language, ask for the minimum, and avoid unnecessary logins. If you describe accessibility features, describe only what you have actually confirmed.

## More from OpenCommunity

- [All resources](https://opencommunity.ca/blog/index.md): Browse every published guide.
- [OpenCommunity features](https://opencommunity.ca/features/index.md): Explore the platform.