WCAG 2.2 Compliance: What Belfast Businesses Must Do in 2026

Understanding WCAG 2.2 Requirements

Web Content Accessibility Guidelines version 2.2 represents the latest evolution of accessibility standards. Published by the World Wide Web Consortium, these guidelines define how websites should work for people with disabilities.

For Belfast businesses, WCAG compliance isn't just an ethical consideration. The Equality Act 2010 requires reasonable adjustments for disabled customers, increasingly interpreted to include digital services. Failing to provide accessible websites creates legal risk alongside the business cost of excluding disabled customers.

This guide explains what's new in WCAG 2.2, what compliance means practically, and how Belfast businesses can work toward accessible websites in 2026.

What's New in WCAG 2.2

Focus Appearance

WCAG 2.2 strengthens requirements for visible focus indicators. When keyboard users navigate websites, they must see clearly which element is currently focused.

The new success criterion requires focus indicators that are at least 2 CSS pixels thick and visible against the background. The area of the focus indicator must also be large enough to be noticeable.

Many websites remove default focus indicators for aesthetic reasons without providing adequate replacements. WCAG 2.2 makes this practice clearly non-compliant.

Target Size Minimum

Interactive elements like buttons and links must be at least 24×24 CSS pixels to meet Level AA requirements. This ensures targets are large enough for users with motor impairments to activate accurately.

Inline links within text are exempt, but buttons, icons, and other standalone interactive elements must meet this minimum size. Many mobile-optimised websites already meet this requirement, but desktop designs sometimes use smaller targets.

Dragging Movements

Any functionality that requires dragging must also be achievable through single-pointer actions. Users who cannot perform drag movements must have alternative ways to complete the same tasks.

This affects slider controls, drag-and-drop interfaces, and other dragging-based interactions. Provide alternatives like clicking specific positions or using buttons to adjust values.

Consistent Help

If websites provide help mechanisms like contact information, chatbots, or help pages, these must appear consistently across pages. Users relying on help features shouldn't have to search for them on each page.

This doesn't require providing help, but if you do provide it, it must appear in consistent locations.

Redundant Entry

Users shouldn't have to enter the same information multiple times within a process. Information provided earlier should auto-populate later fields when possible.

This particularly affects multi-step forms and checkout processes. If users provide their address for shipping, billing address fields should offer to use the same information rather than requiring re-entry.

Accessible Authentication

Login processes must not require cognitive function tests like remembering passwords without assistance, recognising specific objects in images, or solving puzzles.

This means allowing password managers to work properly, not blocking paste functionality in password fields, and ensuring CAPTCHA alternatives exist for users who cannot complete visual or audio challenges.

Compliance Levels Explained

WCAG defines three conformance levels: A, AA, and AAA. Each higher level includes all requirements of lower levels plus additional criteria.

Level A represents minimum accessibility. Websites failing Level A have severe barriers preventing access for many disabled users.

Level AA is the standard target for most organisations. UK legal requirements and best practices typically reference Level AA. The new WCAG 2.2 criteria described above are Level AA requirements.

Level AAA represents enhanced accessibility. While valuable, AAA compliance is not typically expected for general websites due to some highly specific requirements.

Belfast businesses should target Level AA compliance for WCAG 2.2 to meet current best practices and likely legal expectations.

Practical Compliance Steps

Conducting an Accessibility Audit

The first step toward compliance is understanding your current state. An accessibility audit identifies existing barriers and prioritises remediation.

Use automated testing tools like WAVE or axe to identify obvious issues. These tools catch many common problems but cannot identify all accessibility barriers. Manual testing complements automated checking.

Test with keyboard navigation. Can you access all functionality without a mouse? Can you always see which element is focused?

Test with screen readers. Does content make sense when read aloud? Are images described appropriately? Are forms labelled clearly?

Addressing Common Issues

Certain accessibility issues appear repeatedly across Belfast business websites. Addressing these common problems significantly improves accessibility.

Missing Alternative Text: Every meaningful image needs alt text describing its content or purpose. Decorative images should have empty alt attributes.

Poor Colour Contrast: Text must have at least 4.5:1 contrast ratio against its background. Use contrast checking tools to verify.

Inaccessible Forms: Every form field needs an associated label. Error messages should clearly explain what went wrong and how to fix it.

Keyboard Traps: Users must be able to navigate to and away from all elements using keyboard alone. Modal dialogs and complex widgets often trap keyboard focus.

Missing Headings: Proper heading structure helps screen reader users navigate and understand content organisation.

Implementing WCAG 2.2 Specific Changes

For websites already meeting WCAG 2.1 requirements, the specific WCAG 2.2 additions require targeted attention.

Focus Indicators: Review focus styles across your website. Ensure every interactive element has a visible focus indicator meeting the new size and visibility requirements.

Target Sizes: Measure interactive element sizes. Buttons and links in navigation, forms, and content must meet the 24×24 pixel minimum except for inline text links.

Drag Alternatives: Identify any dragging functionality and implement single-pointer alternatives. Slider controls should allow clicking to set values. Drag-and-drop should offer alternative upload methods.

Consistent Help: Ensure help links, chat widgets, or contact information appear in the same position across all pages.

Form Efficiency: Review multi-step forms for redundant data entry. Implement auto-fill from previously entered information where possible.

Authentication Methods: Verify password fields accept paste. Ensure password managers can function. Provide CAPTCHA alternatives.

Building Accessibility Into Development Processes

Design Phase Accessibility

Accessibility is most efficiently addressed when considered from design inception rather than retrofitted after development.

Design with sufficient colour contrast from the start. Specify focus states in design systems. Plan form layouts with clear labelling and error handling.

Include accessibility requirements in design briefs. Designers should understand accessibility implications of their choices.

Development Best Practices

Use semantic HTML that communicates meaning to assistive technologies. Proper heading structures, landmark regions, and form associations provide accessibility foundation.

Test during development rather than only at completion. Catching issues early reduces remediation costs.

Implement accessibility testing in quality assurance processes. Add accessibility checks to pre-launch checklists.

Ongoing Maintenance

Accessibility requires ongoing attention. New content, features, and design changes can introduce accessibility barriers.

Include accessibility checks in content creation workflows. Train content creators on accessible writing and image descriptions.

Periodically re-audit the website to catch issues that may have accumulated.

Legal and Business Considerations

UK Legal Context

The Equality Act 2010 prohibits discrimination against disabled people in providing goods and services. While no specific technical standard is mandated for private sector websites, WCAG 2.1 Level AA is commonly referenced in legal guidance.

As WCAG 2.2 becomes established, expectations will likely shift toward this newer standard. Proactive adoption positions businesses well for evolving legal interpretation.

Public sector websites have explicit accessibility requirements under the Public Sector Bodies Accessibility Regulations 2018. Private businesses working with public sector may face accessibility requirements through contracts.

Business Benefits

Beyond legal compliance, accessibility benefits business outcomes. The spending power of disabled people in the UK exceeds £270 billion annually. Inaccessible websites exclude these potential customers.

Accessibility improvements often enhance usability for all users. Clear navigation, readable text, and logical structure benefit everyone.

Search engines favour accessible websites. Proper structure, alternative text, and clean code all support SEO alongside accessibility.

Getting Professional Help

While many accessibility improvements are achievable internally, professional assistance may be valuable for thorough audits, complex remediation, or training.

Web development agencies with accessibility expertise can audit existing websites, identify priorities, and implement fixes. Ongoing relationships ensure new development maintains accessibility standards.

For Belfast businesses seeking accessible website development or accessibility audits, contact Amigo Studios. We help local businesses create websites that work for everyone, meeting accessibility standards while delivering excellent user experiences for all visitors.

Resources for Further Learning

Several free resources support accessibility learning and implementation.

WebAIM provides comprehensive accessibility resources including articles, tools, and training materials.

W3C Web Accessibility Initiative offers official documentation and supplementary guidance for WCAG implementation.

gov.uk accessibility guidance provides UK-specific context and expectations for digital accessibility.

Investing time in accessibility understanding enables better decisions and more efficient compliance efforts. The resources exist; the commitment to use them determines outcomes.