US-based RMM platform · Lancaster, Pennsylvania Support Mon–Fri, 8:00 AM – 8:00 PM ET

Accessibility Statement

We aim to meet WCAG 2.1 Level AA on this website. Where we fall short, we would rather know about it and fix it than claim conformance we have not verified.

1. Our commitment

IT professionals who use assistive technology should be able to evaluate and buy software without obstruction. We designed this website to work with keyboards, screen readers, magnification and high-contrast settings, and we treat accessibility defects as functional defects rather than cosmetic ones.

"Partially conformant" is an honest description: we have built to Level AA and tested the main paths, but we have not commissioned a formal third-party audit of every page and component. We publish the limitations we know about in section 3 instead of asserting full conformance.

2. What we have implemented

  • Semantic structure: landmark elements (header, nav, main, footer), one h1 per page, and headings in logical order without skipped levels.
  • Keyboard access: every interactive control is reachable and operable by keyboard, in a logical tab order, with no keyboard traps. A "Skip to main content" link is the first focusable element on every page.
  • Visible focus: a high-contrast focus indicator is never suppressed.
  • Navigation: the mobile menu button exposes aria-expanded state, can be closed with the Escape key, and dropdown menus open on hover and on keyboard focus. Current-page links carry aria-current.
  • Text alternatives: informative images have descriptive alt text; decorative elements and icons are hidden from assistive technology.
  • Contrast: body text and interactive controls are designed to meet or exceed a 4.5:1 contrast ratio, and large text at least 3:1.
  • Forms: every field has a persistent visible label programmatically associated with it, required fields are indicated in text as well as by attribute, hints are provided as visible text rather than placeholder-only, and validation messages are conveyed as text, not by color alone.
  • Resizing and reflow: layouts reflow to a 320 pixel viewport without horizontal scrolling and remain usable at 200% zoom; no text is embedded in images.
  • Motion: no autoplaying audio or video, no flashing content, and animation is disabled for users who set prefers-reduced-motion.
  • No interference: no pop-ups or interstitials cover the content, and the storage notice can be dismissed by keyboard without blocking navigation.
  • Progressive enhancement: every page's content is present in the HTML and readable with JavaScript disabled; scripting only adds the mobile menu, the notice dismissal and the pricing estimator.
  • Tables: data tables use th with scope and a caption describing content and any assumptions.

3. Known limitations

  • Formal audit: no independent third-party accessibility audit has been completed for this website. We rely on internal testing, which is less rigorous.
  • Wide data tables: some comparison and pricing tables scroll horizontally within their container on narrow screens. The scroll container is keyboard reachable, but a table with many columns remains harder to consume on a small screen than we would like.
  • Pricing estimator: results update as values change; screen reader users are notified through the result text, but we have not yet implemented a live region with configurable politeness. This is on our list.
  • Photographic contrast: photographs used for illustration have no text overlay, so they carry no informational contrast requirement, but they are not described beyond their alt text.
  • Platform console: the authenticated ITSupport RMM console is a separate application with its own accessibility characteristics. If you have specific requirements — screen reader compatibility, keyboard-only operation of remote sessions, contrast settings — contact us before purchasing and we will demonstrate the relevant workflows honestly, including where they need improvement.

4. Compatibility

This website is designed to work with current versions of Chrome, Edge, Firefox and Safari on Windows, macOS, iOS and Android, in combination with assistive technologies including NVDA, JAWS, VoiceOver and TalkBack, and with operating system zoom, high-contrast and reduced-motion settings. It does not depend on browser plug-ins.

5. Reporting a barrier

If any part of this website or our product is difficult or impossible for you to use, tell us:

Email: Info@itsupport-rmm.com with the subject line "Accessibility"
Phone: +1 717 823 6666, Monday–Friday, 8:00 AM – 8:00 PM ET
Mail: ITSupport RMM, 401 W Lemon St, Lancaster, PA 17603, United States

Please include the page URL, what you were trying to do, and the browser and assistive technology you were using. We acknowledge reports within 2 business days, aim to fix critical barriers within 10 business days, and will tell you the plan and timeline for anything that takes longer.

6. Alternative ways to get what you need

If a page or process is not usable for you, we will provide the information or complete the transaction another way at no extra cost: by phone, by email, in a plain-text document, or in a large-print format. Requesting pricing, a quote, a demo, a trial or support by phone or email is always available as an alternative to any form on this site — and the contact form itself is intentionally simple, opening your own email client rather than depending on a scripted multi-step flow.

7. Assessment approach

We assess accessibility through internal review using keyboard-only navigation, screen reader spot checks, automated checks in browser developer tools, contrast measurement of the design system tokens, and zoom and reflow testing at 320 pixel width and 200% zoom. New pages and components are reviewed before publication. We intend to commission an independent audit and will update this statement with the outcome when we do.