Accessibility Statement

The standard we build against

We aim for the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. Conformance is partial: the parts of the site we wrote are built and reviewed against that standard, and the parts supplied by other companies are listed further down because we cannot audit or repair them.

What this site does

Checked against the code rather than assumed:

• A skip link at the top of every page jumps straight to the main content, past the header and its menus.
• Every page has one first-level heading, and its sections run in order under it.
• Every control can be reached and operated with a keyboard alone, including the menus and the showroom tour switcher, which follows the standard tab pattern with arrow keys.
• Focus is visible on everything focusable, by a site-wide rule rather than one screen at a time.
• The photo viewer and the mobile menu are real dialogs: the page behind them cannot be reached with the Tab key, Escape closes them, and focus returns to whatever opened them.
• The reviews carousel advances on its own, so it carries a pause control, it does not start at all when the operating system has been asked for reduced motion, and opening a quote to read the whole of it stops the timer.
• Colour pairs are verified against the WCAG contrast thresholds rather than judged by eye, and the ratios are recorded beside the palette in the code.
• An image cannot be added to the blog without a text alternative. It is required in the language the image is uploaded in; if the other language is left empty, that version reads the first one's text.
• Photographs behind text are darkened by a measured amount, so the text over them holds its contrast whatever the photograph turns out to be.
• Animation respects the operating system setting: with "reduce motion" on, the site stops animating.
• Pages reflow into a single column on a narrow screen and are checked at the 320-pixel width the guidelines name, so nothing has to be scrolled sideways to be read, and the browser can enlarge the text without the page cutting it off.
• Controls that are nothing but an icon — the menu buttons, the marks in the footer, the arrows in the photo viewer — are at least 44 by 44 pixels, so they can be hit without a steady hand.
• The whole site exists in English and Spanish, with the same structure in both.
• Every page declares which of the two languages it is in, so a screen reader reads it in the right voice, and the switch between them sits in the header of every page and lands on the same page in the other language.

How we checked this

This is a self-assessment. The people who build the site checked it themselves, three ways: by reading the code, for the things one rule guarantees everywhere at once — the focus outline, the reduced-motion block, the contrast of the palette, the text alternative the system will not let an editor skip; by running an automated audit against WCAG 2.2 AA on 11 September 2026, across ten pages at phone width and at desktop width, with axe-core and a contrast check that resolves every colour the way a browser paints it; and by working the pages with a keyboard alone, which is how the focus order, the focus ring and the absence of keyboard traps were confirmed.

That audit is written down, method and all, so anyone can repeat it and get the same numbers. It found two real faults, both fixed the same day: a carousel that announced no slide count, and two table headers that named nothing. It also confirmed that no informative text on the site falls below the contrast the standard asks for.

No outside firm has audited this site, and nobody who depends on a screen reader every day has been asked to try it yet. So where this page says something is true, it is true because we checked it here. That is a weaker guarantee than an audit by someone else, and we would rather say so plainly than let the word "conformance" imply one we have not had.

Parts supplied by other companies

Two things on this site are embedded from other companies. Their interfaces are theirs, we cannot audit or fix them, and each one has a way around it:

• The virtual showroom tours, listed on our virtual showrooms page, are hosted by Panoee. They are navigated by dragging inside the frame, which is not usable by keyboard alone, and what they show has no text alternative. Every tour also opens in its own tab, and anything you want to know about a unit you see in one, we will describe and price over the phone or by email.
• The map on the contact and virtual showrooms pages is a Google Maps embed, and it only loads when you press “Show the map”. The address, the phones and the opening hours are written as text beside it, and “Get directions” is an ordinary link, so nothing on those pages depends on the map loading or being operable.

What we know is not right yet

Some photographs have not been taken yet. Where one is missing the page draws a neutral placeholder rather than a broken image, which keeps the layout stable but means the slot carries no picture and no description.

The site does not follow the dark theme setting of your operating system. It is drawn on a light ground whichever way that setting is turned, and for a reader who needs a dark one that is a real cost.

Blog articles are written in our content system and can change after they are published. The editor offers no top-level heading, so an article cannot add a second main title, but whether its headings run in order and how its links are worded are held to by review rather than by the software, so an article added later can drift from what this page describes. Tell us when it does.

The tours described above are the largest gap, and it is not one we can close ourselves.

Tell us if something does not work

If any part of this site stops you doing what you came to do, we want to hear about it, and we would rather hear about it than have you give up. Email us at it@mvcwindows.com.

If it is something we can fix, we will tell you when it is fixed; if it is one of the third-party parts above, we will say so rather than leave you waiting, and get you what you needed another way.

It helps if you can say which page you were on, what you were trying to do, and what you were using — a browser, a phone, a screen reader. We answer in English or Spanish, whichever you write in.

Whatever you were trying to do on the site, you can also do by talking to us: measurements, prices, product questions and the paperwork are all handled by phone, WhatsApp or email.

About this statement

This statement applies to the whole of mvcwindows.com. It was first published on 7 September 2026 and last updated on 15 September 2026. It was last checked against the site on 11 September 2026, the date of the audit described above. It is reviewed when the site changes, and corrected whenever a claim on it stops being true.