Accessibility Statement

We want Marklet to be usable by as many people as possible, regardless of disability, assistive technology, or browsing environment. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA.

This means we try to make the platform:

• Operable using a keyboard alone, without a mouse.
• Compatible with screen readers and other assistive technologies.
• Readable with sufficient colour contrast in both light and dark mode.
• Usable at up to 200% browser zoom without loss of functionality.
• Free of content that flashes or flickers in ways known to cause seizures.

Marklet is a growing product and accessibility improvements are ongoing. We are currently working towards WCAG 2.1 Level AA compliance. We have tested the following across major browsers and screen readers:

• Keyboard navigation through the main application layout and navigation menu.
• Focus management when dialogs and modals open and close.
• ARIA labels on interactive icon-only buttons (such as filter and sort controls).
• Colour contrast ratios for primary text and interactive elements.

We are aware of the following areas that do not yet fully meet WCAG 2.1 AA and are actively working to address them:

• Some data tables (service charges, issue lists) may not provide sufficient row/column header associations for screen reader users. We are adding explicit scope attributes.
• Rich text areas in issue comments do not yet provide a full accessible toolbar for screen reader users.
• Some chart visualisations (analytics charts) do not currently have text alternatives. We plan to add accessible data tables alongside charts.
• PDF invoices and service charge documents uploaded by users are not processed for accessibility - their accessibility is the responsibility of the uploader.

Marklet is built with the following accessibility practices:

• Semantic HTML5 elements (headings, landmarks, lists, buttons, links).
• ARIA attributes where native HTML semantics are insufficient.
• Focus-visible outlines on all interactive elements.
• Colour contrast ratios tested against WCAG 1.4.3 (minimum 4.5:1 for text).
• No content relies on colour alone to convey meaning.
• Motion is kept minimal; no auto-playing media or animations that cannot be paused.

Marklet is designed to work with:

• Modern versions of Chrome, Firefox, Safari, and Edge on desktop and mobile.
• Screen readers including NVDA and JAWS on Windows, and VoiceOver on macOS and iOS.
• Keyboard-only navigation on all major operating systems.

Internet Explorer is not supported.

If you experience any accessibility barriers or have suggestions for improvement, we want to hear from you. Please contact us at privacy@marklet.io with a description of the issue and, if possible, the page or feature affected.

We aim to acknowledge accessibility feedback within 5 working days and to resolve issues as promptly as possible.

This statement is provided in accordance with the Equality Act 2010. We are committed to not discriminating against people with disabilities in the provision of our services.

If you are not satisfied with our response to an accessibility complaint, you may contact the Equality and Human Rights Commission (EHRC).

This statement was last reviewed on 5 March 2026. We review and update it at least annually, or whenever significant changes are made to the platform.