Accessibility statement

We want everyone to be able to use Semonto. This statement explains the accessibility standards we aim to meet, what we have already done, what we are improving, and how you can report a problem.

Scope

This statement covers the marketing website at semonto.com, the Semonto dashboard (Supervisor) web app, and the Semonto mobile applications for iOS and Android.

Standards we aim to meet

We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We are also working to meet the requirements of the European Accessibility Act (EAA). For our iOS and Android apps, we follow the same WCAG 2.2 AA principles and the platform accessibility guidelines (Apple Human Interface Guidelines and Android Accessibility Guidelines).

Conformance status

We are actively working toward WCAG 2.2 Level AA. Based on our most recent self‑assessment, the Semonto marketing website and dashboard are partially conformant: some parts do not yet fully conform, but we have an ongoing remediation plan (see Known limitations).

What we do

  • Use semantic HTML, proper headings and landmarks (header, nav, main, footer).
  • Provide text alternatives for non-text content (alt text for images/icons).
  • Maintain sufficient color contrast and readable font sizes.
  • Ensure full keyboard accessibility and visible focus styles.
  • Label form inputs and controls with associated labels or aria attributes.
  • Support screen reader users with clear structure, link names and aria-labels where needed.
  • Test changes with automated checks (e.g., Lighthouse) and human reviews.

Known limitations

Some legacy content (e.g., older images in blog posts or third‑party embeds) may not fully meet our current standards yet. We are addressing these items during ongoing content updates. If you encounter an issue, please let us know so we can prioritize it.

  • Contrast in a few image/overlay sections is under review; we are adjusting tokens and overlays where needed.
  • Keyboard focus order review across all templates is planned; initial fixes for navigation, search, and tiles are in place.
  • Form error announcements are being improved using aria‑live regions and more explicit associations.
  • Heading hierarchy is being audited across long‑form content (blog, guides).

How we test

We use a combination of automated and manual testing:

  • Automated: Google Lighthouse accessibility audits on key pages, monitored periodically via Semonto’s Lighthouse Monitoring. We receive alerts when scores degrade so issues can be triaged quickly.
  • Automated: Broken link and mixed‑content checks via Semonto to avoid inaccessible error states.
  • Manual: Keyboard‑only navigation reviews and inspection of landmarks, labels, and focus styles.
  • Manual: Spot checks with assistive technologies (VoiceOver on macOS/iOS; TalkBack on Android).

Technical specifications

Accessibility of Semonto relies on the following technologies to work with your browser and assistive technologies: HTML, WAI‑ARIA, CSS, and JavaScript.

Compatibility

Semonto is designed to work with the latest stable versions of major browsers (Safari, Chrome, Firefox, Edge) on desktop and mobile. Older browsers that do not support modern web standards may provide a degraded experience.

Feedback and contact

If you have trouble accessing any part of our website, dashboard, or apps, or if you have suggestions to improve accessibility, please contact us via our contact page. You can also email us at info@codingmammoth.com. We aim to respond within 5 business days.

Enforcement procedure

We review reported issues, provide workarounds when available, and schedule fixes in our development backlog according to impact and effort.

Preparation of this statement

This statement was prepared on 26 August 2025, last reviewed on 26 August 2025, and is reviewed at least annually or whenever we make significant changes to our website, dashboard, or apps.

Related documents

Get in touch!