1.Our commitment
Aheadnode intends its website and products to be usable by everyone, including people who rely on keyboards, screen readers, magnification, or reduced motion. Accessibility requirements are part of our engineering checks, not an afterthought — several are enforced by automated tests that fail our build when violated.
2.Conformance status
We aim for the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. This statement reflects a self-assessment (automated checks plus manual keyboard walkthroughs), not a third-party audit. We are not aware of unresolved Level AA violations on this site; if you find one, we want to know about it — see section 5.
3.What is implemented on this site
- Semantic structure: landmark regions, a skip-to-content link on every application page, and a logical heading hierarchy.
- Images and icons: meaningful images carry real alternative text; decorative icons are hidden from assistive technology — enforced by an automated test.
- Color and contrast: the design system's text colors are chosen to meet WCAG AA contrast ratios on both light and dark surfaces, and color is never the only carrier of meaning.
- Keyboard operability: all interactive elements are reachable and operable by keyboard, including the document gallery, which implements the WAI-ARIA tabs pattern (roving tabindex, Arrow, Home, and End keys). Focus is always visible.
- Forms: every field has a programmatically associated label; required states are announced; submission results are exposed through live regions.
- Motion: all animation is disabled for visitors with
prefers-reduced-motionenabled. - Resizing: layouts remain usable at 200% zoom and on small viewports; text is real text, not images.
4.Known limitations
- The two marketing pages (home and product) currently require JavaScript to render their content; this legal page and its siblings do not. Pre-rendering the marketing pages to static HTML is on our roadmap.
- This statement is based on self-assessment. A formal third-party evaluation (and a full VPAT/ACR document for procurement) is planned as the company grows; enterprise buyers who need one sooner should contact us.
5.Feedback and contact
If you encounter an accessibility barrier on this site or in Smart Runbooks for Jira, email support@aheadnode.com. Reports go directly to the person who can fix them, and we aim to respond within two business days.
6.The product
Smart Runbooks for Jira renders inside Atlassian products using Atlassian's UI Kit component system, inheriting the accessibility semantics of Atlassian's design system, and its documents are produced as standard Confluence pages — as accessible as any page in your Confluence. Product-specific accessibility issues can be reported through the same channel above or via our support portal.