Accessibility Statement

1. Our Commitment

Vediwood Studio is committed to making this website usable by everyone, including people with disabilities. Accessibility is not retrofitted here. It is built into every page from the start, as a standard part of how we work.

Roughly one in five people has a disability of some kind. Many more have a temporary one — a broken wrist, an eye infection, a phone in bright sunlight. A website that excludes them is a website that is not working.

The same standard applies to the sites we build for clients. If you want to know how we approach a build, see our services.

2. Standards We Follow

We aim to conform to WCAG 2.1 Level AA (opens in a new tab) — the Web Content Accessibility Guidelines published by the W3C. It is the internationally recognised standard for web accessibility, and the benchmark most accessibility law points at.

Those laws include the Americans with Disabilities Act (opens in a new tab) in the United States, the UK Equality Act 2010 (opens in a new tab), and the European Accessibility Act (opens in a new tab), which applies from June 2025.

Level AA is the middle of three levels. Level A is the minimum and leaves real barriers in place. Level AAA is stricter than most websites can meet across every page. AA is the level regulators expect, and the level we build to.

The W3C Web Accessibility Initiative (opens in a new tab) publishes a plain-language introduction if you want to read more about what the guidelines cover.

3. What WCAG Actually Means

WCAG is built on four principles. Content must be perceivable, operable, understandable, and robust. They are usually shortened to POUR.

Perceivable means you can take the information in. Images carry text alternatives, video carries captions, and colour is never the only way something is explained — because roughly one man in twelve cannot reliably tell red from green.

Operable means you can use the site with whatever you have. Everything works by keyboard alone, nothing traps your focus, and nothing moves or disappears before you have had time to read it.

Understandable means the site behaves predictably. Language is declared so screen readers pronounce it correctly, navigation stays in the same place, and when a form rejects your input it tells you what to fix in words.

Robust means the code is clean enough that assistive technology can interpret it — valid HTML, correct roles, and states that update when the page updates.

4. How We Have Built This Website

Every page includes a skip link so keyboard users can bypass the navigation, a logical heading hierarchy from h1 down through h2 and h3, and landmark regions — header, main, nav, footer, aside — so screen reader users can jump straight to the part they want.

Everything interactive works by keyboard, with a visible focus indicator that never disappears. Interactive elements carry ARIA labels where the visible text alone is not enough. Decorative elements are marked aria-hidden so they are not announced as noise.

Form inputs have properly associated labels, and error messages are announced as live alerts rather than appearing silently. Modal dialogs trap focus while open and return it to the button that opened them when closed.

Colour contrast meets or exceeds the 4.5:1 ratio WCAG requires for normal text. The site is dark by design, and we chose the palette to hold that ratio rather than picking colours first and checking later.

We respect the reduced motion setting in your operating system. If you have asked your device to limit animation, this site honours that and drops its entrance animations.

5. Assistive Technology Compatibility

This website is designed to work with NVDA (opens in a new tab) on Chrome or Firefox on Windows, JAWS (opens in a new tab) on Chrome or Edge on Windows, VoiceOver (opens in a new tab) on Safari on macOS and iOS, and TalkBack (opens in a new tab) on Chrome on Android.

We test both keyboard-only navigation and screen reader reading mode, because they are not the same thing and a site can pass one while failing the other.

Screen readers, browsers, and operating systems all update on their own schedules, and a combination that worked last month can break. If you hit a problem with a specific pairing, tell us using the link at the end of this page and name the combination — it makes the fix far faster.

6. Using This Site Your Way

You do not need any special software to adjust this site. Your browser and your operating system already carry most of what you need.

You can zoom to 200% with Ctrl and plus on Windows, or Command and plus on a Mac, and the layout will reflow rather than break. Text-only zoom works too.

If animation is uncomfortable, turn on Reduce Motion in your system settings — Accessibility on macOS and iOS, Ease of Access on Windows, Accessibility on Android. This site checks that setting and respects it.

For keyboard navigation, Tab moves forward, Shift and Tab move back, Enter activates a link or button, and Space scrolls the page. The first Tab press on any page reveals a skip link that jumps you past the navigation.

If you want a deeper introduction to what your own devices can do, WebAIM (opens in a new tab) publishes clear, practical guides written for people rather than developers.

7. How We Test

Automated tools catch roughly a third of accessibility problems. We run them, but we do not stop there, because the remaining two thirds are the ones that actually block people.

Beyond the automated pass, we walk each page by keyboard alone, listen to it through a screen reader, check contrast values against the WCAG threshold rather than by eye, and view every page at 390 pixels wide to confirm nothing is lost on a small screen.

Accessibility is checked before a page is published, not audited afterwards. A statement written after launch usually documents problems. Ours is meant to prevent them.

8. Known Limitations

We are not aware of any significant accessibility barrier on this website at the time of this statement.

Some third-party embeds are outside our direct control and may not fully conform to WCAG 2.1 AA. The Cal.com booking widget is the main one. We cannot rewrite another company's code, but we can make sure you are never forced through it.

If you encounter a problem with embedded content, tell us and we will give you another way to reach the same information or service — by email, by phone, or in whatever format works for you. Booking a call should never depend on a widget behaving.

9. Help Us Improve

If you have any difficulty using this website, or you need content in a different format, we want to hear about it. Every report makes the site better for the next person.

The most useful reports name the page, describe what you were trying to do, and mention the browser and any assistive technology you were using. Even a rough description helps — do not worry about getting the technical details right.

We aim to respond within 5 business days. If your need is time-sensitive, say so and we will prioritise it. You can also reach us through our contact page, and our Privacy Policy explains what happens to anything you send us.