Accessibility statement
We want everyone to be able to use evenentry.com, however they browse. That includes people with disabilities. We build the site to a published standard and check every page against it.
- In effect from
- Last reviewed
- 8 minutes to read
- Earlier versions
The short version
- We build evenentry.com to the Web Content Accessibility Guidelines (WCAG) 2.2, at Level AA.
- On November 6, 2026, we checked all 59 pages with an automated checker.
- Our own software went through all 59 pages by keyboard and with a screen reader. The checks marked nothing as a problem on any page. A person signed off every check by November 6, 2026.
- If something gets in your way, write to hello@evenentry.com.
Text that is easy to read
We build the site to WCAG 2.2, at Level AA. For normal text, WCAG asks for a contrast of at least 4.5 to 1 against its background.
We choose our text colors to reach at least 5 to 1 on every background they sit on. We do this in the light and the dark color scheme. That leaves room to spare, so text stays clear to read. This is our aim and what we check against, not a claim about every page.
What works for you today
- Press Tab once on any page to reach a "Skip to content" link. It takes you past the menus to the content.
- Every page has one main heading, and the rest run in order, so you can skim by them to the part you want.
- If your screen reader can jump by landmark, you can go straight to the menus, the main content or the footer.
- Use a small phone, 320 pixels wide, or zoom in: any page reads without scrolling sideways, even with extra space between letters, words and lines.
- Set text to twice its size, and every page fits a laptop, a tablet or a phone with no scrolling sideways.
- Turn scripts off, and every page still shows its content. Each menu in the header still opens, as a plain list under its name.
- Press Enter on a menu in the header, or on the Colors button, to open it. Press Escape to close it, and focus goes back to the button you used.
- The site follows your device's light or dark setting by itself. You can also choose Light, Dark or Match my device from Colors in the header.
- With your device's high-contrast setting on, paler text becomes as strong as the main text, and faint lines get clearer.
- Ask your device for less motion, and every animation and transition stops at once.
- Our short silent films play by themselves when you scroll to them, and stop when you scroll away. Press Pause under one, and it stays paused until you press Play.
- You will not meet ads or an accessibility overlay on our pages. We count visits with two tools, and neither puts anything on the page for you to see, hear or reach with the keyboard.
- You choose whether our site uses Google Analytics, with the "Privacy choices" button at the foot of every page. In the European Economic Area, the UK and Switzerland, we use it only once you say yes in a small box of ours. That box leaves your focus where it was.
- We serve our fonts from our own site, so reading a page sends nothing to a font service.
What does not work yet, and what to do instead
-
The call and contact forms
With scripts off, the call page's calendar and both forms do not work, and each form shows our email address instead. The forms' spam check needs scripts turned on.
We have not yet tested the spam check with a keyboard and a screen reader. If a form does not work for you, write to hello@evenentry.com with the same details it asks for. We will test the spam check with a keyboard and a screen reader, and say here what we find.
-
The example walkthroughs
Each walkthrough has a half-minute video of our keyboard check, with a computer voice and captions. Just under the video, open "Read what the video says" to read every word the voice speaks. The link "Read every step of the check, written out" lists each place the keyboard reached, in order. None of the walkthroughs shows the check with a screen reader.
How we checked the site
Our last check
- Date checked
- November 6, 2026
- Pages checked
- 59
- Screen widths
- 1,280 and 375 pixels wide
- Color schemes
- Light and dark
- The checker's rules, at each width, in both color schemes
-
Passed
- No scrolling sideways at 320 pixels wide
-
Passed
- No scrolling sideways at 320 pixels wide, with extra text spacing
-
Passed
- Text at twice its size, at laptop widths
-
Passed
- Text at twice its size, at tablet and phone widths
-
Passed
- Each page shows its content with scripts off
-
Passed
- The skip link, by keyboard
-
Passed
- The header's menus on the homepage, by keyboard
-
Passed
- The Colors button on the homepage, by keyboard
-
Passed
- Pausing the films, by keyboard
-
Passed
On November 6, 2026, we checked all 59 pages of the site with an automated checker. We used its rules for WCAG Levels A and AA, including its rule for the size of tap and click targets. We also used its rules for good practice.
First, we checked each page at 1,280 and 375 pixels wide, in both color schemes. Then we checked them at 320 pixels wide, with and without extra text spacing, and with scripts turned off. We also set text to twice its size at laptop, tablet and phone widths. With the keyboard, we used the skip link on every page, and the header's menus and the Colors button on the homepage.
On each page with a short film, we scrolled to it at 1,280 pixels wide, and it played with no sound. We pressed its Pause button with the keyboard, and it stopped and stayed stopped. We asked for less motion, and no film played by itself. We turned scripts off, and none played by itself then either.
We did all of this in one browser, and we have not tried another.
Our last check covered every page on the site. Nothing failed the checker's rules on any page. That held at both widths and in both color schemes.
On a small phone, 320 pixels wide, no page scrolled sideways, even with extra space between letters, words and lines. With text at twice its size, every page fit at each width we checked. With scripts turned off, every page still showed its content. The checker also marked three things for a person to review.
- The Colors button on every page, and the menu button on a phone. The menu each one opens only appears when you open it, so the checker could not find it.
- Contrast on some pages. The checker could not tell the color behind a piece of text, so it could not measure that contrast.
- Captions for short videos on six pages, including our About page and plan pages. The checker could not tell whether these videos need captions. They have no sound, so there is nothing to caption. Words beside each one say what it shows.
Next, our own software went through all 59 pages by keyboard. On each page, it pressed Tab through every place you can reach and checked that you can see where you are. It did this at 1,280 pixels wide in the light and dark color schemes, and at 375 pixels in the light one. At 1,280 pixels, it opened each menu in the header with Enter, closed it with Escape and checked that you land back on its button.
Then, at 1,280 pixels wide, our software ran a screen reader on every page. It read each page and jumped through it by headings, landmarks, form fields and pictures.
A person signed off every check. These checks marked nothing as a problem on any page.
Before we keep a change to anything our pages share, such as a button, menu or form field, we test it on its own page. We test it at three widths and in both color schemes. We also test it with the keyboard, with scripts off, and with the same checker rules we use on the stores we check.
A page goes live only if its headings are in order. From other sites, it may load the two tools that count our visits and the forms' spam check, and nothing else.
Automated checks find some problems and miss others. Here is what we have not done yet. At 375 pixels, our keyboard check reached the Menu button in the header but did not open its menu. Neither check measured contrast. Both checks used only one browser. The screen-reader check used one screen reader, at 1,280 pixels only.
Tell us if something gets in your way
Write to hello@evenentry.com about anything that got in your way. It helps to know the page, what you were trying to do and, if you are willing, what you use to browse. We reply by email.
How this statement is made and dated
Today we write this statement by hand, from the record of our last check. Each time we change it, we date the change in the list below and keep the earlier version at its own address. For the keyboard and screen-reader checks, we take the dates and the number of pages from our own software's record. The automated checker's figures come from a script that is part of the site.
Changes and earlier versions
-
In effect from (this version)
First version.