Accessibility Statement

Last updated: 13 November 2026

We want anyone to be able to order, book and collect loyalty rewards through LoyalMT, whatever device or assistive technology they use. This page says what standard we work to, where we currently fall short, and how to tell us when something does not work for you.

1. Our commitment

Accessibility is not a feature we bolt on at the end. The people using LoyalMT are the general public — everybody who walks into a café, books a table, or wants a haircut. A significant proportion of them use a screen reader, need large text, cannot use a mouse, are colour blind, or are standing in bright sunlight on a phone with one hand full of shopping. If the ordering page does not work for them, they do not file a bug report. They give up, and the business loses the sale.

So we treat accessibility as part of whether the product works at all, and we would rather know about a barrier than not know.

2. The standard we work to

We aim to meet Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, which is the standard referenced by EN 301 549 (the European harmonised standard for ICT accessibility) and by accessibility law across the EU. Where WCAG 2.2 adds criteria that are straightforward to meet, we apply those too.

We claim partial conformance, not full conformance

LoyalMT is partially conformant with WCAG 2.1 level AA. “Partially conformant” means most of the product meets the standard, but some parts do not yet. The known gaps are listed in section 5 below.

We have deliberately not written “LoyalMT is fully accessible” or “WCAG 2.1 AA compliant”. We have not commissioned an independent audit against all fifty level A and AA success criteria, and until we have, a full conformance claim would be a statement we could not stand behind. It would also be unfair on any business relying on this page to meet its own accessibility obligations.

3. What the law requires of us, honestly

The European Accessibility Act (Directive (EU) 2019/882), transposed in Malta, applies accessibility requirements to e-commerce services from 28 June 2025. The ordering, booking, appointment and ticketing flows in LoyalMT are e-commerce services within the meaning of that Act.

However, Article 4(5) of the Act exempts microenterprises that provide services — businesses employing fewer than ten people with an annual turnover or annual balance sheet total not exceeding €2 million. LoyalMT is operated by a sole trader and currently falls within that exemption, so the Act’s binding requirements do not presently apply to us.

We are telling you that rather than hiding it, for two reasons. First, because claiming to be bound by a law that does not bind us would be dishonest. Second, and more importantly, the exemption is ours, not yours:

If you are a business using LoyalMT, our exemption is not your exemption

Your own accessibility obligations depend on your size and sector, not ours. If your business employs ten or more people, or exceeds the €2 million threshold, the European Accessibility Act applies to the e-commerce service you offer your customers — and that service includes the LoyalMT ordering or booking page you point them at.

Our partial-conformance position does not discharge your duty, and this page is not a conformance certificate you can rely on. If you are subject to the Act, you should assess the pages your customers actually use, and tell us about anything that would put you in breach. We will treat that as a priority, because a gap that puts you in breach is a gap we want closed.

If LoyalMT grows past the microenterprise thresholds, the exemption falls away and we become directly subject to the Act. We would rather be close to the standard already than have to retrofit it under a deadline, which is why we work to WCAG 2.1 AA now despite not being required to.

4. What we have done

These measures are in place across the customer-facing pages (menus, ordering, bookings, appointments, tickets, loyalty cards) and, to a somewhat lesser extent, the business dashboard.

Structure and navigation

  • Semantic HTML throughout — real headings, lists, buttons and form labels rather than styled div elements, so a screen reader can announce what things are and a user can jump between landmarks.
  • A logical heading order on each page, so the document outline makes sense when read without any visual styling.
  • Keyboard operability: every interactive control can be reached and activated with the keyboard alone, and focus is visible rather than suppressed.
  • Dialogs and overlays trap focus while open and return focus to the control that opened them when dismissed.
  • Page titles that describe the specific page, not just the site name.

Text and colour

  • Body text meets the 4.5:1 contrast ratio against its background, and large text meets 3:1.
  • Text resizes to 200% without loss of content or function, and the layout reflows to a 320 CSS pixel width without requiring horizontal scrolling.
  • Colour is never the only way information is conveyed — status is also carried by text or an icon, so a red-green colour deficiency does not hide the meaning.
  • No text is rendered as an image of text, so it scales and can be read by assistive technology.

Forms and errors

  • Every input has a programmatically associated label. Placeholder text is never used as a substitute for a label, because it disappears as soon as you type.
  • Validation errors are described in text, identify which field is wrong, and say what to do about it — rather than just turning a border red.
  • Errors are announced to assistive technology rather than appearing only visually.
  • Required fields are marked in text as well as visually.

Motion, touch and media

  • Animation respects the operating system’s prefers-reduced-motion setting. If you have asked your device to reduce motion, transitions are minimised.
  • Nothing flashes more than three times a second, so the product does not present a seizure risk.
  • Touch targets on customer-facing pages are sized for a thumb rather than a cursor, which matters because almost all customer use is on a phone.
  • No feature depends on a complex gesture, device motion or shaking; everything can be done with a single tap or a keyboard.
  • Images that convey meaning carry alternative text. Decorative images are marked so that a screen reader skips them rather than reading out a filename.

Not relying on the senses

  • There is no audio-only or video-only content in the product that carries information, so captions and audio description are not currently required. If we add video, we will caption it.
  • Time limits: where a basket or booking hold expires, we do not silently discard your work without warning.

5. Known gaps

This is the part of an accessibility statement that is usually missing, and it is the part that is actually useful. These are barriers we know about and have not yet fixed. We would rather publish them than let you discover them.

AreaThe problemStatus
Business dashboard — data tablesSome reporting tables are wide and rely on horizontal scrolling. Row and column relationships are not always announced clearly by a screen reader, which makes a large report hard to read non-visually.Being worked on. Customer-facing pages were prioritised first, because that is where the general public is.
Charts and analyticsReporting charts are rendered visually and the underlying numbers are not always available as an accessible table or text alternative next to them.Planned. The data is exportable in the meantime, which is a workaround rather than a fix.
Drag-and-drop orderingReordering menu items, categories and form fields in the dashboard is done by dragging. A keyboard-only alternative is not available everywhere it should be.Planned. Where no keyboard path exists, contact support and we will make the change for you.
Third-party checkoutPayment pages are served by Stripe and Viva.com and are outside our control. Their accessibility is governed by their own statements, not this one.Outside our control. See section 6.
Embedded mapsThe map used for venue locations comes from Google Maps and is not fully keyboard operable. Every venue address is also given as plain text so the map is never the only way to get the information.Mitigated rather than fixed — a text alternative always accompanies the map.
AI-imported menusWhen a business imports a menu from a photograph, the resulting item descriptions are only as good as what the business reviews afterwards. Poorly structured or missing descriptions are a content problem we cannot correct automatically.Guidance given to businesses. We cannot guarantee content we did not write.
PDF documentsAny PDF a business uploads (a menu, a price list) is accessible only to the extent that the business made it so. We do not remediate uploaded PDFs.Businesses are responsible for their own uploads.
Independent auditNo third-party accessibility audit has been carried out. Our assessment is a self-assessment, with automated testing and manual keyboard and screen-reader checks.Not yet commissioned. This is why we claim partial and not full conformance.

6. Parts of the experience we do not control

Some of what a customer sees when using LoyalMT is not ours, and we cannot make an accessibility claim about it:

  • Payment pages hosted by Stripe or Viva.com, which run on their infrastructure under their own accessibility statements.
  • Apple Wallet and Google Wallet, including how a loyalty pass is displayed, read aloud or surfaced on a lock screen. That is the platform’s interface, governed by Apple’s and Google’s own accessibility work — both of which are considerably more mature than ours.
  • Google Maps embeds used to show where a venue is.
  • Content written or uploaded by businesses — menu descriptions, images and their alternative text, uploaded documents, custom form questions. We provide the fields and the guidance; what goes in them is the business’s choice. Section 7 covers what we ask of them.
  • Your browser, operating system and assistive technology, and how they interact with standards-based HTML.

Where something we do not control creates a barrier, tell us anyway. We can often provide an alternative route, and we would rather raise it with the provider than leave you stuck.

7. If you are a business using LoyalMT

Most accessibility problems your customers will actually hit are in content, not code. These are the things only you can do:

  • Write real item descriptions. “Chef’s special” tells a screen-reader user nothing. Say what it is.
  • Add alternative text to images you upload, describing what the dish or room actually looks like. If an image is purely decorative, leave the alt text empty rather than repeating the item name.
  • Do not put essential information only in an image. A photographed menu, a price list as a JPEG, or opening hours inside a graphic are invisible to assistive technology. Put the text in the text fields.
  • Keep allergen and dietary information in the structured fields rather than buried in a description or a footnote. It is the information most likely to be needed urgently and least forgiving of being hard to find.
  • Check your own colour choices. If you customise your page colours, a pale brand colour on white can drop below the 4.5:1 contrast ratio and make your own menu unreadable.
  • Offer a non-digital route. A phone number a customer can call, and staff who will take an order at the counter, is the most effective accessibility measure in hospitality and costs nothing. Do not make the QR code the only way to order.

The QR-code-only trap

A table with nothing on it but a QR code excludes anyone without a smartphone, anyone whose battery is dead, anyone who cannot read small print on a screen, and anyone who finds the process unfamiliar or stressful. It is also, for a business within scope of the European Accessibility Act, a plausible compliance problem.

Keep a printed menu available and let people order from a person. LoyalMT is meant to be the faster option, not the only option.

8. How we test

We assess accessibility using a combination of:

  • Automated checks during development, which catch contrast failures, missing labels and missing alternative text — roughly a third of WCAG issues, and no more than that.
  • Manual keyboard testing: working through each customer-facing flow using only the keyboard, from landing on a menu to completing an order.
  • Screen-reader testing with VoiceOver on iOS and macOS, since iOS is where most customer traffic is.
  • Testing at 200% text size and at a 320 CSS pixel viewport width.
  • Testing with reduced-motion enabled.

This is a self-assessment. It has not been verified by an independent accessibility specialist, and automated tooling cannot tell whether an alternative text is meaningful — only whether it exists. Treat our assessment accordingly.

9. Tell us about a barrier

If you cannot do something in LoyalMT because of an accessibility barrier, please tell us. You do not need to know what the technical problem is, or use any particular terminology — describing what you were trying to do and what happened is enough.

  • Email hello@loyalmt.com with “Accessibility” in the subject line.
  • If it helps, tell us which page, which device and browser, and which assistive technology you were using — but none of that is required.

What we will do

  • Acknowledge within 2 working days.
  • Respond substantively within 10 working days, telling you either that it is fixed, when it will be fixed, or that we cannot fix it — and if we cannot, what alternative route is available to you in the meantime.
  • Provide the information or service another way if a fix is going to take time. If you cannot complete a booking, we will take the details and arrange it with the business directly.

A barrier that blocks someone from completing an order or a booking entirely is treated as a high-priority fault, not a feature request.

10. If we do not resolve it

If you are not satisfied with how we have responded, you can escalate:

  • In Malta, the Commission for the Rights of Persons with Disability (CRPD) handles disability discrimination complaints and can be contacted at crpd.org.mt.
  • Where the complaint concerns a business’s own goods or services rather than our software, the MCCAA Office for Consumer Affairs may also be relevant.
  • Elsewhere in the EU, your national accessibility enforcement authority or equality body can take a complaint about a service provided to you.

We would much rather you came to us first and gave us the chance to fix it, but you are not obliged to.

11. Status of this statement

  • Prepared on: 13 November 2026, on the basis of a self-assessment carried out by LoyalMT.
  • Method: self-assessment, using automated testing plus manual keyboard and screen-reader checks as described in section 8. Not independently audited.
  • Conformance claim: partially conformant with WCAG 2.1 level AA, with the exceptions listed in section 5.
  • Review cycle: reviewed at least annually, and whenever a significant new customer-facing feature ships.

12. Contact

Accessibility questions, barrier reports and requests for information in an alternative format:

  • Email: hello@loyalmt.com
  • LoyalMT, a trading name of Roden Muscat (sole trader), Malta
  • Address supplied on request

If you need any document in this legal set in a different format — larger text, plain text, or read aloud — ask and we will provide it.

Revision history

  • 13 November 2026 — First published. Previously there was no accessibility statement at all. This version states the standard we work to (WCAG 2.1 AA), claims only partial conformance, lists eight known gaps rather than concealing them, explains that our microenterprise exemption under the European Accessibility Act does not transfer to the businesses using us, and sets response times for barrier reports.