Design
Accessible Design for Russian Business: Baseline Minimum or Full WCAG
Not every site needs full WCAG, but every commercial site has a low-cost baseline that makes no economic sense to skip.
In short
Not every commercial site in Russia needs full, expensive WCAG compliance, that is justified primarily for government, government-adjacent and socially significant services, where legal requirements are stricter. For an ordinary commercial site, there is a low-cost baseline, text contrast, keyboard accessibility, image alt text, visible focus states, that is worth building into any project by default regardless of industry, because the cost of that baseline at the design stage is close to zero, while the cost of skipping it is real lost users.
Why this is a question of tiers, not "needed or not"
Accessibility discussions often fall into one of two extremes: either "accessibility is not in this project’s budget" or "full WCAG level AA compliance across every criterion is needed." Both extremes are imprecise for most commercial sites: the real question is not binary but about which tier of accessibility investment is economically and legally justified for a specific type of business and its audience.
Three investment tiers
| Tier | What it covers | Who it fits |
|---|---|---|
| Baseline minimum | Contrast, alt text, keyboard accessibility, focus states | Any commercial site, by default |
| Extended tier | + screen-reader testing, semantic markup | A mass-market B2C service with a broad audience |
| Full WCAG (AA and above) | Full external audit, compliance with every criterion | Government, government-adjacent and socially significant services |
Why the baseline is nearly free at the design stage
The key economic argument for the baseline: nearly every item in it is an order of magnitude cheaper when built in at the design stage rather than retrofitted onto a finished site. Sufficient text contrast is a colour choice in the design system, not a separate task. Image alt text is a few minutes of extra work while laying out content, not a separate retroactive audit project on an existing site.
That exact same set of changes, added to an already-launched site with hundreds of pages, requires a retroactive audit and reworking each page individually, an order of magnitude more expensive and slower than building the same principles into the design system from the start.
When full WCAG is justified
Full, expensive-to-achieve WCAG compliance with an external audit is justified where legal requirements are stricter, government and government-adjacent services, socially significant platforms (education, healthcare, financial services for a broad audience), or where the product’s nature and audience make accessibility a direct business priority, not just a compliance question. For an ordinary commercial B2B site or online store, this investment tier is usually excessive relative to legal requirements and the actual audience composition.
Frequently asked questions
Does an ordinary commercial site need full WCAG?
Generally not, full, expensive compliance is justified for government, government-adjacent and socially significant services, where legal requirements are stricter. An ordinary commercial site is well served by a low-cost baseline built in at the design stage.
What does the accessibility baseline include?
Sufficient text contrast, keyboard-accessible controls, image alt text, and clear focus states on interactive elements. All of these are an order of magnitude cheaper when built into the design system from the start, rather than retrofitted afterward.
Why is accessibility cheaper at the design stage than retrofitted?
Because at the design stage it is a choice within decisions already being made, a colour in the design system or the markup structure, for example, not a separate task. On an already-launched site with hundreds of pages, the same changes require a separate retroactive audit and reworking each page individually, which is significantly more expensive and slower.
Who genuinely needs a full accessibility audit?
Government and government-adjacent services, socially significant platforms like education, healthcare and financial services for a broad audience, and products for which accessibility is a direct business priority, not just a formal compliance question.
Need a hand with this?
We do this work, not just write about it. Describe the task and we will scope it and send a staged estimate.
Related services
- UX/UI design for websites and appsWe design interfaces that survive contact with production: research, structure, UI kit and a clean handoff to the developers. Everything lives in Figma as components with real states and real breakpoints, not as a folder of flat mockups. The same process covers landing pages, corporate sites, e-commerce, web apps and mobile.
- Website audit: technical, SEO and UXBefore changing the design, raising the ad budget, or telling support the site "just feels slower," find out what is actually happening. An audit is one report that pulls technical health, SEO and usability into a single list: what is on fire, what matters, and what can wait.
Read next
- UX Research Without a Lab Budget: What Actually Produces ResultsMost teams do not need a research department, they need to stop guessing. Methods ranked by cost and payoff, the five-user rule and its important caveat, and how to turn findings into decisions without a sixty-page report nobody reads.
- Design Systems: When They Pay Off and When They Are an Expensive ToyMost teams asking for a design system need a component library and naming discipline instead. Where the line sits, how to calculate the payback before you start, and what actually belongs in a minimum viable version.
- Website Audit Checklist: What to Check Before a Redesign or Ad LaunchA complete self-audit checklist covering indexation, speed, markup, mobile usability and commercial ranking factors, with the tools to run each check and a way to prioritise what you find.