Uptimeify

Accessibility: Status and Measures

How accessible Uptimeify is: self-assessment against WCAG 2.1 AA, the measures in place, the gaps we know about and how to reach us.

How accessible Uptimeify is, what we do about it and where we are not there yet.

Scope

This page covers the website at https://uptimeify.io including all language versions, the Uptimeify web application behind the login, the free tools and the documentation at docs.uptimeify.io. The documentation runs on a codebase of its own and has not yet been measured the way the rest has. It stays in scope because it is publicly linked and you may end up there, but we would rather say that than let it look checked.

It does not cover content our customers create themselves: their own logos, color schemes, copy and white-label status pages served from a custom domain. More on that under "Status pages and white-label output".

Why this page is voluntary

The European Accessibility Act, Directive (EU) 2019/882, has been enforceable since 28 June 2025. Germany transposed it as the Barrierefreiheitsstärkungsgesetz (BFSG). As we read it, Uptimeify falls outside the scope for two independent reasons:

We do not sell to consumers. The Directive covers services provided to consumers. Uptimeify is offered exclusively to businesses within the meaning of section 14 of the German Civil Code, to legal entities under public law and to public-law special funds (section 1.2 of our Terms). Consumers are not part of our customer base.

We are a microenterprise. Zaskoku & Haupt GbR employs fewer than ten people and has an annual turnover or balance sheet total of no more than 2 million euro, which makes it a microenterprise under Commission Recommendation 2003/361/EC. Article 4(5) of the Directive exempts microenterprises providing services from the accessibility requirements, and section 3(3) BFSG mirrors that exemption in German law.

So none of what follows is something we are required to publish. We publish it anyway. If you run a monitoring dashboard eight hours a day, you should be able to run it. And if you are an agency working for a public sector client, you need dependable statements about every tool in the chain.

A note for public sector buyers

Public sector bodies are covered by Directive (EU) 2016/2102 and its national transpositions, and have to publish an accessibility statement for their own digital services. If you deploy Uptimeify, for instance for a publicly reachable status page, our implementation status feeds into your own assessment. That is exactly what the information on this page is for. If you need more detail for a tender or for your own statement, ask us directly and we will supply the specifics for the module in question.

Conformance status

This is a self-assessment. No external audit, no certification, no third party report. We measure against the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA and the harmonised European standard EN 301 549.

On that basis, we consider the public pages of uptimeify.io largely conformant with WCAG 2.1 Level AA. For the dashboard and the data-heavy views, that holds with limits: parts of them have not been tested systematically with assistive technology. The gaps we know about are listed below rather than written around.

What we do

  • Semantic HTML with a consistent heading structure and one H1 per page.
  • Alternative text for informative images and mockups, decorative graphics marked up as such.
  • Color contrast: for text and controls we work against the Level AA contrast ratios. The public website is built in one dark color scheme; the application behind the login follows your system setting and is measured in both.
  • Keyboard operability for navigation, forms and interactive elements, with a visible focus indicator.
  • Scalable layout: zoom is not locked, layouts are responsive.
  • Reduced motion: animations respect the prefers-reduced-motion system setting, charts included. Loading spinners keep turning, more slowly — a frozen one would say the app had hung.
  • Numbers, not just curves: in the application behind the login, uptime figures, response times and incident histories are available as numbers or tables, not only as charts. On public status pages the uptime bar carries a text alternative that screen readers read out day by day.
  • Language markup via the lang attribute per language version, so screen readers pronounce content correctly.
  • Accessibility in review: new interfaces are checked for keyboard operability, contrast and heading structure before release.

Known limitations

Honest beats complete. These are the gaps we know about and are working on:

  • Interactive charts. Uptime histories, response time charts and heatmaps are built visually first. Screen reader operation is possible but has not been tested systematically. The underlying values are also available in the table views and through the API.
  • Maps and node views. The overview of our European checking locations carries its information spatially. An equivalent text alternative is in progress.
  • PDF reports. The generated SLA and monthly reports have not been checked against PDF/UA. The same data is available in the dashboard and through the API in a more accessible form.
  • Complex tool output. Some free tools return results as structured code blocks, such as JSON, DNS records or certificate chains. That output is machine readable but not consistently prepared for speech output.
  • Older documentation pages. Individual pages on docs.uptimeify.io date back to earlier revisions and do not yet meet our current heading and contrast rules everywhere.

Status pages and white-label output

Uptimeify generates status pages, reports and client portals that our customers ship under their own brand. Responsibility is shared.

On us: templates, markup, interaction logic, keyboard handling and the default color palette. We build that foundation to the same standard as the rest of the platform.

On the customer: their own colors, logos, domains and copy. A brand red picked in-house can fall below a contrast ratio our default palette meets. We can check and we can warn, but we do not get to decide what a customer's brand looks like.

If you run a status page on your own domain and you are unsure whether your customisations hold up, get in touch. We will look at it with you.

Third party content

Third party content embedded in our pages is outside our direct control. That includes embedded status widgets, links to external documentation and links to our integration partners' services. Accessibility there is the respective provider's responsibility.

How this page was prepared

These statements were prepared in August 2026 on the basis of an internal self-assessment. We review them at least once a year and additionally whenever the website or the web application changes substantially.

Feedback and contact

Run into a barrier, or need content in a more accessible format? Tell us. The more specific, the faster we can act: which page, which assistive technology, what did not work.

Zaskoku & Haupt GbR Lange Str. 54 - 56 48683 Ahaus Germany

Phone: +49 2568 900 9000 Email: hello@uptimeify.io

We aim to respond promptly.

If our answer does not satisfy you

Enforcement of the BFSG in Germany sits with the joint market surveillance authority of the federal states. Even though Uptimeify falls outside that law as we read it, we name the authority here: anyone who thinks our reading is wrong, or that our response to their feedback fell short, should know where to go.

Marktüberwachungsstelle der Länder für die Barrierefreiheit von Produkten und Dienstleistungen, Anstalt öffentlichen Rechts (MLBF AöR) Carl-Miller-Straße 6 39112 Magdeburg Germany

Phone: +49 391 289 230 23 Email: kontakt@mlbf-barrierefrei.de Web: https://www.mlbf-barrierefrei.de

More legal information

Last updated: 6 August 2026