Legal
Accessibility statement
This statement explains how accessible projineer.com is, what we have checked and fixed, where we know the site still falls short and how to tell us about a problem.
If anything on the site gets in your way, you can phone us on 021 471 2019 or email info@projineer.com instead.
Last updated 4 October 2026
The standard we aim to meet
Projineer Limited wants everyone who visits projineer.com to be able to read about our services and get in touch with us, whether they use a mouse, a keyboard, a phone, screen magnification or other assistive technology.
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, the accessibility standard published by the World Wide Web Consortium (W3C). WCAG 2.2 Level AA is the target we design and test the site against. It is not a certification, and this statement should not be read as one.
Conformance status
The projineer.com website partially conforms with WCAG 2.2 Level AA. This means some parts of the site may not yet fully meet the standard, and we have not yet been able to confirm that every page meets every requirement.
We have run automated checks on every public page and a set of manual checks covering keyboard use, focus, layout, images and forms, and we fixed the problems the automated checks found. We have not yet tested the site with screen readers or carried out a full manual audit against each WCAG success criterion, and automated tools cannot judge everything the standard asks for, such as whether a text alternative describes an image well. One part of the contact form, the spam check, is also a third-party widget that we have not tested ourselves and can change only a little. Until those gaps are closed, partial conformance is the accurate description.
How we checked the site
We checked the site on 3 October 2026, using a preview copy of the version prepared for launch.
Automated checks
We ran the axe-core accessibility testing tool (version 4.10.2) on every page of the site, including the page-not-found page, at a desktop width of 1440 pixels and at phone widths of 375 and 320 pixels, and checked each page for sideways scrolling at those widths. The checks used the axe-core rules for WCAG 2.0, 2.1 and 2.2 at Levels A and AA, together with its best-practice rules.
Manual checks
Alongside the automated checks, we:
- used the main menu and the mobile menu with a keyboard alone, opening each one, moving through its links and closing it with the Escape key
- confirmed that links and buttons show a visible 3 pixel outline when they receive keyboard focus
- confirmed that the “Skip to main content” link is the first thing you reach with the Tab key
- confirmed that every page fits a screen 320 pixels wide without sideways scrolling
- checked page layouts at 375 pixels and 1440 pixels wide
- confirmed that animations switch off when a device is set to reduce motion
- confirmed that every image has a text alternative
- confirmed that each page has a single main heading
- confirmed that contact form fields have visible labels and that error messages are linked to the fields they relate to
What we have not tested yet
We have not yet tested the site with screen readers such as NVDA, JAWS or VoiceOver, we have not tested it with disabled people using their own set-ups, and we have not carried out a full manual audit against every WCAG 2.2 success criterion.
The cookie consent panel and the Cookie settings control in the footer appear only on the live site, not on the preview copy, so they were not part of these checks. The optional document upload on the contact form was added on 4 October 2026, after these checks, so it has not been through them yet.
What we fixed on 3 October 2026
The automated checks found seven problems, and we fixed all of them the same day.
| Problem we found | What we changed |
|---|---|
| Gold text on small labels and numbers did not contrast strongly enough with light backgrounds. | We added a darker gold for small text, with a contrast ratio of at least 4.5 to 1 on the site’s white and light backgrounds. |
| Gold buttons inside dark sections picked up the light link colour used in those sections, which made their labels hard to read. | Buttons now keep their own dark label on the gold background inside dark sections too. |
| The phone number strip at the top of each page sat outside any page landmark, so people moving around the page by landmarks could miss it. | We made the strip a labelled landmark of its own, named “Phone”. The strip has since been removed, and the phone number now sits in the page header. |
| Rows of related links were each marked up as separate navigation landmarks with repeated names, which cluttered the list of landmarks. | Those rows are now ordinary lists of links rather than separate landmarks. |
| A small label on the page-not-found page had low contrast. | We increased its contrast. |
| On phones, the legal links at the bottom of each page wrapped into rows with tap targets smaller than WCAG asks for. | Each of those links now has a tap target at least 44 pixels tall. |
| Wide tables, such as those in our cookie policy, scroll sideways on phones, but keyboard users could not move into them to scroll. | Each table now sits in a labelled area that you can reach with the Tab key and scroll with the arrow keys. |
After these changes, the automated checks reported no violations on any page at any of the three widths.
Features that should help
- Keyboard access. The main menu and the mobile menu can be opened, used and closed with a keyboard alone, and the Escape key closes them.
- Skip link. A “Skip to main content” link is the first item you reach with the Tab key, so you can jump past the menu.
- Visible focus. Links and buttons show a clear 3 pixel outline when you reach them with the keyboard, so you can see where you are on the page.
- Reduced motion. If your device is set to reduce motion, the site switches off its animations and smooth scrolling.
- Text alternatives. Every image has a text alternative.
- Clear page structure. Each page has a single main heading.
- Labelled form fields. Each field on the contact form has a visible label, and error messages are linked to the field they relate to.
- Layouts that reflow. Every page fits a screen 320 pixels wide without sideways scrolling. WCAG treats that width as the equivalent of zooming to 400% in a browser window 1280 pixels wide.
Known limitations
The spam check on the contact form
Our contact form uses Cloudflare Turnstile, a spam check provided by Cloudflare, Inc., to stop automated submissions. It is a third-party widget that loads from Cloudflare’s servers. Cloudflare states that Turnstile meets WCAG 2.2 Level AA, but we have not tested it ourselves, and apart from choosing its size and colour scheme we cannot change how it looks or works. If the check stops you sending the form, phone us on 021 471 2019 or email info@projineer.com and we will take your enquiry that way.
Resource articles
The guidance articles in our resources section were included in the automated checks, but they have not yet had their content review. Until that review is done, some articles may be harder to read or follow than they should be. If you find one difficult to use, tell us which one and we will look at it.
Other ways to contact us
You do not have to use the website to reach us. If any part of the site does not work for you, contact us directly:
- Phone: 021 471 2019, or +353 21 471 2019 from outside Ireland
- Email: info@projineer.com
Reporting a problem
If you find something on projineer.com that you cannot use, or that is harder to use than it should be, please tell us by email at info@projineer.com or by phone on 021 471 2019.
It helps us find and fix the problem if you can include:
- the web address (URL) of the page, or the name of the page if that is easier
- what you were trying to do
- what went wrong, including any error message you saw
- the device and browser you were using, and any assistive technology, such as a screen reader, screen magnifier or voice control software, with version numbers if you know them
- how you would like us to reply
Tell us whatever you can; you do not need every detail. We will reply as soon as we can.
How we handle the details you send us is explained in our privacy notice and on our data protection page.
About this statement
We prepared this statement on 3 October 2026, based on the checks described above. We will review it when the site changes significantly and update the date at the top of this page when we do.
You may also want to read our cookie policy and our website terms.