Accessibility
We want everyone to be able to use this website
Prosper Fingal is committed to making this website accessible and easier to understand, including for people with an intellectual disability.
Compliance status
This website has been designed and reviewed against the Web Content Accessibility Guidelines, WCAG 2.2 Level AA. We also take account of the web requirements in EN 301 549 V3.2.1.
Based on the internal technical audit completed on 5 August 2026, the website is partially compliant. The audited page templates performed well in keyboard, accessibility-tree, zoom, reflow and responsive mobile checks. Full conformance is not claimed because testing with real screen-reader users and physical devices, service-user testing, and a complete review of every downloadable document and future third-party component have not yet been completed.
Statement prepared: 5 August 2026.
Last reviewed: 5 August 2026.
Next review: before public launch and after major design or content changes.
What has been built in
Accessibility features in the website
Clear structure
Pages use a main heading, ordered subheadings, short sections, lists, breadcrumbs and descriptive link text.
Readable content
Body text is large, line spacing is generous and important information is written in direct language.
Strong contrast
Dark text is used on light backgrounds. Bright brand colours are accents and meaning does not rely on colour alone.
Keyboard access
A skip link bypasses repeated navigation. Links, buttons, menus and expandable questions have clear focus styles and large targets.
Reduced motion
The design avoids auto-playing carousels and respects the device preference for reduced motion.
Flexible display
The layout adapts to phones, tablets and larger screens and is designed to reflow when content is enlarged.
Technical audit
What was tested on 5 August 2026
The audit combined automated checks, source review and browser-based interaction tests using representative Prosper Fingal page components.
Keyboard
Tab order, visible focus, dropdown navigation, disclosure controls and the skip-to-main-content route were tested. Native expandable questions opened with the Enter key and focus remained visible.
Screen-reader structure
The Chromium accessibility tree was inspected for headings, links, images, navigation and content structure. Images reviewed had useful alternative text or were marked as decorative.
Zoom and reflow
Layouts were tested at widths representing 200% zoom and the WCAG reflow requirement of 320 CSS pixels, equivalent to a 1280-pixel-wide viewport at 400% zoom. Tested content did not require two-directional scrolling.
Mobile and orientation
Representative pages were checked at 375 and 320 CSS pixels and in a small landscape viewport. Cards, buttons, headings, contact panels and navigation remained available without clipped content.
Text spacing and resizing
Stress tests applied increased line height, paragraph spacing, letter spacing and word spacing. Text was also enlarged to 200% to check for loss of content or functionality.
Controls and focus
Prominent tested controls met or exceeded 24 by 24 CSS pixels. Strong focus indicators, scroll spacing and wrapping rules were added to keep keyboard focus and long text visible.
Corrections made
Changes completed during the audit
- A visible-on-focus “Skip to main content” link was added to the primary navigation.
- The main content target on every published page and news story was made programmatically focusable.
- Keyboard focus indicators were strengthened with a dark outline and a light halo so they remain visible on different backgrounds.
- Scroll spacing was added so a fixed header does not hide the focused or linked-to content.
- Desktop dropdown menus now remain available while focus is within the menu.
- Mobile navigation targets were enlarged and nested service links remain available when the mobile menu is opened.
- Long words and URLs can wrap, and grid items are allowed to shrink without creating horizontal page overflow.
- Decorative visual overflow was contained so it does not create unwanted horizontal scrolling.
- Expandable questions retain native keyboard and accessibility behaviour while using a clearer visual indicator.
- The Prosper Fingal logo in the media library was given descriptive alternative text.
Cognitive accessibility
Making information easier to understand
- Important pages begin with a direct explanation of what the page is about.
- Common tasks are presented as numbered steps.
- Service pages include short “In simple words” summaries.
- Navigation labels use familiar words.
- Long information is separated into clear topics.
- Contact options are repeated near the point where a person may need help.
Easy Read development
The clear-language web content is a starting point. Formal Easy Read documents should combine simple text with helpful images and should be tested with people who use Easy Read.
Prosper Fingal should prioritise Easy Read versions of application, safeguarding, complaints, privacy and service information.
Known limitations
Work that still needs human or content-specific testing
Real screen-reader sessions
The audit inspected the browser accessibility tree, but it did not replace hands-on testing with NVDA, JAWS, VoiceOver or TalkBack on their supported operating systems and devices.
Physical-device testing
Responsive layouts were tested in browser emulation. Final launch testing should also use representative iPhone, iPad and Android devices with their built-in accessibility settings.
Documents and media
Each PDF, Word document, video and audio item needs its own accessibility review. Documents may need tagging, reading-order corrections, captions, transcripts or an accessible HTML alternative.
Third-party components
Future forms, cookie controls, maps, media players, CAPTCHA and other plugins must be tested after they are configured. A plugin can introduce barriers even when the page around it is accessible.
Service-user testing
People with intellectual disabilities should test key journeys, wording, navigation and Easy Read materials before launch and after major changes.
Ongoing content checks
New pages, images, links and downloads must be checked before publication. Accessibility Checker supports this process but does not replace manual review.
Ask for help
We can provide information another way
Tell us which information you need and what format helps you. This may include plain language, larger print, an accessible digital document or support from a person who can explain it.
When reporting a website problem, please include the page address, what you were trying to do, what went wrong and the device or assistive technology you used.
Accessibility contact
Email: info@prosperfingal.ie
Phone: 01 849 3600
Prosper FingalStrand Street
Skerries
Co. Dublin
K34 TD61
Complaints and redress
What to do if the response does not resolve the problem
Please contact Prosper Fingal first and allow us a reasonable opportunity to investigate and respond.
Depending on the legal route that applies to the complaint, information may also be available from the Office of the Ombudsman or the Workplace Relations Commission. The National Disability Authority explains accessibility statement and redress requirements for bodies within the Irish public-sector regulations.
Your feedback matters
Accessibility improves when people tell us what is difficult. Please report barriers, unclear information or features that do not work with your technology.