Accessibility Statement
Last updated: 4 September 2025

We want everyone who visits olive-gnat-835556.hostingersite.com to be able to use the site with ease. We’re committed to digital accessibility and to designing, building, and maintaining our website in line with recognised standards.

Standards we aim to meet

• We strive to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA.
• We reference the European Standard EN 301 549 (which maps to WCAG for web content).
• Accessibility is an ongoing effort; we continually improve as standards and technologies evolve.

Conformance status

• We believe our site is largely conformant with WCAG 2.2 Level AA. Some parts may not fully conform yet.
• If you encounter any barrier, please let us know. We take feedback seriously and aim to fix issues promptly.

Measures we take to support accessibility

• Build accessibility into our design and development process (privacy- and accessibility-by-design).
• Use semantic HTML, correct heading structure, and meaningful link text.
• Provide sufficient colour contrast and visible focus states.
• Ensure keyboard accessibility for navigation and interactive components.
• Add text alternatives for meaningful images and icons.
• Label form fields, group related fields, and provide clear error messages.
• Avoid autoplaying media and provide captions or transcripts for video/audio where present.
• Test with automated tools and manual checks before publishing significant changes.
• Train team members and follow internal checklists for accessible content.

Accessibility features of this website

• Skip links: A “Skip to main content” link is available for keyboard and screen reader users.
• Keyboard navigation: All menus, buttons, and forms are designed to be reachable and operable via keyboard (Tab, Shift+Tab, Enter, Space, Arrow keys where appropriate).
• Responsive design and reflow: Content adapts to different devices and supports zoom up to at least 200% without loss of functionality.
• Headings and landmarks: Pages use logical headings (H1–H6) and ARIA landmarks (header, nav, main, footer) to support quick navigation.
• Forms: Inputs have associated labels, instructions, and clear validation feedback.
• Images and media: Informative images include alt text; decorative images are marked to be ignored by assistive technologies.
• Links and buttons: Link purpose is clear from text or context, with visible focus indicators.
• Contrast and colour: We avoid relying on colour alone to convey information and maintain sufficient contrast ratios.

Known limitations and what we’re doing about them
We are aware that:

• Some third‑party embeds (e.g., maps, video players, social widgets) may not be fully keyboard accessible or may set cookies before consent. Where possible, we provide accessible alternatives, placeholders, or consent‑gated loading.
• Legacy content or older blog posts may occasionally have missing alt text or headings that need refinement. We are auditing and updating these items on a rolling basis.
• PDF or downloadable assets from third parties may not meet accessibility standards. On request, we will provide an accessible alternative format.

If you find an issue not listed above, please contact us. We aim to acknowledge reports within 2 business days and provide a timeline for fixes, typically within 10–20 business days depending on complexity.

Technical specifications and compatibility

• Technologies: HTML5, WAI‑ARIA, CSS, JavaScript.
• Supported browsers: The latest versions of Chrome, Firefox, Safari, and Edge. Older browsers may have reduced support.
• Assistive technologies: We aim to support a range of tools including screen readers (e.g., NVDA, JAWS, VoiceOver) and screen magnifiers.
• Some features rely on JavaScript. Core navigation and content remain accessible if scripts fail to load, but certain interactive elements may not function without JavaScript.

Assessment approach

• Self‑evaluation using automated tools (e.g., WAVE, axe, Lighthouse) plus manual keyboard and screen reader checks.
• Content reviews against our internal accessibility checklist before major releases.
• Periodic re‑testing when we introduce new components, templates, or third‑party integrations.

Feedback, requests, and contact
We welcome your feedback on the accessibility of our site. If you need information in a different format (accessible PDF, large print, plain text), or you encounter a barrier, contact us:

• Email: info@olive-gnat-835556.hostingersite.com
• Phone: +353-867807401
• Postal address: [Add your Irish business address]

Please include:

• The page or feature where you had an issue (URL if possible)
• A description of the problem and any assistive tech or browser you’re using
• Your preferred way for us to contact you

We aim to acknowledge within 2 business days and resolve issues as quickly as possible.

Formal complaints and escalation
If you’re dissatisfied with our response, please ask for your case to be escalated to a manager. For advice on your accessibility rights in Ireland, you can also contact the Irish Human Rights and Equality Commission (www.ihrec.ie). This information is provided for guidance; it does not limit your legal rights.

Third‑party content and services
Our website may link to or embed content from third‑party providers (e.g., video platforms, booking/payment tools). While we strive to choose accessible solutions, we do not control their code. We monitor these integrations and, where feasible, offer accessible alternatives or clearly label limitations.

For our clients
Accessibility is part of our delivery approach. On client projects we can:

• Design and build to WCAG 2.2 AA guidelines
• Provide accessibility reviews of designs and content
• Implement accessible forms, menus, and media
• Configure consent management and reduce non‑essential script loading
• Offer audits with prioritized remediation plans