Website accessibility: baseline requirements and a quick audit
Website accessibility is usually framed as care for users with disabilities. In practice it makes a site easier for everyone: for someone reading a phone in bright sun, for an older relative, and for a customer on an unstable mobile connection. Below are the baseline requirements, a checklist and a way to audit a site in half an hour.
Website accessibility: who it actually helps
Screen reader users and people with visual, hearing or motor impairments come first. But the circle is wider: age-related vision loss, temporary limits such as a broken arm, older low-cost smartphones, and slow connections where images fail to load. Many people in Uzbekistan open sites on a phone, on the move and in bright light, so these requirements concern ordinary visitors, not a narrow group.
There is also a side effect: nearly every accessibility requirement is at the same time a markup quality requirement, such as meaningful headings, image descriptions and clear link names. This does not guarantee rankings in Google, but a clean structure helps a search engine understand what a page is about.
On cost, the rule is simple: building accessibility in at the design and layout stage is cheaper than reworking a finished site. Fixing a colour in a mockup takes minutes; changing it across a hundred pages is a separate task.
Baseline requirements for text, colour and size
Contrast. The WCAG standard recommends a ratio of at least 4.5 to 1 for regular text and 3 to 1 for large text. The most common failures are light grey text on white, white text on a bright button, and captions over photos without a dark overlay. Check colours with a contrast calculator or the browser developer tools.
Readability. Body text of at least 16 pixels, line spacing of roughly 1.4 to 1.6, and lines no longer than 70 to 80 characters. Do not block zooming on phones: the user-scalable=no parameter gets in the way of anyone who needs to enlarge the page.
Tap targets. A good guideline for buttons and links is at least 44 by 44 pixels with a gap between neighbours. This matters most for menus, the ru/uz/en language switcher and the form submit button. And never convey meaning by colour alone: “fields highlighted in red” are useless to someone with colour blindness.
Images, forms and page language
Meaningful images get alt text that describes the point: “Diagram of website development stages”, not “image1.jpg”. Decorative images get an empty alt. If an image is a link, its alt describes the destination. Repeat text that lives inside banners in ordinary markup.
Every form field is tied to a real label, because a placeholder disappears as you type and does not count as one. Use proper field types for phone and email so the right keyboard opens on a smartphone. Describe errors in words next to the field (“Enter the number in the +998… format”), not only with a red border.
On a multilingual site, set the page language in the lang attribute (ru, uz, en): screen reader pronunciation depends on it. Add subtitles to videos with speech.
Keyboard navigation and page structure
Go through the whole site with the Tab key without touching the mouse. You should see where focus is, reach every link and button, open menus, and close a modal window with Escape. The tab order should match the visual order.
Typical mistakes: a removed focus outline “so it does not spoil the design” (replace it with your own instead of deleting it); modal windows and menus from which focus escapes to the page underneath; clickable divs instead of real buttons, which a keyboard cannot activate.
Structure: one h1, then h2 and h3 in order without skipping levels, the main content in a main element and the menu in nav. Screen readers build navigation from these, and search engines build their understanding of the page.
How to audit website accessibility in half an hour
First 5 minutes: run Lighthouse in Chrome and open the Accessibility tab. It lists automatically detectable problems such as contrast, missing alt and labels, and a broken heading hierarchy. Automation catches only part of the issues; the rest are visible only by hand.
Next 15 minutes: complete a key flow (an enquiry or an order) using only the keyboard; zoom to 200% and check the layout holds; disable images and see whether the meaning survives; open the site on a phone at full brightness in a well-lit room or outdoors.
Last 10 minutes: turn on VoiceOver on a Mac or iPhone, or TalkBack on Android, and listen to the home page and a form. Write down what you find and split it into critical (the form cannot be submitted) and cosmetic.
FAQ
Does a small brochure site need accessibility? Yes. The basic items, which are contrast, font size, alt text and form labels, cost almost nothing if done from the start.
Does accessibility affect SEO? There is no guaranteed boost, but structure, headings and alt text help search engines understand the page better.
How much does auditing and fixing an existing site cost? As a rough guide, 1,000,000 to 5,000,000 UZS depending on the number of templates and the complexity of the interface. When a site is built from scratch, the baseline requirements are part of normal work.
Can an accessibility overlay widget be enough? No. It does not replace correct markup and contrast, and it only masks some problems.
What to include when ordering a website
Put the requirements in the brief: WCAG contrast, keyboard operation, alt text, form labels, and a Lighthouse check before acceptance. Ask to see the audit result for the key pages; it is quick and prevents disputes.
If you need a site with these points built in from the start, the 4 Digital studio offers turnkey website development from 1,399,000 UZS. The final price depends on the number of pages, languages and features, and we name it after discussing the task.