Accessibility statement
Accessibility
We build this site to WCAG 2.2 level AA, the international guidelines for accessible websites. This is a target we work towards, and no one has certified the site against it. So this page keeps two lists apart: what already works and can be measured, and what we know is still missing.
- Target
- WCAG 2.2 AA
- Applies to
- webway.ee, all three languages
- Status
- Checked by us. No external audit.
- Report a problem
- info@webway.ee
Live check
What your browser is set to right now
Below are four settings from your browser. This page reads them using only CSS (media queries). If you change one in your system settings and reload the page, the answer here changes too. Nothing is stored and nothing is sent anywhere: your browser gives these answers only to the page's stylesheet.
Reduced motion
You have asked for less motionYou have not asked for less motion
The line above stays still because you asked for less motion.The line above moves only while you scroll. It never starts moving by itself.
Every animation on this site checks this setting. Animations made with CSS sit inside a reduced-motion rule. The few that are drawn on a canvas with JavaScript ask the browser the same question before they start, and if you asked for less motion, they do not start at all. In both cases movement stops at the finished picture: nothing is left half-drawn, and nothing waits for code that will never run.
Forced colours
Your system is replacing this page's coloursYour system lets the page use its own colours
High-contrast modes remove shadows and background fills, and the thin lines of this site's design are drawn with exactly those. Separate rules for this mode put back what gets lost: the keyboard focus marker is an outline instead of a shadow, decorative fills are dropped, and anything that showed meaning through colour gets a border instead.
Higher contrast
You have asked for more contrastYou have not asked for more contrast
The page reads this setting, but the site does nothing with it yet. Both colour themes, light and dark, are built to meet AA, but there is no third, higher-contrast version. We did not choose this on purpose. It is a gap, and it is listed again below.
JavaScript
JavaScript is off in this browserJavaScript is running
Every word of every page is in the HTML our server sends, so the text is there before any script runs. With JavaScript off you lose the chat assistant, the light and dark theme switch and, on narrow screens, the menu button. The footer at the bottom of the page has the same navigation as plain links, and they work without scripts.
If a row does not match your settings, your browser may not be able to answer that question. In that case the page assumes the setting is off, and that is also how the page is shown to you.
Built in
What already works
Clear page structure
Every page has one main content area (the main landmark), one top-level heading (h1), and headings that go down level by level without skipping one. A screen reader can list a page's headings like a table of contents, and on this site that list is complete and in order.
Works with a keyboard
Everything you can use is a real button or a real link, and the Tab key moves through them in reading order. The mobile menu, the services panel and the chat assistant window keep keyboard focus inside while they are open, close with the Escape key, and return focus to the button that opened them.
Visible keyboard focus
The frame that shows where you are on the page when you use a keyboard (the focus) is drawn as an outline set slightly apart from the element, never as a shadow. High-contrast modes remove shadows, and the people who use those modes need to see the focus most.
Buttons big enough to tap
Buttons, header links and the two icon buttons are at least 44 pixels tall. WCAG 2.2 asks for at least 24. We use 44 because people often read this site on a phone, holding it in one hand, with a client in the room.
Each page states its language
Each page tells the browser which language it is written in. The language switcher marks each of its three links with that link's own language code (lang and hreflang). So a screen reader switches to the right voice there instead of reading Estonian with English pronunciation.
Nothing appears only on scroll
Effects that bring content in as you scroll only move text that is already on the page. Turn animation off, turn scripts off or open the page source, and the text is complete every time. Nothing on this site needs a script to appear.
Videos are decoration only
The only videos on this site are clips of client websites shown in a browser frame. Each one is muted, hidden from screen readers and other assistive technology, skipped by the Tab key, and shows nothing the text next to it does not already say. If you ask for less motion, each video shows a still frame.
Clear forms
Every field has a proper label and an autocomplete value, so your browser can fill it in for you. Required fields are marked as required both on screen and in the code, so a screen reader says so too. The form's reply is announced through a status region, so screen readers read it out instead of it only appearing on screen.
Contrast planned into the colours
The site has two line colours on purpose: a thin, light line for the edges of cards, and a darker one for the edges of anything you can click or type into. The edge of such a control has to reach a contrast of 3:1; a decorative edge does not have to. The table below checks the whole colour palette against these rules.
Measured
Contrast table
Each row is a real colour pair from the site's stylesheet, a colour and its background, with the contrast ratio it reaches in the light and the dark theme. The samples are drawn in the theme you are using right now, so you can compare each number with what you see on screen. Switch the theme in the header to see the samples for the other column.
| Sample | What it is used for | Light | Dark |
|---|---|---|---|
| --ink / --ground | Headings and body textneeds 4.5:1 | 18.3 | 18.1 |
| --ink-2 / --ground | Paragraphs and supporting textneeds 4.5:1 | 9.0 | 7.6 |
| --ink-3 / --ground | Labels, captions, small interface textneeds 4.5:1 | 5.2 | 6.0 |
| --line-control / --ground | Edges of anything you click or type intoneeds 3:1 | 3.1 | 3.3 |
| --btn-a-ink / --btn-a-bg | Text on the main buttonneeds 4.5:1 | 5.1 | 17.9 |
| --platform / --ground | Platform accent colourneeds 4.5:1 | 5.0 | 7.0 |
| --academy / --ground | Academy accent colourneeds 4.5:1 | 5.4 | 10.2 |
| --studio / --ground | Studio accent colourneeds 4.5:1 | 5.2 | 7.8 |
Known gaps
What is still missing
These are the problems we know about. We list them here instead of leaving them out, and each one is something to fix.
No “skip to content” link
The header has several links before the main content starts, and keyboard users have to go past them on every page. A “skip to content” link is first on our list of fixes.
No button to pause motion yet
The header design includes a button that stops motion across the whole site, but it has not been added to the site yet. Until it is, the only way to stop animation is the reduced-motion setting on your device, and that setting stops all of it.
On narrow screens, the menu needs JavaScript
On screens narrower than 900 pixels, the navigation sits behind a menu button, and that button needs JavaScript. With JavaScript off on a phone, the same links are in the footer at the bottom of the page as plain HTML. That works, but you have to scroll all the way down to reach them.
The chat assistant needs JavaScript
The assistant that answers questions on the site does not work without JavaScript. The email address and phone number at the bottom of the page reach the same people.
The higher-contrast setting is not used yet
Your browser can tell the site that you want more contrast, but the site does nothing with that yet. Both themes are built to meet AA on their own; neither has a higher-contrast version so far.
The heading font has no Cyrillic letters
Russian headings use your system's own sans-serif font, because our heading font only has Latin letters. The Russian pages read correctly, but their headings look a little different from those on the English and Estonian pages.
No independent check yet
There has been no external audit and no testing with people who use assistive technology every day. Everything on this page is our own check of our own work, so please read it with that in mind.
Method
How we checked this
- We calculated the contrast ratios in the table from the colour codes in the stylesheet, for both themes. We did not measure them from screenshots.
- We went through every animation one by one and found what stops it: the reduced-motion rule in the stylesheet or, for the few animations drawn on a canvas, the same check in JavaScript. We did not just assume it from how the site behaves.
- We read the pages exactly as the server delivers them, with JavaScript off, to confirm that the text is there before any script runs.
- What we have not done: an independent audit, a test by someone who uses a screen reader every day, or a formal statement of conformance. This page does not claim any of the three.
Something not working?
Write to us. For us, a page you cannot use is as serious a fault as a page that will not load, and we handle it the same way. It helps if you tell us:
- The page address.
- What you were trying to do when it stopped working.
- Your browser, operating system and any assistive software, with version numbers if you know them.
- Whether it happens every time or only sometimes.
We reply in English, Estonian and Russian. We do not promise a deadline, because nobody here has committed to one. The aim is to reply and tell you what we found. If email does not suit you, call the phone number at the bottom of the page; it reaches the same people.