Accessibility Statement

Accessibility Statement is committed to making its platformaccessible, in accordance with European Union (AccessibilityRequirements of Products and Services) Regulations ****.This accessibility statement applies to*It does not apply to other content or websites published on any of itssubdomains.These websites and their content will have their ownspecific accessibility statement.This website is designed to comply with the technical standard forwebsites and mobile apps, EN ******* v.3.2.1.This closely follows level'AA' of the Web Content Accessibility Guidelines 2.2 level AA.Compliance StatusThis website is partially compliant with technical standard EN *******v.3.2.1 and the Web Content Accessibility Guidelines 2.2 level AA.See is committed to providing a platformthat is accessible to the widest possible audience, regardless oftechnology or ability.We are currently working with Vially and Vision Ireland to ensure wemeet accessibility standards.We are continually improving the user/.-,636%2F****%20-%20European%20Union%20(Accessibility%20Requirements%20of,Products%20and%20Services)%20Regulations%******&text=%E2%80%9CIris%20Oifigi%C3%BAil%E2%80%9D%20of%****th%20December%2C%******.&text=Citation%20and%20commencement-,1.,Products%20and%20Services)%20Regulations%******..-,636%2F****%20-%20European%20Union%20(Accessibility%20Requirements%20of,Products%20and%20Services)%20Regulations%******&text=%E2%80%9CIris%20Oifigi%C3%BAil%E2%80%9D%20of%****th%20December%2C%******.&text=Citation%20and%20commencement-,1.,Products%20and%20Services)%20Regulations%******.////experience for everyone and adhering to the required accessibilitystandards.The Web Content Accessibility Guidelines (WCAG 2.2) definesrequirements for designers and developers to improve accessibility forpeople with disabilities.Preparation of this Accessibility StatementThe Statement is based on a combination of manual and automatedaccessibility testing, using multiple platforms;• Windows (JAWS, NVDA),• Mac (VoiceOver),• iOS (VoiceOver) and Android (TalkBack) and their nativeaccessibility tools.A detailed issue log was created to measure against WCAG 2.2standards.These issues were presented to the development team whoare amending these issues and bringing the platform in to WCAG 2.2 AAcompliance.This statement was created by Vially in June ****.The statement was last reviewed in June ****.Feedback and Contact InformationWe welcome feedback on the accessibility of this website.If you haveany comments or find any problems not listed on this page, pleasecontact [client to enter email]Compatibility with browsers and assistive technologyThis website is designed to be compatible with the following most usedassistive technologies:The latest version of Google Chrome, Microsoft Edge and Apple Safaribrowsers;In combination with the latest versions of NVDA, VoiceOver andTalkBack.Technical specificationsThe accessibility of this website relies on the following technologies towork with the particular combination of web browser and any assistivetechnologies or plugins installed on your computer:• HTML• WAI-ARIA• CSS• JavaScriptAccessible ContentSkip to content link – has been implemented correctly.The "skip tocontent" link on the website appears as the first element on the pagewhen using the 'tab' key on keyboards.Non-accessible ContentDespite our best efforts to ensure the accessibility of this website we areaware of some limitations, which we are working to fix.Below is adescription of known limitations and potential solutions.Please contactus if you encounter an issue not listed below.Known limitations for this website: Keyboard/Screen reader navigation is not yet accessible on parts ofthe platform.Many pages have interactable elements that are eitherplaced in the wrong programmatically determinable order or are skippedentirely by a screen-reader.Other pages feature non-interactableelements that may appear in the wrong focus order on a screen-reader.Some pages also have invisible interactable elements in theprogrammatically determinable focus order.Some pop-up dialogs do notautomatically move the screen-reader focus to them when they areopened.Images – Some parts of this platform feature photos or icons that haveincomplete or missing alt text.We are currently working through imagesto add contextual alternative text.Videos – we are currently working through videos to add accessiblecaptions and other media alternatives.Link Text & Graphical Elements – we are working to remove linksnamed 'read more' and 'click here' where possible, links and graphicalelements such as icons, will be given clear labels.Correctly structured content with good heading usage – Manypages on this platform do not have a programmatically determinableheading structure, whilst other pages feature a heading structure that isin the wrong order.We are creating logical heading structures on ourpages and implementing correct navigation of menu links.Crossoperating system compatibility– has not yet been implementedin every section.We are currently updating CSS for desktop andMobile navigation – along with cross operating system compatibility,once CSS has been updated, we will audit for mobile navigation andease of use for screen readers./Third-party content – there are areas of our website controlled by thirdparty companies, such as the cookies.These are not funded by,developed, or controlled by , but workis in progress to resolve as many issues related to these areas asfeasibly possible.WCAG 2.2 Accessibility Auditing ServiceIf you would like your website, application or digital documents reviewedand tested against the WCAG 2.2 standards, please contact the Viallyteam at ******./mailto:******Accessibility StatementPreparation of this Accessibility StatementFeedback and Contact InformationCompatibility with browsers and assistive technologyTechnical specificationsAccessible ContentNon-accessible ContentWCAG 2.2 Accessibility Auditing Service#J-*****-Ljbffr