Meeting at His Studio in Quebec City

In a peaceful neighbourhood of Quebec City, I met Jean-Sébastien Ouellet in his studio-office, a space where digital and Indigenous culture harmoniously converge. The shelves are filled with books on First Nations, ranging from historical accounts to contemporary studies on cultural self-determination. On his desk, a screen displays lines of code, reflecting his ongoing work on a complex multilingual project.

Jean-Sébastien, an independent web developer for over twelve years, has specialized in digital projects for Indigenous non-profit organizations. His experience is rich with clients such as the Cree Nation Government and the Niskamoon Corporation. With expertise in sovereign hosting and accessibility, he has become an indispensable reference in his field.

1. Career Path: How to Specialize in Indigenous Projects

Journalist: How did you steer your career towards Indigenous web projects?

To understand the client context, read our presentation of Niskamoon Corporation and its mission in Eeyou Istchee.

Jean-Sébastien Ouellet: My career really took shape when I was at UQAM, where I studied computer science. At the time, I didn’t have a clear vision of the direction my career would take. In 2013, I had the chance to work on a project for the Mohawk Council of Kahnawake. I got this contract somewhat by chance. A former colleague recommended me, and I was immediately fascinated by the unique challenges this project presented. This first contact with the world of Indigenous NPOs opened my eyes to a niche that required a very particular approach. I discovered that it wasn’t simply about transposing a conventional model onto a website, but about understanding and respecting the cultural and linguistic specificities of the communities. I quickly realized that each project was unique and required attentive listening and thorough consultation with community members. This motivated me to specialize further, participate in specific training, and build my practice around these principles of respect and co-construction.

2. First Structuring Project and Lessons Learned

Journalist: Can you tell us about your first structuring project and the lessons you learned from it?

Jean-Sébastien Ouellet: My first structuring project was to develop an institutional site for a Cree NPO. It was a formative experience in many ways. The technical challenges were numerous, particularly regarding the implementation of syllabic languages and the management of multilingual content. This project taught me the importance of preliminary consultation. You cannot simply transpose existing models from other projects. Each community has its own expectations and sensitivities, and it’s crucial to understand them before starting development. I also learned that listening to elders and community leaders is essential. They offer a valuable perspective that must guide the project’s development. It was a lesson in humility and a constant reminder that technology must serve the needs and values of those it aims to support.

3. Cultural Challenges: Co-Construction and Consultation

Journalist: What cultural challenges do you face in co-constructing projects with Indigenous communities?

The ethical framework of reference is defined by the First Nations OCAP principles.

Jean-Sébastien Ouellet: The cultural challenges are numerous and require a very delicate approach. One of the most important aspects is respecting co-construction protocols. For example, the OCAP principle — Ownership, Control, Access, and Possession — is fundamental. It stipulates that communities must have full control over their data. This means that every image, every text must be validated by the band council or elders before being published. It is also crucial to consider traditional visual codes without falling into pastiche or clichés. It’s about respecting cultural authenticity while using modern elements of web design. Each project is unique, and it is essential to integrate these elements in a way that is both respectful and innovative.

This same OCAP-driven principle of community data ownership underpins digital preservation of Inuit and Cree languages, where communities similarly retain full control over which archived materials and recordings are published or kept private.

4. Technical Aspects: Hosting, Accessibility, Multilingual Inuktitut/Cree

Journalist: How do you manage technical aspects like hosting, accessibility, and multilingual support for Inuktitut and Cree languages?

Jean-Sébastien Ouellet: Technically, UTF-8 encoding and the use of Canadian Aboriginal syllabics (UCAS) are essential for supporting Inuktitut and Cree languages. Specialized fonts like Pigiarniq and Euphemia are often necessary to ensure readability and correct rendering of syllabic characters. Regarding accessibility, I ensure that all projects comply with WCAG 2.2 AA standards. This includes testing with screen readers capable of reading syllabics, although this remains a challenge due to the lack of documentation and developer support. The community develops little documentation on this subject, which means we often have to innovate and find solutions as we go.

5. Digital Sovereignty: Canada/Quebec Hosting vs. US Cloud

Journalist: What is your approach to hosting and digital sovereignty for Indigenous projects?

Jean-Sébastien Ouellet: The issue of digital sovereignty is crucial. For the projects I manage, hosting is generally located in Canada, via Cloudflare or AWS Canada (CA-CENTRAL-1). The idea is to avoid the American cloud as much as possible, especially for sensitive data, due to the Patriot Act, which allows the US government access to this data. It is important to consider the sovereignty of Indigenous data and ensure that it remains under the control of the communities. I often mention the example of the First Nations Health Authority, which developed its own sovereign cloud. It’s an inspiring initiative that shows the way forward for other organizations.

Important: the technical challenges specific to Indigenous web projects concentrate on three axes — language support (UTF-8, Canadian Aboriginal syllabics/UCAS, Pigiarniq/Euphemia fonts for Inuktitut and Cree), WCAG 2.2 AA accessibility tested with screen readers still poorly equipped for syllabics, and data sovereignty through Canadian hosting (Cloudflare, AWS CA-CENTRAL-1) that avoids the American Patriot Act.

6. Remote Maintenance in the North: Connectivity, Telemaintenance

Journalist: How do you manage site maintenance in remote northern regions?

To understand how the web developer profession is evolving today, see the guide Becoming a web developer in 2026 on CodeYourWeb.

This remote collaboration logic echoes the experience of remote work by an Inuit entrepreneur in Salluit.

For a concrete IT case study, see our Hyper-V server fiber/satellite deployment in northern environments.

Jean-Sébastien Ouellet: Remote maintenance is a challenge, especially in remote villages like Mistissini or Kuujjuaq. Connectivity, often provided by Tamaani, can be uneven, complicating telemaintenance. To address this, I use local backups combined with cloud backups. CI/CD deployment via GitHub Actions is also a standard practice to automate updates. However, it is sometimes necessary to visit on site once or twice a year to manage issues that cannot be resolved remotely. This hybrid approach minimizes service interruptions while respecting logistical constraints.

7. Budget and Economic Viability of NPO Projects

Journalist: What are the budgetary and economic viability issues of projects for Indigenous NPOs?

For general technical services offered by Soleica, see the web development services page.

Jean-Sébastien Ouellet: Budgets for an institutional site generally range between 20,000 and 80,000 CAD, with annual maintenance costs of 8,000 to 15,000 CAD. Funding models, often supported by Canadian Heritage, require multi-year planning. This is essential for ensuring the long-term viability of projects. A common pitfall is underestimating costs, especially by non-specialized providers. Consultation, validation, and respect for protocols can extend timelines, but they are essential for the project’s success. It is crucial to budget accordingly and be transparent with clients about the actual costs.

8. Common Mistakes by Non-Specialized Providers

Journalist: What common mistakes do non-specialized providers make in Indigenous projects?

Jean-Sébastien Ouellet: One of the most common mistakes is using unvalidated stock images, which can be culturally inappropriate. Additionally, some use Google Translate to translate from French to Inuktitut, which is often catastrophic. Linguistic nuances are lost, and it can be perceived as disrespectful. Using generic WordPress templates without customization is another frequent mistake. This ignores the OCAP protocol and underestimates the importance of consultation and content validation. Finally, there is often an underestimation of the time needed to fully understand and integrate the cultural and linguistic needs of the communities.

9. Advice to a Developer Looking to Reorient to This Market

Journalist: What advice would you give to a developer wishing to reorient to this market?

Jean-Sébastien Ouellet: I recommend taking specific training, such as those on the OCAP protocol or certificates offered by the Métis Authority at Concordia University. Networking is essential, and it is beneficial to connect with NPOs through initiatives like the Indigenous Innovation Initiative. Starting with volunteer contracts can help gain experience and make a name in the field. However, it is crucial to maintain a continuous learning posture and stay attentive to the needs and feedback from the communities. This kind of skill-building ideally starts much earlier: our interview with a youth digital literacy coordinator in Nunavik shows how Northern schools are already preparing this technology talent pipeline.

Tip: to pivot into this market, start with training on OCAP principles, connect with NPOs through initiatives like the Indigenous Innovation Initiative, and take on a first volunteer or reduced-rate contract to build a track record — specialisation is built through trust accumulated project after project, not by adding a few keywords to a portfolio.

10. Future: AI, Accessibility, Content in Indigenous Languages

Journalist: How do you see the future of digital technologies in this field?

Jean-Sébastien Ouellet: The future is promising but complex. Language models like LLMs, trained on Inuktitut and Cree corpuses, like the Aalla Aalla project, open up interesting possibilities. However, there is a risk of cultural appropriation if these technologies are not developed with the active participation of communities. Machine translation may be acceptable for a first draft, but human validation will always be necessary. I also think accessibility will be significantly enhanced between 2026 and 2030, as it is a constantly evolving area that is increasingly considered.

Quick Questions — Common Misconceptions About Indigenous Web Projects

  1. “A generic WordPress site is enough for an Indigenous NPO.”

    False. Each project must be custom-designed to respect cultural and linguistic specificities.

  2. “French content can be translated into Inuktitut with Google Translate.”

    Absolutely false. Automatic translations lack precision and respect for cultural nuances.

  3. “US hosting is interchangeable with Canadian hosting.”

    False. Canadian hosting is preferable to ensure data sovereignty and avoid the American Patriot Act.

  4. “Images must absolutely represent traditional elements (drums, feathers).”

    False. Images must be chosen in consultation with communities to avoid stereotypes and respect authenticity.

  5. “Consulting elders unnecessarily delays projects.”

    False. Consultation is essential to ensure that the project respects and integrates the community’s values and needs.

  6. “Multilingualism increases the cost by 50%.”

    Not necessarily. While multilingualism can increase costs, they are not as high if the project is well-planned from the start.

3 Key Takeaways

  • Consultation and respect for cultural protocols are essential for the success of Indigenous web projects.
  • Sovereign hosting in Canada is crucial for data protection and respecting community rights.
  • Technical challenges, particularly in multilingualism and accessibility, require specialized expertise and a commitment to continuous learning.