1. Our commitment
MediaMatic aims to make its website, forms and client-support tools perceivable, operable, understandable and robust. Accessible structure, readable contrast, keyboard-friendly interactions, descriptive links, useful labels, alternative text and responsive layouts are part of our design work.
2. What we are working towards
We use WCAG 2.2 Level AA as an improvement benchmark where reasonably practicable. We have not completed a formal conformance audit, so this statement is not a claim that every page, document or third-party component conforms to WCAG 2.2 Level AA.
The European Accessibility Act covers specified consumer products and services. Whether a particular requirement applies depends on the service, the operator and any applicable exemption. Our practical objective is to remove avoidable barriers regardless of formal scope.
3. Current approach
- semantic headings and landmarks are used to make pages easier to navigate;
- forms are intended to have visible labels, instructions and understandable errors;
- interactive elements should be keyboard accessible and display a visible focus state;
- text and controls are designed to maintain useful contrast and resize responsively; and
- essential support routes are available by email or telephone when an online route is difficult to use.
4. Known limitations
Some older articles, uploaded documents, third-party widgets, administrative interfaces or images may not yet have ideal heading structure, captions, transcripts, alternative text or keyboard behaviour. Client portal and form components partly depend on WordPress plugins whose accessibility we do not control in every detail.
We prioritise issues that block contact, consultation requests, support tickets, secure client access or access to essential service information.
5. Adjusting your experience
You can use browser zoom, text resizing, high-contrast settings, keyboard navigation and supported assistive technologies. If a page or document is inaccessible, ask us for the information in a reasonable alternative format.
6. Feedback and assistance
Tell us the page, feature or document concerned, what you were trying to do, and the browser or assistive technology used where relevant. Contact us through the contact page, submit a support ticket, or email [email protected]. We aim to acknowledge accessibility reports within two business days where practical.
7. Review
We review this statement when significant website, form or portal features change. Relevant reference points include WCAG 2.2, the European Accessibility Act and Malta’s disability-rights framework.
