# Website Accessibility Fixes to WCAG 2.2 AA Source: https://dijitulsupport.co.uk/website-accessibility-fixes/ Updated: 2026-10-10 > dijitul support audits and fixes website accessibility problems for UK businesses, working to WCAG 2.2 level AA. We test with automated tools, keyboard-only navigation and a screen reader, then fix colour contrast, missing labels, alt text, focus states and heading structure. Smaller fixes are £45 an hour + VAT; full audits and remediation are quoted. ## Common symptoms - You cannot use your menu or forms with the keyboard alone - Grey text on white, or white text on a pale image, is hard to read - Images have no alt text, or alt text like "IMG_4032.jpg" - Form fields have placeholder text but no labels - A customer or client has complained they cannot use the site - A tender or contract requires a WCAG 2.2 AA accessibility statement ## Key facts - WCAG 2.2 was published by the W3C in October 2023 and level AA is the usual target - Normal text needs a contrast ratio of at least 4.5:1, large text 3:1 - WCAG 2.2 added criteria including Focus Not Obscured, Target Size (Minimum) and Accessible Authentication - Automated tools find only part of the problems; we also test by keyboard and with a screen reader - UK businesses have duties under the Equality Act 2010 to make reasonable adjustments for disabled people - We do not recommend accessibility overlay widgets as a fix - Small fixes £45 an hour + VAT; full audits quoted ## What WCAG 2.2 AA means in practice The Web Content Accessibility Guidelines (WCAG) are the international standard for accessible websites, published by the W3C. Version 2.2 was published in October 2023, and level AA is the benchmark used by the UK public sector, in most tenders and in accessibility statements. It is organised around four principles: content must be perceivable, operable and understandable, and it must work reliably with assistive technology. In plain terms, people should be able to read your content whatever their eyesight, use the site with a keyboard or switch device instead of a mouse, understand forms and error messages, and use screen readers that rely on correct code. For private businesses, the Equality Act 2010 expects reasonable adjustments for disabled customers, and an inaccessible website can fall short of that. ## The problems we fix most often - **Colour contrast.** Text needs at least 4.5:1 contrast against its background (3:1 for large text), and buttons and form borders need 3:1. Pale grey body text and text over photos are the usual failures. - **Keyboard access.** Dropdown menus that open only on hover, custom buttons built from divs, and pop-ups that trap focus or cannot be closed with Escape. - **Visible focus.** Themes that remove the focus outline, so keyboard users cannot see where they are. WCAG 2.2 also requires the focused item is not hidden behind sticky headers or cookie banners. - **Forms.** Missing labels, errors shown only in red, and CAPTCHAs that are hard to complete. WCAG 2.2's Accessible Authentication criterion means logins should allow paste and password managers. - **Images and media.** Meaningful alt text, empty alt on decorative images, captions on videos. - **Structure.** One H1, headings in order, proper lists and landmarks, link text that makes sense out of context (not "click here"). - **Target size.** WCAG 2.2 asks for interactive targets of at least 24 by 24 CSS pixels, or enough spacing, which catches tiny social icons and close buttons. ## How we test Automated checkers such as axe, WAVE and Lighthouse are a good start, but they can only catch some issues: they can tell an image has no alt text, not whether the alt text is meaningful. So dijitul support combines them with manual checks: we tab through every template using only the keyboard, test with the NVDA screen reader on Windows and VoiceOver on Apple devices, zoom to 200 and 400 percent to check reflow, and review content for clear headings and links. You get a prioritised list, with the issues that block people at the top. ## Why we do not recommend overlays Accessibility overlay plugins promise compliance with one line of code. They do not fix the underlying markup, can interfere with the screen readers disabled people already use, and many accessibility specialists and disabled users have criticised them publicly. They are not a substitute for fixing the site. We remove them where they cause problems and fix the real issues instead. ## Accessibility statements and ongoing work Once the main fixes are done, we can help you publish an accessibility statement explaining your standard, known issues and how people can ask for help. Accessibility then needs keeping up: new pages, images and plugins can reintroduce problems. Content editors are often the biggest factor, so we give simple guidance on alt text, headings and link text. For edits we make on your behalf, see content updates. ## Cost Targeted fixes, such as contrast, focus styles, form labels or a menu that does not work by keyboard, are **£45 an hour + VAT**. A full audit of a site's templates and the resulting fixes are quoted, since the work depends on the theme and number of templates. A Business or Complete plan (£50 or £99 a month + VAT) gives you monthly hours to work through the list steadily. Ask for a quote. ## FAQs ### Is website accessibility a legal requirement in the UK? Public sector bodies must meet the Public Sector Bodies Accessibility Regulations 2018. Private businesses have duties under the Equality Act 2010 to make reasonable adjustments for disabled people, which can include their website. Meeting WCAG 2.2 AA is the clearest way to show you have taken accessibility seriously. ### What changed in WCAG 2.2? WCAG 2.2, published in October 2023, added criteria including Focus Not Obscured, Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication. It also removed the old 4.1.1 Parsing criterion. Most sites built to WCAG 2.1 need only modest changes. ### Will an accessibility plugin or overlay make my site compliant? No. Overlays add a toolbar but do not fix the underlying code, and can clash with screen readers disabled people already use. dijitul support fixes the actual issues: contrast, keyboard access, labels, alt text and structure. ### How do you test website accessibility? dijitul support uses automated tools such as axe and WAVE, then tests manually: keyboard-only navigation, the NVDA and VoiceOver screen readers, zoom to 400 percent and a content review. Automated tools alone miss many real barriers. ### How much do accessibility fixes cost? Targeted fixes are £45 an hour + VAT with a 30-minute minimum. Full WCAG 2.2 AA audits and remediation are quoted because the effort depends on the number of page templates, forms and third-party components on the site. ## Pricing and contact This work is quoted to fit. Request a quote at https://dijitulsupport.co.uk/quote/ or call 01623 650333.