Clear thinking on inclusive web design
Error summaries are often the first thing a resident sees after a failed council tax submission, yet many are vague, unreachable, or disconnected from the fields they describe. This practical audit sets out four questions and a repeatable routine for testing WCAG 3.3.1 and 3.3.3 in UK council tax and benefits forms.
The first tab stop on a council homepage should offer a fast route past repeated navigation. Too often it is invisible, misdirected, or covered by a consent banner. This practical audit explains how to test skip links properly and fix them without disturbing the visual design.
Live captions on council webcasts are frequently treated as a box already ticked, yet nobody measures whether they work in the moment a resident is watching. This guide sets out a repeatable audit routine covering latency, accuracy, speaker attribution and failure states, and argues that a live stream deserves the same scrutiny as a published transcript.
WCAG 2.2's target size minimum is easy to quote and surprisingly hard to apply on a council mobile site. This practical audit guide explains the 24 by 24 CSS pixel rule, its exceptions, and a prioritised repair list for teams working with legacy templates and limited budgets.
Transient toast messages can vanish before screen readers announce them and leave no trace for anyone who looks away. This practical audit examines notification patterns on UK energy account portals and sets out how to design persistent, keyboard-accessible messages for billing and meter-reading updates.
Council tables often look orderly on screen while losing their structure for screen reader users. This practical audit routine helps UK local authority teams test headers, captions, merged cells and responsive layouts without stripping meaning from public data.
Screen reader users can pull every link on a page into a single list, stripped of headings and surrounding prose. This guide sets out a five-point audit routine for UK council and housing association sites, reports the patterns a small sample revealed, and offers plain-English rewrites that keep link text useful without making every line unwieldy.
Date pickers can turn a straightforward Blue Badge renewal into a test of patience, particularly for keyboard and screen reader users. This practical audit routine gives UK local authority teams a repeatable way to test manual entry, focus order, calendar navigation and error recovery.
Session timeouts on UK benefits and council tax portals are often treated as a security necessity rather than an accessibility decision. This practical audit examines warning banners, extension controls, and the data loss that follows an unexpected logout — and sets out a plain-English checklist for time limits that do not penalise slow readers, screen reader users, or people with cognitive disabilities.
Banking apps often use red, amber and green as a shorthand for payment status. This guide sets out a repeatable audit routine for teams that need to prove status messages remain understandable without colour, including WCAG 1.4.1 checks, monochrome testing and the edge cases design systems overlook.
Product images carry much of the information a shopper needs to decide. A practical audit routine can separate useful descriptions from decorative noise, keyword padding and missing text — and give content teams a repeatable standard that satisfies WCAG 1.1.1 without turning every image into an essay.
Cookie consent banners are often reviewed for legal compliance and rarely for accessibility. This opinion piece examines the focus traps, tiny close controls, colour-only status messages and screen reader confusion that recur in UK consent interfaces, and sets out a practical review checklist. It argues that accessible consent is an editorial and design responsibility, not merely a legal one.
Parallax heroes, autoplay video and animated carousels can make UK retail sites unusable for vestibular-sensitive shoppers. This practical guide explains how to respect prefers-reduced-motion across product discovery, product pages, basket and checkout. It includes implementation notes and testing prompts for design and content teams.
Sign-in and password flows remain a neglected weak point in UK accessibility work, from council portals to retail accounts. WCAG 2.2 raises the standard, but passkeys and authentication design need careful handling if they are to include rather than exclude.
Many UK council homepages pass automated checks yet fall apart when a low-vision resident zooms to 400%. This practical guide explains the reflow test in plain English and sets out a repeatable audit routine for web teams.
Accessibility overlays promise quick compliance, but UK organisations need to ask what such tools actually detect, what they hide, and who carries the risk when barriers remain. The Equality Act 2010 is not satisfied by a floating toolbar.
PDFs remain a stubborn accessibility gap in councils, NHS trusts, and government agencies. This guide explains the common failure modes, the hidden cost of retrospective remediation, and a practical route to HTML-first publishing.
Accessibility statements are compulsory, public and read almost exclusively by people who have just hit a barrier. This guide sets out what the 2018 regulations genuinely ask for, examines the omissions that make statements useless, and offers a working structure any UK organisation can adopt in an afternoon.
For five working days I ran my life through the tab key: banking, council tax, train tickets, the weekly shop. What I found was not a catalogue of exotic failures but a handful of ordinary ones, repeated everywhere — and cheap to fix.
Most UK web teams still assess accessibility through visual QA and automated scans, then wonder why screen reader users struggle. This opinion piece examines the gap between sighted assumptions and assistive technology use, and sets out a practical, low-cost route to testing with blind and low-vision people.