What WCAG 2.2 means for your awards program (a practical explainer)

When it comes to providing accessibility for your awards program users, the word “compliance” can feel daunting. What does it mean to be compliant with accessibility standards? How do you know if your awards program is accessible for all users?

At its core, accessibility is about making your awards program open to more people. Awards can be awarded to anyone, so at Award Force, we ensure our software works for everyone.

“Accessibility is universal design: when we design for people with disabilities, we’re also creating better experiences for everyone,” said Rachel Martin, product manager and our accessibility champion at Award Force.

“Think of how captions are helpful if you’re in a noisy environment or good colour contrast when you’re out and about on a sunny day and trying to read a message on your phone. Even dropped kerbs and ramps, designed for people with disabilities, are useful for anyone with wheels, be it a pram, bike or scooter. Universal design makes things better for everyone.”

From screen-reader-friendly navigation to keyboard navigation and flexible colour options, video captioning and more, Award Force is fully compliant with WCAG 2.2.

But what do those letters and numbers mean? In this article, we’ll demystify the terminology, explain why it matters in the awards experience, and give insights into what’s in your control as a program manager.

What is WCAG 2.2?

WCAG stands for Web Content Accessibility Guidelines, published by the W3C (World Wide Web Consortium), the international body that sets web standards.

The guidelines serve as a technical standard and explain how to make web content more accessible to people with disabilities. Web “content” generally refers to the information in a web page or web application, including:

• Information such as text, images, and sounds
• Code or markup that defines structure, presentation, etc.

WCAG applies to dynamic content, multimedia, web on mobile devices, and AI web interfaces. WCAG can also be applied to non-web information and communications technologies (ICT) such as native apps, software and documents.

Is WCAG a legal requirement?

WCAG 2.2 is a technical standard, not a law, but it underpins legislation across most major markets, such as the Public Sector Bodies Accessibility Regulations and the Equality Act 2010 in the UK, the Americans with Disabilities Act in the US, and the European Accessibility Act in the EU.

For awards programs, WCAG 2.2 guidelines and related legislation can apply to multi-step forms, file uploads, login flows, judging interface, broadcast communications, and more.

The WCAG guidelines include the four “POUR” principles:

• Perceivable: Users must be able to perceive the information being presented (it can’t be invisible to all of their senses).
• Operable: Users must be able to operate the interface.
• Understandable: Users must be able to understand the information as well as the operation of the user interface.
• Robust: Users must be able to access the content as technologies advance.

If any of these principles are not met, users with disabilities will not be able to use the web—or participate in the awards program.

What’s new in WCAG 2.2, and what does it mean in practice?

WCAG 2.2 contains 87 success criteria in total, which added 9 new criteria and retired one from version 2.1, which had become redundant as modern browsers now handle it automatically.

Here is a breakdown of what’s new:

Clearer keyboard navigation

Two new criteria, Focus Not Obscured and Focus Appearance, require that when someone navigates your site using a keyboard (rather than a mouse), the active element is always clearly visible on screen. Previously, a sticky header or cookie banner could silently hide the focused element.

For awards programs, this affects anyone navigating a submission form or adjudication interface without a mouse, a common need for users with motor impairments.

Accessible login

The new Accessible Authentication criterion means that websites can no longer require users to solve a cognitive test, such as a distorted-text CAPTCHA, as the only way to log in. An accessible alternative must be available.

It also means copy-pasting into password fields must not be blocked. This matters because many users with cognitive disabilities rely on password managers or stored credentials rather than typing from memory.

Less repetitive data entry

Redundant Entry requires that information a user has already provided in the same session is either pre-filled or available to select again. They should not have to type the same details twice.

This is directly relevant to multi-step submission forms, where entrants are often asked to re-enter contact or organisational details they supplied at registration.

Better touch and pointer usability

Two criteria address how interfaces behave on touchscreens and with pointing devices:

• Dragging Movements: any action that requires dragging (reordering items, for example) must also be achievable with a simple tap or click.
• Target Size Minimum: interactive elements such as buttons and links must be at least 24×24 CSS pixels, which is small enough to still give designers flexibility, but large enough to reduce mis-taps on mobile.

Both matter as more entrants and judges complete their tasks on phones and tablets.

Consistent help

If a help mechanism, a chat widget, help link or contact details, appears across multiple pages of your program, it must appear in the same position on every page. Users who rely on support features should not have to hunt for them.

This is something program managers directly control: if you include a help link or contact email in your program pages, keep it consistently placed.

How to meet WCAG 2.2 as an awards program manager

The good news: most of the technical work belongs to your awards management provider, not you. Their job is to ensure the underlying software, such as navigation, authentication flows, form behaviour, touch targets, focus indicators, meets the standard.

Your job is to ensure the content you create and configure does the same.

What to ask your platform provider

Request an accessibility statement or Voluntary Product Accessibility Template (VPAT). This is a formal document that sets out which WCAG criteria the platform meets and where any gaps exist. If your provider cannot produce one, that is worth noting, especially if your program is run by or on behalf of a public sector organisation.

Award Force is fully compliant with WCAG 2.2 AA standards, Revised Section 508 standards and EN 301 549 accessibility requirements. A VPAT is available to download, and accessibility improvements are ongoing and regularly audited against the latest WCAG standards.

What you can control as an awards manager

Here are a few considerations when managing the content around your awards program:

• Images: Add descriptive alt text to any images you upload. Note that Award Force automatically applies alt text to platform images, but you should review alt text on any images you add to your program content.
• Links: Use descriptive link labels like “view eligibility criteria” rather than “click here”
  Documents: Any PDFs you attach should be tagged and screen-reader readable; most accessibility checkers will flag this.
• Video: Include captions or a transcript for any video content in your program. Award Force supports video captions and allows audio descriptions to be uploaded as audio files on the entry form.
• Help content: If you include a help link or contact details across your program pages, keep them in a consistent position.
• Colour and branding: Where your platform allows customisation, check that text meets minimum contrast ratios against its background. Award Force’s default theme is designed for strong colour contrast, and Pro plan accounts and above can adjust colours while maintaining accessibility compliance, with 40+ elements available for colour customisation.

Practical next steps for awards managers

Accessibility is an ongoing exercise for any organisation. Not sure what to do next? Here are some suggested next steps.

• Run a free automated audit on your program’s public-facing pages using a tool such as WAVE.
• Review content you have authored for the common issues listed above.
  Add accessibility to your checklist for any platform procurement or renewal.

Accessibility benefits everyone

Accessibility is about compliance, but also about providing access and an easy user experience for your awards participants.

Users with cognitive disabilities, motor impairments, low vision and mobile-only users all benefit from WCAG 2.2’s new criteria. But these improvements also help attract broader program participation in general. An easy and pleasant user experience helps anyone who might struggle to complete forms online.

By providing a user-friendly and accessible experience, you are proving your organisation and awards are genuinely inclusive, not just technically compliant.