Accessibility Statement

OUR TARGET STANDARD

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA published by the World Wide Web Consortium (W3C). These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including:

• Visual impairments (blindness, low vision, colour blindness)
• Hearing impairments
• Motor and physical disabilities
• Cognitive and learning disabilities
• Speech disabilities

TECHNICAL APPROACH

The yokly.gives website is built with accessibility integrated at the engineering level:

• Semantic HTML — correct use of landmark elements (header, main, nav, footer) and heading hierarchy (h1 → h2 → h3).
• Keyboard navigation — all interactive elements are reachable and operable via keyboard alone. Tab order follows visual reading order.
• Skip-to-content link — a visible skip link appears on keyboard focus, allowing users to bypass repeated navigation.
• ARIA attributes — ARIA labels, roles, and states are applied where HTML semantics alone are insufficient (menus, modals, accordions).
• Focus management — modals and drawers trap focus while open and restore it on close.
• Colour contrast — text meets WCAG AA contrast ratios: 4.5:1 for body text, 3:1 for large text and UI components.
• Alternative text — all informative images have descriptive alt attributes. Decorative images use alt="" with aria-hidden="true".
• Reduced motion — animations respect the prefers-reduced-motion media query and are disabled for users who prefer it.
• Responsive design — the Site reflows correctly at up to 400% zoom and is functional on mobile devices.
• Form labelling — all form inputs have associated <label> elements or aria-label attributes.

CONFORMANCE STATUS

We believe yokly.gives is partially conformantwith WCAG 2.1 Level AA. "Partially conformant" means that some content does not fully conform to the accessibility standard.

Known limitations

We are aware of the following areas currently under active improvement:

• Blog post hero images — some blog posts reference legacy image assets that may lack descriptive alt text. We are migrating these as part of an ongoing content audit.
• Third-party embeds — GoHighLevel booking modals and embedded calendar interfaces are provided by a third-party vendor. Their accessibility conformance is governed by GoHighLevel and may not fully meet our own standard.
• Video content — webinar recordings and video content on the Resources hub do not currently include closed captions or transcripts. We are working to address this.

We are actively addressing these gaps. If you encounter an issue not listed here, please report it (see below) and we will prioritise a fix.

BROWSERS AND ASSISTIVE TECHNOLOGIES

yokly.gives is tested for compatibility with the following combinations:

• Chrome + NVDA (Windows)
• Safari + VoiceOver (macOS)
• Safari + VoiceOver (iOS)
• Chrome + TalkBack (Android)
• Firefox + NVDA (Windows)

We test keyboard navigation in all modern browsers including Chrome, Firefox, Safari, and Edge on desktop and mobile viewports.

REPORTING AN ACCESSIBILITY ISSUE

We welcome feedback on the accessibility of yokly.gives. If you encounter a barrier that prevents you from accessing any part of our Site, please tell us:

• The page URL where the issue occurs
• A description of the barrier and what you were trying to do
• The assistive technology or browser you are using (if applicable)

We aim to acknowledge accessibility reports within 2 business days and resolve confirmed issues within 30 days, prioritised by severity.

FORMAL COMPLAINTS

If you are not satisfied with our response to your accessibility feedback, you may contact the relevant regulatory authority in your country. In the United States, the Department of Justice enforces Title III of the Americans with Disabilities Act (ADA) with respect to websites open to the public.

For EU residents, your national data protection or equality body may also be a point of contact for digital accessibility complaints.

OUR ONGOING COMMITMENT

Accessibility is integrated into our engineering workflow. New components and page builds include:

• Linting with eslint-plugin-jsx-a11y at the error level (not warn)
• Keyboard navigation tests on every interactive element before deployment
• Colour contrast verification against WCAG AA for all new colour combinations
• Manual screen reader checks for complex interactive flows (modals, menus, accordions)

This statement was last reviewed on May 20, 2026. We will review and update it at least annually, or whenever a significant change is made to the Site.

CONTACT US

For general accessibility enquiries: