★ ACCESSIBILITY STATEMENT ★
MUMIO · ACCESSIBILITY
WHAT WE DO — AND WHAT WE DO NOT CLAIM

A DARK BLUE PAGE

SHOULD STILL BE READABLE.

This site is built to look like a 1982 advertisement. That is a decision about style, and it must not become a decision about who gets to read it.

We aim at WCAG 2.2 level AA. We are not going to tell you we have reached it, because nobody outside this workshop has ever tested the site and a claim of conformance made without testing is worth nothing at all.

So this page does something more useful instead: it says what has actually been done, what we already know is wrong, and where to send the thing you found. That last part matters most — you will find problems we cannot, because we are not using the site the way you are.

IN ONE SENTENCE

We aim at WCAG 2.2 AA; the site has not been audited; several things listed below fall short; tell us what breaks and we will fix it.

Report anything to contact@mumio.dev — a person reads it, and it is the same person who can change the page.

WHAT IS ALREADY IN PLACE

01 · CONTRAST

MEASURED, NOT GUESSED

The palette was checked rather than eyeballed. Body text sits at roughly 14:1 against its background; the pale grey used for small captions is about 9:1; the weakest text colour we use — the red — is about 5.4:1.

AA asks 4.5:1 for body text and 3:1 for large text. Every text combination on these pages clears both.

02 · STRUCTURE

REAL HEADINGS

Headings are heading elements, in order, one h1 to a page, used because the text underneath is a section — never because a line needed to look big.

That is what lets a screen-reader user jump through a page instead of listening to it end to end.

03 · KEYBOARD

NOTHING TO GET STUCK IN

These pages are made of text, headings, lists and links. There are no custom widgets, no modal dialogues and no carousels, so there is nothing exotic for the Tab key to fall into.

Links keep a visible focus outline. If you can see where you are, you can use the page without a mouse.

04 · IMAGES

TEXT ALTERNATIVES

Photographs in the shop do not yet carry text alternatives. We know it, we are not pleased about it, and we are working through the library adding them. Until that is finished, a screen reader will announce many of our product images only by their file name, which is no use to anybody.

Nothing that matters is communicated by a picture alone.

05 · TARGETS & TEXT

BIG ENOUGH TO HIT

Buttons are at least 44 pixels tall — comfortably above the minimum WCAG 2.2 asks for, and about the size a shaking hand or a thumb on a train actually needs.

Body text is set at a normal reading size with generous line spacing, and it is real text: zoom it, restyle it, or read it in your own font.

06 · CALM

NOTHING MOVES

No animation, no autoplay, no flashing, no pop-up that arrives five seconds after you do. The retro styling stops at colour and typography.

Below 660 pixels the layout folds into a single column, so a phone gets one column of text rather than a page you have to drag sideways.

WHERE WE KNOW WE FALL SHORT

Listed because a statement that mentions no faults is not a statement, it is an advertisement.
  • Nobody independent has tested this site. There has been no audit, no assistive-technology testing session and no user testing with disabled people. Everything above is our own assessment of our own work.
  • The shop and checkout are not entirely ours. Product pages, the basket and the payment steps are generated by WooCommerce and the theme. We can style them; we cannot rebuild their markup, and we have not checked them page by page.
  • Older pages use styled containers where a heading element belongs. The newer pages — this one, Shipping, Returns and the site map — use proper headings. The rest are being converted, and until that is done the heading outline of the site is uneven.
  • Decorative rules and borders are low contrast on purpose. The pale purple lines between sections measure about 2:1 and would fail if they carried meaning. They do not: remove every one of them and nothing is lost but tidiness.
  • Some text alternatives are still only part numbers. A few older photographs are labelled with the board they show rather than described — accurate, but thin. They are being rewritten.
  • The display typeface is heavy. Bungee is used for short headings only, never for running text, but it is a decorative face and some readers will find it hard. Every heading is also a plain text string, so it can be restyled or read aloud without loss.
  • Technical drawings and screen photographs have limits. A caption can say that a demo runs at full speed on real hardware; it cannot let you hear the AY chip or see the border effect. Where that matters, write and ask — we will describe it properly.

FOUND
SOMETHING
BROKEN?

Tell us. Not because a regulation says you may, but because you have information we do not have and cannot get on our own. A page that fails you is a bug, and we treat it as one.

HOW TO REPORT IT

E-mail contact@mumio.dev, with the word ACCESSIBILITY somewhere in the subject line so it does not get filed behind the order enquiries.

Four things help us reproduce it, and none of them is compulsory — send what you have:

  • the address of the page;
  • what you were trying to do;
  • what happened instead;
  • what you were using — browser, screen reader, magnifier, keyboard only, phone.

IF THE SITE ITSELF IS THE OBSTACLE

You should not have to fight a web page in order to report a web page. Telephone L-TEK on +48 575 080 805, Monday to Friday, 07:00–16:00 CET, and say what you need.

If a page stops you from ordering, ask and we will take the order by e-mail or over the telephone instead. Prices and terms are exactly the same; nothing about buying that way costs you more.

This statement covers the pages published at mumio.dev. It is a statement of intent and of current practice; it is not a declaration of conformance with WCAG 2.2, and it has no legal force of its own.