The Web Content Accessibility Guidelines (WCAG) are the internationally recognised standard for digital accessibility. They define how websites and digital platforms should be designed and built so content is perceivable, operable, understandable and robust for users with a wide range of abilities and assistive technologies.

WCAG provides specific, testable success criteria rather than subjective opinions, which is why it is referenced by governments, regulators and organisations worldwide.

WCAG defines different levels of conformance: A, AA, and AAA.

• AA focuses on removing the most common and impactful barriers, such as sufficient colour contrast, keyboard accessibility, clear structure, accessible forms and predictable navigation.
• AAA includes stricter and more demanding criteria, such as higher contrast ratios (for example, 7:1 for body text), additional support for cognitive accessibility and tighter controls around timing and interaction.

Not all AAA criteria are practical or appropriate for every website. We help organisations understand which level is required or appropriate for their context.

If required, yes, but not always. Accessibility requirements are agreed upfront on a project-by-project basis.

Some organisations require formal WCAG compliance due to regulatory, sector or risk considerations. Others prioritise inclusive design principles without targeting a specific conformance level.

Our role is to explain the implications of different levels, help assess risk and audience needs and support the level of accessibility that is appropriate for the project.

When accessibility is in scope, requirements are drawn directly from WCAG and may include areas such as:

• Colour contrast and visual clarity
• Keyboard access and focus management
• Semantic structure and heading hierarchy
• Accessible forms, labels, and error messaging
• Text resizing and readability
• Interaction behaviour and motion

The exact requirements addressed depend on the agreed accessibility scope and level of conformance.

No. Accessibility spans design, development, content and ongoing management.

Even well-designed interfaces can become inaccessible if content is added incorrectly or features evolve without care. That's why accessibility needs to be considered across the full lifecycle of a website or digital platform, not just at launch.

Yes. We review existing websites against WCAG guidelines and identify accessibility barriers, risks and priority improvement areas.

Findings are presented clearly, focusing on what will have the greatest impact first rather than exhaustive issue lists.

No. Accessibility needs to be maintained over time.

As content changes, features are added or platforms are upgraded, accessibility issues can be unintentionally reintroduced. We help organisations embed accessibility into their ongoing design, content and delivery processes to reduce regression.

Some platforms make accessibility easier to achieve and maintain than others.

CMSs such as Craft CMS support clean markup, structured content and strong separation between content and presentation. This reduces reliance on inaccessible page builders and makes it easier to maintain accessible outcomes as content evolves.

Platform choice plays a significant role in long-term accessibility success.

No. While accessibility is mandatory in some sectors, inclusive design improves usability for all users.

Clear structure, readable content and predictable interactions benefit everyone, not just users with disabilities. Many organisations pursue accessibility to improve experience quality, reduce risk and align with their values.