Frequently asked questions

A small, independent editorial team. We have no ties to agencies, hosting providers or software developers, and no connection with the former site on this domain.

No, we don't run audits or take requests. This reference explains how to check a site yourself, and the tools for that are covered in a separate section.

Software names and features change quickly, and any mention could easily look like promotion. We describe which features to look for and leave the choice to you.

The WCAG guidelines developed by the W3C, the Russian standard GOST R 52872-2019 and our own editorial experience. We don't quote requirements word for word; it's better to read the primary source.

At level AA, at least 4.5:1 for normal text and at least 3:1 for large text. If in doubt, make the text darker: it almost never hurts the design.

No. Descriptions are needed for images that convey information. Decorative elements get empty alt text so screen readers skip them.

Better not. Some people can't tell certain colors apart, and in a system high contrast mode, color may disappear entirely. Pair color with a word, a labeled icon or an underline.

It means short sentences, familiar words and the main point at the start of each paragraph. Everyone understands such text faster, from a person with reading difficulties to a busy visitor on a phone.

No. Placeholder text disappears as soon as someone starts typing and isn't always read by screen readers. Every field needs a permanent, visible label.

As a first draft, yes. But they must be proofread: speech recognition gets names, terms and numbers wrong, and a single error can change the meaning of a sentence.

Tab through the page, zoom it to double size, check the contrast, write down the headings and listen to the page with the built-in screen reader. That alone will catch most obvious barriers.

After every noticeable design change and whenever you add a new type of page. It helps to keep a short checklist and run through it before publishing.