Loading SUBLAKELoading SUBLAKEAccessibility is a baseline at SUBLAKE — not a checkbox at the end of a project. Every page, every component, every flow is designed and built so that customers with disabilities can use them on equal footing.
Last reviewed: April 27, 2026
Anyone running a service business should be able to operate SUBLAKE — regardless of the device, browser, or assistive technology they rely on every day.
We treat accessibility as engineering work. It lives in our component library, our review checklists, and our shipped tests — not in a quarterly remediation sprint after the fact.
We design and build to meet the Web Content Accessibility Guidelines 2.1 at conformance Level AA. New features are reviewed against the same bar before they ship.
Our platform is built to align with U.S. Section 508 standards for federal-context use, including keyboard operability, perceivable content, and consistent navigation.
For our customers in the EU, our product surfaces are built with EN 301 549 in mind — the European accessibility standard for ICT products and services.
Every interactive element on the marketing site and in the product is reachable, operable, and visibly focused with a keyboard alone — Tab, Shift+Tab, Enter, and Escape behave the way you expect.
Semantic HTML, descriptive alt text, ARIA labels on icon-only buttons, and live regions for status updates. Tested against modern VoiceOver, NVDA, and JAWS workflows.
Body text meets a 4.5:1 contrast minimum; large text meets 3:1. Functional color (errors, success, warnings) is always paired with an icon or label so meaning is never carried by color alone.
Animations respect the system-level prefers-reduced-motion setting. Complex transitions are disabled or simplified for visitors who request reduced motion.
Text reflows cleanly up to 200% zoom without loss of content or function. We use relative units throughout and avoid layout breakage at large text sizes.
Every form input has a visible, persistent label. Errors are announced to screen readers, anchored to the offending field, and explain how to fix the problem.
We are honest about the gaps that remain. Some product surfaces — particularly rich data tables, custom drag-and-drop interactions, and embedded third-party content — are still being polished against the WCAG 2.1 AA bar. We track each gap publicly in our internal accessibility log and address them by severity.
User-generated content (customer reviews and inbound messages displayed inside the dashboard) reflects the source material we receive — we cannot guarantee its accessibility, but we never strip alt text or accessible markup from it.
Email contact@sublake.com with the page URL, the device and assistive technology you were using, and a brief description of the barrier. We acknowledge accessibility reports within two business days and treat them at the same priority as security reports.