1. Our commitment
We aim to identify, prevent, and remove accessibility barriers in the public website, customer application, status pages, and support resources. Accessibility is considered during design, implementation, testing, and maintenance rather than treated as a one-time project.
2. Accessibility target
Our voluntary design and testing target is the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA where reasonably applicable. This target describes our direction; it is not a claim that every page, third-party experience, or historical component currently conforms in every respect.
3. Current approach
- Semantic headings, labels, landmarks, and status messages where practical.
- Keyboard-operable navigation, forms, dialogs, menus, and primary actions.
- Visible focus indicators and colour choices intended to maintain readable contrast.
- Responsive layouts that support mobile screens and browser zoom.
- Text alternatives for meaningful images and labels that do not rely on colour alone.
- Clear validation messages placed close to the field or action needing attention.
- Plain-language help and downloadable records where the product supports them.
4. Known limitations
Complex time-series charts and high-density monitoring logs can be difficult to interpret with some assistive technologies. We are continuing to improve text summaries, table alternatives, focus handling, and mobile presentation. Customer-uploaded logos, status-page descriptions, and external monitored content are controlled by the customer and may not meet the same standards.
If an accessibility barrier prevents you from completing an important task, contact us and identify the page, task, browser, assistive technology, and preferred response method if you are comfortable doing so.
5. Third-party services
Some flows are provided by third parties, including hosted identity and billing experiences. We choose established providers and consider accessibility during vendor review, but their interfaces and updates are not fully controlled by StackResolve. We will help identify an alternative path where reasonably possible.
6. Feedback and accessible-format requests
Send accessibility feedback or a request for an accessible copy to support@uptimebasics.com with the subject "Accessibility request." You may also write to StackResolve, 65 Leitch Avenue, North York, Ontario M3J 0E2, Canada.
We will acknowledge requests as soon as reasonably practicable and work with you on a suitable format or accommodation. We will not charge an additional fee for an accessible format.
7. Ongoing review
We review this page and our accessibility work at least annually and when significant customer-facing features change. Feedback is recorded and prioritized according to impact, urgency, and the availability of an effective workaround.