Accessibility Statement for yonihavana.com
Effective date: 9.26.2025
Version: 1.0
Site owner: Yoni Havana (“we,” “us,” “our”)
Domain covered: https://yonihavana.com (including subpages, blog posts, forms, downloadable documents, and embedded media hosted under this domain)
Our Commitment
We’re committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability. We actively work to ensure our digital content is usable by people with disabilities and inclusive for everyone.
Standards We Aim to Meet
We strive to conform to the following standards and laws to the greatest extent feasible:
WCAG 2.2 Level AA (W3C Web Content Accessibility Guidelines)
Section 508 of the U.S. Rehabilitation Act (as applicable)
Title II & Title III of the Americans with Disabilities Act (ADA)
EN 301 549 (EU accessibility standard) — as a reference where relevant
Note: We use WCAG 2.2 Level AA as our primary target because it is widely recognized as the benchmark for accessible web content.
Conformance Status
Partially conformant with WCAG 2.2 Level AA.
This means many key parts of the site meet Level AA, while certain areas are still being improved. Accessibility is an ongoing effort as we publish new content and update features.
Scope of This Statement
This statement applies to all web content we control at yonihavana.com. Some third-party integrations (e.g., payment processors, embedded videos, social feeds, scheduling widgets) are outside our sole control. We select vendors that claim accessibility conformance where possible and provide accessible alternatives when needed.
What We’re Doing
We follow a continuous improvement process that includes:
Design & content standards: Semantic HTML, proper heading order, sufficient color contrast, keyboard operability, visible focus, descriptive link text, alt text for meaningful images, and captions/transcripts for media where feasible.
Authoring practices: ARIA used carefully and only when necessary; components tested for name, role, and value.
Forms: Programmatically associated labels, clear instructions, helpful error messages, and minimal reliance on color alone.
Documents & downloads: New PDFs are created with accessibility in mind (tagged structure, text alternatives). Where a legacy file is not accessible, we offer an accessible alternative on request.
Ongoing testing: Periodic automated checks plus manual reviews with keyboard-only navigation and common assistive technologies (e.g., VoiceOver, NVDA/JAWS).
Current Known Limitations & Fix Roadmap
We’re actively working on the items below. If you encounter an issue we haven’t listed, please tell us (see Feedback & Contact).
Landmarks & structure
Ensure each page has one top-level banner and that content is fully contained within landmarks (header, main, footer, complementary).
Provide unique and descriptive labels for repeated regions (e.g., multiple navs).
Planned fix: audit and standardize templates; addaria-label/aria-labelledbyonly where helpful.
Headings & page titles
Ensure a single, descriptive H1 per page and logical, descending heading order.
Planned fix: content pass across key pages; lock in heading patterns within theme builder.
Link purpose & visual distinction
Guarantee link text is descriptive in context and distinguishable beyond color alone (e.g., underline on hover/focus).
Planned fix: style updates; content review to replace “Read more”/“Learn more” with specific link text.
Color contrast & non-text contrast
Meet or exceed 4.5:1 for body text and 3:1 for large text/icons/controls.
Planned fix: refine palette tokens; update button and text-on-image styles.
Keyboard navigation & focus
Ensure all interactive elements are reachable/operable via keyboard; avoid keyboard traps; provide visible focus outlines that aren’t obscured.
Planned fix: component testing and adjustments to dialogs, menus, carousels, and skip links.
Forms & errors
Provide explicit labels, helpful error identification/suggestions, and avoid relying solely on color.
Planned fix: standardize form patterns and validation messaging; addaria-livestatus where appropriate.
Media alternatives
Provide captions for prerecorded videos and transcripts for audio when feasible; avoid auto-play with sound.
Planned fix: add captions/transcripts for new media; provide on-request alternatives for legacy media.
Target cadence: We review priority pages quarterly and aim to address reported blockers as quickly as possible (see response times below).
Technical Specifications & Compatibility
This website relies on technologies that work with current browsers and assistive tools, including:
HTML5, WAI-ARIA 1.2, CSS, JavaScript
Supported browsers: current versions of Chrome, Safari, Firefox, Edge
Supported input methods: keyboard, mouse, touch
Layout supports zoom/reflow up to 200% without loss of content or functionality (where feasible)
Some older browsers or extensions that modify default behavior may affect accessibility.
Measures We Take
Accessibility awareness for designers, editors, and developers
Component/library choices that favor accessible patterns
Periodic automated scanning plus manual testing of key user journeys (navigation, forms, checkout, contact)
Third-Party Content & Integrations
We may embed or link to third-party platforms (e.g., payment, video, booking tools). While we don’t control their code, we:
Select vendors that publish accessibility information when possible
Provide contact options for accessible alternatives
Monitor for regressions and raise issues with vendors as needed
Feedback & Contact
Your feedback helps us improve. If you experience a barrier on yonihavana.com or need an alternative format:
Email: hello@yonihavana.com
Relay (TRS): Dial 7-1-1 for TTY assistance
Mailing address (optional): [Add address if you want to receive mailed requests]
Response times: We aim to acknowledge accessibility inquiries within 2 business days and to provide a path to resolution or an accessible alternative within 30 days (often sooner). Complex fixes may take longer; we’ll keep you updated.
Formal Complaints & Enforcement
If you believe we have not adequately addressed your concern, you may have the right to file a complaint with relevant authorities (for example, under the ADA or Section 508 where applicable). We recommend consulting official guidance for your jurisdiction. We’re committed to resolving issues directly and promptly whenever possible.
Preparation of This Accessibility Statement
Assessment approach: Self-evaluation using WCAG 2.2 Level AA criteria, periodic automated checks, manual keyboard/AT testing, and content reviews.
Date first published: 9.26.2025
Last reviewed: 9.26.2025
Next planned review: 12.31.2025