DSIT’s Equality Objectives: What They Mean for Digital Accessibility and WCAG Compliance

Equality objectives in the public sector are more than policy statements—they’re commitments that should shape how digital services are planned, designed, built, and maintained. For the UK’s Department for Science, Innovation and Technology (DSIT), equality objectives connect directly to the experience people have when accessing government information and services online. If a website, document, or app is difficult to use with a screen reader, impossible to navigate by keyboard, or unclear for people with cognitive disabilities, equality goals become harder to achieve in practice.

This article explains how DSIT’s equality objectives translate into concrete digital accessibility actions, how they align with WCAG, and how teams can demonstrate progress through measurable outcomes and strong governance.

Why equality objectives matter for digital accessibility

Equality objectives typically focus on reducing barriers for people who share protected characteristics and ensuring fair access to services, information, and opportunities. Digital channels are often the primary (or only) route for interacting with public services—so accessibility becomes a central mechanism for meeting those objectives.

In practical terms, digital accessibility supports equality objectives by:

• Removing functional barriers (e.g., enabling keyboard access for people with motor impairments).
• Improving usability for everyone (e.g., clear headings and plain language help users with cognitive disabilities and users on mobile).
• Reducing reliance on workarounds (e.g., users shouldn’t need to call for help because a form is inaccessible).
• Increasing trust and transparency through accurate accessibility statements and visible progress.

Mapping DSIT’s equality objectives to WCAG outcomes

While equality objectives are often written at a strategic level, they become actionable when mapped to outcomes that can be evaluated against the Web Content Accessibility Guidelines (WCAG). Most public sector digital compliance programs focus on WCAG 2.1 AA (and increasingly plan toward WCAG 2.2), because it provides testable success criteria.

Objective: Improve equitable access to information and services

Digital interpretation: people must be able to perceive content and complete tasks regardless of disability. WCAG-aligned actions include:

• Provide text alternatives for non-text content (images, icons, charts).
• Ensure sufficient color contrast and avoid conveying meaning by color alone.
• Use semantic headings and landmarks so assistive technologies can navigate effectively.
• Make forms accessible with properly associated labels, clear errors, and instructions.

Objective: Reduce disproportionate impacts on disabled users

Digital interpretation: identify barriers that create extra time, cost, or effort for disabled people, then remove them. Examples include:

• Fix keyboard traps, missing focus indicators, and non-operable menus.
• Provide accessible PDFs or, where possible, HTML alternatives.
• Ensure videos have captions and (when needed) audio description.

Objective: Build inclusive services from the start

Digital interpretation: inclusive design should be embedded into discovery, alpha, beta, and live phases. That means:

• Designing with accessibility patterns (skip links, predictable navigation, clear focus order).
• Testing early with assistive technologies and with disabled users.
• Including accessibility acceptance criteria in user stories and definitions of done.

How to turn equality objectives into measurable accessibility goals

Equality objectives are most effective when accompanied by measurable indicators and a feedback loop. For digital accessibility, this generally includes a combination of compliance, usability, and operational metrics.

Compliance metrics (WCAG-based)

• Percentage of pages/templates passing automated checks (with known limitations acknowledged).
• Number of WCAG 2.1 AA issues open vs. resolved by severity.
• Time-to-remediate for critical issues on high-traffic journeys (e.g., sign-in, payments, applications).

User-centered metrics (experience-based)

• Task completion rates for key journeys using keyboard-only navigation.
• Assistive technology compatibility checks (screen readers, speech recognition).
• Support contact rates attributable to digital barriers (a strong signal of exclusion).

Operational metrics (governance-based)

• Accessibility training completion rates for design, engineering, and content roles.
• Percentage of new releases passing accessibility quality gates before deployment.
• Accessibility statement freshness and accuracy (review cadence, evidence links, known issues updated).

Platforms like Corpowid (corpowid.ai) can help operationalize these goals by running automated accessibility audits, supporting continuous monitoring, and helping teams maintain accessibility statements that reflect real testing and remediation progress.

Governance: making equality objectives stick beyond a single project

One of the most common failure modes in public sector accessibility is treating it as a one-time remediation effort rather than an ongoing program. Equality objectives imply durable change—so accessibility needs governance.

What strong accessibility governance looks like

• Clear ownership: named roles for accessibility leadership, design standards, engineering quality, and content.
• Defined standards: WCAG level targeted, supported browsers/AT, and documented patterns.
• Quality gates: automated and manual checks required before releases.
• Procurement controls: accessibility requirements for vendors and third-party components.
• Transparent reporting: progress updates tied to equality objectives and service performance.

If your team works across multiple regulatory environments, it can help to look at parallel frameworks. For example, Section 508 compliance and documentation practices like a VPAT show how structured evidence and repeatable processes make accessibility easier to manage at scale.

Inclusive design practices that directly support equality objectives

Inclusive design is how equality objectives show up in day-to-day delivery. The goal is not just to “meet WCAG,” but to create services that are resilient across devices, environments, and user needs.

Content design: clarity, structure, and plain language

• Use descriptive headings to support scanning and screen reader navigation.
• Keep paragraphs short and use lists for steps and requirements.
• Avoid unexplained acronyms; define terms users may not know.

Interaction design: predictable, forgiving, and keyboard-friendly

• Ensure focus states are visible and consistent.
• Make error messages specific and actionable, and link them to fields.
• Give users enough time and avoid motion that can trigger vestibular issues.

Engineering: semantic HTML and robust components

• Prefer native elements (buttons, inputs) before custom controls.
• Use ARIA carefully—only when needed—and test with real assistive tech.
• Build reusable accessible components to reduce repeat defects.

For teams managing multiple digital products (including mobile), aligning audit approaches across platforms is key. A helpful reference is this WCAG-aligned public sector mobile app accessibility audit approach, which translates standards into repeatable testing steps.

Accessibility statements: turning commitments into accountability

Accessibility statements are often where equality objectives become visible to the public. A strong statement does more than declare intent—it sets expectations and provides routes for feedback and remediation.

What an effective accessibility statement should include

• Compliance status (e.g., fully compliant, partially compliant) and the standard referenced.
• Known issues listed plainly, with workarounds where possible.
• Dates of testing, methodology, and who carried it out (internal/external).
• Contact method for reporting problems and requesting alternatives.
• Escalation path if users are dissatisfied with the response.

Maintaining statements can be challenging when content changes frequently. Using a toolset such as Corpowid (corpowid.ai) can help teams keep audit evidence, monitoring insights, and statement updates connected—so the statement reflects the current state of the site rather than a one-off snapshot.

Learning from global accessibility and compliance trends

DSIT’s equality objectives sit within a broader global movement toward enforceable digital accessibility. The EU’s evolving landscape, for example, is reshaping how organizations prepare for compliance and governance—see the EAA and BFSG overview for how legal requirements translate into WCAG-based expectations.

It’s also valuable to view accessibility as part of digital inclusion rather than a narrow checklist. This perspective helps teams design services that work for people with disabilities, limited connectivity, older devices, and varying digital literacy. For a practical example of inclusion-led service building, see Rwanda’s digital inclusion and WCAG-aligned services.

Putting it all together: a practical checklist for DSIT-aligned delivery

• Translate equality objectives into WCAG-based acceptance criteria for priority journeys.
• Audit templates and components first to reduce defects across the whole estate.
• Combine automated checks with manual testing (keyboard, screen readers, zoom, reflow).
• Set KPIs for remediation speed and prevention (quality gates, training, reusable components).
• Publish and maintain accurate accessibility statements with clear feedback routes.
• Monitor continuously so new releases don’t reintroduce barriers.

Equality objectives are ultimately about outcomes: whether people can use digital services independently, confidently, and without unnecessary friction. When DSIT’s objectives are linked to WCAG and implemented through inclusive design and governance, accessibility becomes a measurable, sustainable part of delivering fair public services.