Accessibility Statement

Compliance Status

This website is partially compliant with technical standard EN 301 549 v.3.2.1 and the Web Content Accessibility Guidelines 2.2 level AA. See ‘Non-accessible content’ for more details. 

Pallas Projects is committed to providing a website that is accessible to the widest possible audience, regardless of technology or ability.

We are currently working with Vially and Vision Ireland to ensure we meet accessibility standards. We are continually improving the user experience for everyone and adhering to the required accessibility standards. 

The Web Content Accessibility Guidelines (WCAG 2.2) defines requirements for designers and developers to improve accessibility for people with disabilities. 

Preparation of this Accessibility Statement

The Statement is based on a combination of manual and automated accessibility testing, using multiple platforms;

• Windows (JAWS, NVDA),

• Mac (VoiceOver),

• iOS (VoiceOver) and Android (TalkBack) and their native accessibility tools.

A detailed issue log was created to measure against WCAG 2.2 standards. These issues were presented to the development team who are amending these issues and bringing the website in to WCAG 2.2 AA compliance. 

This statement was created by Vially in June 2025. 

The statement was last reviewed in June 2025. 

Feedback and Contact Information 

We welcome feedback on the accessibility of this website. If you have any comments or find any problems not listed on this page, please contact info@pallasprojects.org

Compatibility with browsers and assistive technology

This website is designed to be compatible with the following most used assistive technologies:

The latest version of Google Chrome, Microsoft Edge and Apple Safari browsers;

In combination with the latest versions of NVDA, VoiceOver and TalkBack.

Technical specifications

The accessibility of this website relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML

• WAI-ARIA

• CSS

• JavaScript

Accessible Content

Use Of Colour – Elements on this site never rely on colour alone as the only way to convey their purpose.

Page Language – Every page has a programmatically set language attribute, ensuring screen readers can read content correctly.

Consistent Navigation & Identification: The website maintains consistent placement and labelling of navigation elements across all pages, ensuring users can navigate confidently without confusion.

Page Titles – All pages on this website feature unique and descriptive page titles.

Heading Structure – All pages on this website feature a logical and programmatically determinable heading structure.

Non-accessible Content

Despite our best efforts to ensure the accessibility of this website, we are aware of some limitations, which we are working to fix. Below is a description of known limitations and potential solutions. Please contact us if you encounter an issue not listed below.

Known limitations for this website:

Images – Many important images on this website are either skipped by a screen-reader or are missing descriptive alt texts. We are working towards adding descriptive alternative text to our images.

Reading & Focus Order – The order in which elements receive screen-reader focus on this website is sometimes illogical, and lacking structure. We are working towards fixing the order and structure of our content.

Colour Contrast – Images on this website have a low colour contrast ratio against the background of the page. A user input form on this site also fails colour contrast ratio requirements when viewed in an iOS device. We are in the process of adjusting the colour scheme across our site in order to achieve a higher contrast ratio for all text and graphical elements.

Focus Visibility – The screen-reader will read out every single element on the navigation bar even if they’re not visible at the time. The “Skip Navigation” button is invisible to iPadOS users when it receives Voiceover focus. If an iOS user opens the “Accessibility” menu in the navigation bar, it will become partially obscured by surrounding elements. A single text field in a user input field is invisible to the user when it receives focus from an iOS device with Voiceover activated. We are working on fixing these issues.

Form Input Fields – Some forms on this website do not feature any error identification system for when invalid data is entered. Some required input fields do not visually and programmatically convey their required nature.

Buttons & Links – We are in the process of adding descriptive labels to all buttons and links across our site.