Visible and readable
Contrast, font size and zoom: why pale gray text on a white background lets down even readers with good eyesight.
a site for everyone: an accessibility reference
Wpget: how to make a website that works for everyone
All kinds of people use your website. Some zoom text to twice its size, some listen to the page with a screen reader, some can't use a mouse, and some are reading on a phone in bright sunlight. This reference explains what gets in each person's way and shows how to remove those barriers yourself: calmly, step by step, and without an expensive redesign.
An accessible website isn't a separate version for special visitors. It's the same page, just one that somebody remembered to check.
Where to start
Works with a keyboard
How to get through a page without a mouse, where focus must be visible, and why no button should ever be click-only.
Clear forms
Field labels, plain error messages and submitting without guesswork: the things that decide whether someone writes to you or leaves.
Video and audio
Captions, transcripts and sign language interpretation: how they differ and where a small website should sensibly begin.
Reference sections
- Guides
Step-by-step guides to making text readable, organizing a page with clear headings and building a contact form that works for everyone. Plus the article catalogue.
- Tools
How to check a site yourself: browser zoom, the keyboard, high contrast mode, the built-in screen reader, color contrast checks and a markup validator.
- Comparisons
Conformance levels A, AA and AAA; alt text vs. captions vs. transcripts; subtitles vs. transcripts vs. sign language, laid out in comparison tables.
- Fixes
What to do when focus is invisible, text breaks on zoom, a button has no label, form errors make no sense or a video has no captions.
- Risks
Accessibility traps: impossible CAPTCHAs, vanishing messages, flashing content, short timeouts, scans instead of text and overlays that promise to fix everything.
- Glossary
Key terms explained: accessibility, WCAG, GOST R 52872-2019, contrast, alt text, focus, screen readers, captions and plain language.
- Questions
Answers to common questions about this reference, text and images, forms and video, and how to check your own site's accessibility without an expert.
Check your site in five steps
Tab through the page
Put the mouse aside and press the Tab key to move from the top of the page to the bottom. At every step you should be able to see which element is selected, and you should reach every link, button and field in a sensible order.
Zoom in to double size
Zoom the page in your browser to twice its normal size and scroll through it. Text shouldn't get cut off or overlap nearby blocks, and menus and buttons should stay in place and keep working.
Check the contrast
Compare the color of your main text with the background using any contrast checker. Level AA requires at least 4.5:1 for normal text and at least 3:1 for large text.
Look at the headings
Write down the page headings in order, like a table of contents. If that list makes it clear what the page is about and where everything is, the structure is fine. If there are no headings, or they were picked for their font size, it needs work.
Check the form field labels
Click the label of each field: a properly linked label moves the cursor into the field. Make sure labels stay visible the whole time instead of disappearing as soon as someone starts typing.
The short version
Do you build websites or run paid audits?
No. Wpget is a reference. We don't build websites, sell hosting, take orders or represent any agency. All you'll find here are explanations to help you check and fix your own site.
Is my website legally required to meet an accessibility standard?
That depends on who owns the site and what it's for, and we don't give legal opinions. If it matters to you, ask a lawyer. Whatever the answer, an accessible site is easier for every visitor to use.
Can I just add a “low vision version” and be done?
No. A separate button with larger text doesn't fix the main site: it won't add field labels, image descriptions or keyboard support. The page everyone sees is the one that needs to be accessible.
How much does it cost to make a site accessible?
Honestly, much of it takes attention rather than money. You can describe images, organize headings, label fields and raise contrast on your own. Major rework is usually needed only where accessibility was ignored for a long time.
About this project
This domain used to host an unrelated blog. Its content was not preserved and is not reproduced here. This reference has no connection with that blog; the name simply came with the domain.
We write for owners and editors of small websites who want everyone to be able to use their pages. You won't find specific software, site builders or companies here, just principles and checks that apply to any website.
Related reading
- Guides
Step-by-step guides to making text readable, organizing a page with clear headings and building a contact form that works for everyone. Plus the article catalogue.
- Tools
How to check a site yourself: browser zoom, the keyboard, high contrast mode, the built-in screen reader, color contrast checks and a markup validator.
- Comparisons
Conformance levels A, AA and AAA; alt text vs. captions vs. transcripts; subtitles vs. transcripts vs. sign language, laid out in comparison tables.
- Fixes
What to do when focus is invisible, text breaks on zoom, a button has no label, form errors make no sense or a video has no captions.
- Glossary
Key terms explained: accessibility, WCAG, GOST R 52872-2019, contrast, alt text, focus, screen readers, captions and plain language.
Sources
- W3C: WCAG 2.2 Recommendation
- GOST R 52872-2019 (Russian national standard)
- Wpget editorial materials
This information is stated in general terms as of the preparation date. Guidelines, browsers and reader habits change over time, so when in doubt, check the primary sources: the text of the WCAG guidelines and, for Russia, the current GOST R 52872-2019 standard.