Legal
Accessi-bility.
Last updated: August 2026
FIREWEB is committed to making fireweb.ie accessible to as many people as possible, and to fixing problems when they are found.
Our aim
FIREWEB wants fireweb.ie to be usable by as many people as possible, including people who use screen readers, keyboard-only navigation, screen magnification, speech input, or who prefer reduced motion.
Accessibility is treated as part of design and build quality rather than an add-on, and it is something we work on continuously.
The standard we work towards
We aim to meet the fundamentals of the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This is a target we design and build towards; we do not claim certification, formal audit sign-off or perfect compliance across every page and assistive technology combination.
Measures we have taken
Practical steps taken on this website include:
- semantic HTML structure with a single main landmark, and headings in a logical order on each page
- a skip link that lets keyboard users jump straight to the main content
- keyboard operability for navigation, the mobile menu, accordions, forms and dialogs, using accessible component patterns rather than custom widgets
- visible focus indicators on interactive elements, using a high-contrast accent outline
- accessible names for icon-only controls, and decorative graphics hidden from assistive technology
- form fields with associated labels, clearly marked required fields, and error and success messages announced to assistive technology
- text and interface colours chosen for contrast against their backgrounds, with meaning never conveyed by colour alone
- text that reflows and remains readable when zoomed or on small screens, with generous tap-target sizes
- respect for the operating-system "reduce motion" setting, which suppresses or shortens non-essential reveal and transition animations
- descriptive alternative text for meaningful images, and link text that makes sense out of context
No accessibility overlay
We do not use an accessibility overlay, plugin or widget. Overlays frequently interfere with people's own assistive technology, so we fix accessibility in the underlying code instead.
Known limitations and ongoing review
Some areas may still fall short, and we would rather say so than overstate our position. Known and possible limitations include:
- large editorial display typography and decorative type may render awkwardly at very high zoom levels on narrow screens
- some longer case-study and article pages have not been tested with every screen reader and browser combination
- third-party content we do not control — such as web fonts or anything a client later embeds — may not meet the same standard
- older content may be less consistent than recently reviewed pages
We review accessibility as part of ongoing site maintenance, when we redesign a section, and when new content or components are added. Issues reported to us are prioritised and fixed as part of that work.
Assessment approach
This statement is based on our own review of the website: manual keyboard and screen-reader spot checks, colour-contrast checks against the design tokens used sitewide, responsive and zoom testing, and code-level review of markup, labelling and motion preferences. It is a self-assessment, not a third-party audit.
Feedback and contact
If you have difficulty using any part of this website, or need information in a different format, please tell us. Email info@fireweb.ie and describe the page and the problem, and we will respond as quickly as we can and work with you to provide what you need another way in the meantime.
You can also call +353 85 108 9986. FIREWEB is based in Cork, Ireland.
Enforcement
If you are not satisfied with how we respond to an accessibility issue, you can contact the relevant Irish body responsible for accessibility oversight, including the Irish Human Rights and Equality Commission, which handles queries about accessibility obligations in Ireland.
Questions? Email info@fireweb.ie.