🎉

Revolution wins Sustainable Business of the Year 2026!

Revolution Logo Inverted
X
SPACES logo
Case Study — Platform

Building an Accessible Home for a Global Nature Initiative

A WCAG 2.1 AA-compliant campaign website for an initiative working to protect 30% of the world's natural ecosystems.

Sector Global Nature Preservation
Established 2025
Services UX/UI · Web Development

Key Results — SPACES for Nature

Results

WCAG 2.1 Level AA Achieved

AA

Full compliance from the very start

Lighthouse Accessibility

100/100

Perfect score (Post-launch audit)

Weeks Delivery

10

From strategy to launch

Specialists Deployed

4

Project Manager · UX/UI · Web Development · Strategy

01 — The Client

A global mission that needed a global stage

SPACES for Nature is the flagship campaign initiative of Campaign for Nature, a global NGO working to support nations in achieving their environmental and climate commitments.

Their focus is to drive the 30x30 agenda: protecting 30% of the world's natural ecosystems by 2030.

Their audience includes heads of state, international donors, conservation organisations and local community partners in dozens of countries.

That sort of reach comes with the responsibility to ensure the platform is accessible to everyone who visits it.

When Campaign for Nature engaged us to build the SPACES platform, there was no existing website to work with. This was a completely fresh build and an opportunity to do it right from the very first line of code.

AA

Standard

2.1 Level AA

WP

Platform

Custom Theme

10W

Timeline

From strategy to launch

Mission Alignment

SPACES works to protect the planet's most vital natural spaces. Revolution is a Certified B Corporation® whose own work is aligned with environmental sustainability. So for us, this was more than a client project. We shared a purpose.

02 — The Challenge

Accessibility isn't a feature, it's a requirement

Most web projects treat accessibility as an afterthought, like a checklist item bolted on at the end. This results in websites that exclude millions of users who rely on assistive technologies to navigate the web.

SPACES had no existing website, which meant there was no legacy of poor decisions to unpick.

But this clean slate came with its own challenge. Accessibility had to be designed and engineered into every decision and design element from the outset. From information architecture and colour palette through to component-level HTML, keyboard interaction patterns and screen reader behaviour.

We identified the WCAG 2.1 AA requirement proactively and brought it to the table as an essential part of the build. We reasoned that for an organisation operating at the intersection of global policy and environmental advocacy, which engaged with NGOs, governments and civil society partners, an inaccessible platform would have been a contradiction of their values.

WCAG 2.1 Level AA compliance is built on four core principles: Perceivable, Operable, Understandable and Robust (POUR). Meeting those standards requires deliberate, systematic work across every layer of a site, including design, markup, interaction and content.

For a content-rich website to meet AA requirements, our entire team had to treat accessibility not as a quality assurance step, but as a design constraint.

The Brief

Build a WordPress platform for a global conservation campaign that would be fully compliant with WCAG 2.1 Level AA, tested with assistive technology and delivered in 10 weeks.

👁

Perceivable

Information needs to be presented in such a way that it can be perceived by everyone who visits the website, regardless of ability. This includes image alt texts, colour contrast, captions and adaptable content structure.

⌨️

Operable

All functionality has to be accessible through a keyboard, not just a mouse. There needs to be sufficient time for visitors to interact. No content that triggers seizures. Clear navigation and skip mechanisms.

💬

Understandable

Text must be readable and predictable. Input assistance helps users avoid and correct mistakes. The language used is clearly identified at page and element level.

🏗

Robust

Content can be reliably interpreted by current and future assistive technologies. Clean, valid semantic HTML that works regardless of how the website is being accessed.

03 — What We Built

Accessibility
built in, not bolted on

Every accessibility requirement was addressed as a design and engineering decision, not a retrospective fix. Here is how we approached each layer of the SPACES build.

01 – Foundation Layer

Semantic HTML & Document Structure

Robust Perceivable

Every page was built with a clean, logical heading hierarchy, H1 through H6, ensuring screen readers can navigate and understand the content structure without visual cues.

We included best-practice page-structure elements throughout, so that assistive technology users have the ability to jump directly to relevant sections on any page.

Custom post types, such as case studies and donor spotlights, were all templated and coded so that assistive technology can easily understand how the page fits together.

02 – Design System

Colour Contrast & Visual Design

Perceivable

The SPACES brand palette was assessed and refined specifically to meet WCAG 2.1 AA contrast ratios.

We implemented a minimum contrast ratio of 4.5:1 for body text and 3:1 for large text and UI components. Every colour pairing used across the site (text on backgrounds, buttons, form fields, link states and interactive elements) was verified against these standards.

Where the brand direction required specific colour choices, our lead creative, Sebastian, worked within those constraints to find combinations that satisfied both the aesthetic vision and the compliance requirements.

No visual design decisions were taken that sacrificed accessibility.

03 – Interaction Layer 

Keyboard Navigation & Focus Management

Operable

Every interactive element on the website, such as dropdown menus and buttons, is fully navigable using only a keyboard.

Focus states (design elements that let a user know which part of the website they are on or which element is currently active) were designed to be clearly visible, meeting the enhanced focus indicator criteria. This means keyboard users always know exactly where they are on any given page.

Skip-to-content links were implemented site-wide, allowing users who navigate by keyboard or screen reader to bypass repeated navigation blocks and get directly to the page content.

We also made sure that users who rely on keyboards to navigate through a website wouldn’t accidentally lose the ability to move through a page because they were trapped on inert background content.

04 – Assistive Technology

ARIA Labels & Screen Reader Support

Robust Perceivable

ARIA (Accessible Rich Internet Applications) attributes were applied wherever native HTML code alone might leave room for misinterpretation by screen readers.

This was particularly important for custom interactive components, icon-only buttons, dynamic content regions and complex navigation patterns.

Every ARIA implementation was tested against the ARIA authoring practices to ensure correct usage, since incorrect ARIA is often worse than no ARIA at all.

The site was tested with real screen reader software (NVDA on Windows + VoiceOver on macOS) to verify that the announced content matched the visual experience, and that all interactive elements were correctly identified, labelled and operable.

05 – Content Layer

Images, Media & Alt Text

Perceivable

Every single image on the platform, including editorial photography, data visualisations, country maps and partner logos, was given descriptive, contextually appropriate alt text. Decorative images were marked with empty alt attributes so screen readers would skip them.

The WordPress content management system was configured to prompt content editors to provide alt text where required before publishing. This puts accessibility considerations at the heart of the editorial workflow.

For complex images such as charts or maps carrying meaningful data, additional text descriptions were provided in adjacent content. This ensures the information is accessible to all users, regardless of whether or not they can view the image clearly.

06 – Understandable Layer

Forms & Input Assistance

Understandable Operable

All forms, including the contact form and any subscription or data capture fields, were built with properly associated labels, clear error messages and input validation that communicates mistakes in an accessible way.

Error messages are coded so that they are always associated with the relevant input field on a form and announced to screen readers on submission. So users know exactly what needs correcting without having to visually scan the page.

04 — The Results

Compliant from the start. Verified by audit

Following the build, we ran a formal accessibility audit using automated tools, including Lighthouse and Axe, alongside manual testing with assistive technology. The results confirmed full WCAG 2.1 Level AA compliance across all key templates and content types.

The Lighthouse accessibility audit returned a perfect score of 100, a result achieved by fewer than 1% of websites on the web.

100

Lighthouse Accessibility Score

Perfect score · Industry benchmark: 70–85

AA

WCAG 2.1 Compliance Level

Achieved across all page templates

10w

Delivery Timeline

Strategy → design → build → tested → live

0

Critical Accessibility Failures

Zero blockers according to the launch audit

6+

Custom Post Types Built

All WCAG compliant by default

4

POUR Principles Met

Perceivable · Operable · Understandable · Robust

Why This Matters

Globally, around one in six people live with some form of disability. For an organisation whose mission is to build broad, inclusive coalitions of support for nature protection, and includes government ministers, NGO partners and civil society voices, an inaccessible website would have been a failure of principle as much as a failure of design.

SPACES now has an online presence that everyone can access.

Your work is helping us to protect some of the most wonderful places in the world.

Joel Dunn
Director, SPACES Secretariat · Campaign for Nature
05 — Why Revolution

Values that run deeper than code

Accessibility is at the heart of the kind of worldwide web we think should exist.

We proactively identified the WCAG requirement and built it into the project scope.

For us, the SPACES website was an ideal project. The initiative seeks to protect the natural world. That’s a goal we actively support ourselves by planting native trees here in Ireland, operating sustainably and choosing clients whose values align with our own.

These are all part of the commitments we have made as one of the few B Corp-certified digital agencies in Ireland.

Shared Mission

"Two organisations that believe the world should work better — one protecting nature, one building a better internet."

Our B Corp certification is a verified commitment to the same values behind SPACES: accountability, transparency and an impact beyond profit.

Your website should work for everyone

Whether you need a WCAG-compliant build from scratch or an accessibility audit of your existing site, we’re the people to talk to.

Shapes of tropical palm tree crowns against the sky
Related Case Study

TFFF: Building a Campaign-Grade Web Platform in Record Time

The Tropical Forest Forever Facility (TFFF) was the centrepiece of the Climate 30×30 Summit in Belém, Brazil, a critical milestone for environmental diplomacy. Our job was to build a website worthy of this landmark initiative.