ParliView — European Parliament Transparency Platform
Version: 1.0
Effective Date: 30 September 2026
Last Updated: 25 September 2026
UCD is committed to making its websites and mobile applications accessible, in accordance with the European Union (Accessibility of Websites and Mobile Applications of Public Sector Bodies) Regulations 2020 (S.I. No. 358 of 2020), which give effect to Directive (EU) 2016/2102.
This statement applies to:
Both are provided by the School of Politics and International Relations, UCD, as part of the Study (UCD research ethics reference 025-HS-26-C-Cross).
The standard we work to is EN 301 549 v3.2.1 (Accessibility requirements for ICT products and services), which incorporates WCAG 2.1 at level AA.
The Platform is partially compliant with the Regulations and with EN 301 549 v3.2.1 (WCAG 2.1 level AA), because of the non-compliances listed in section 3.
The content listed below is not accessible for the reasons given.
All items in this section were identified by code review, not by testing with assistive technology. Each item names the WCAG 2.1 success criterion concerned and the date by which we plan to fix it.
The app (app.parliview.org)
| # | What does not work | What this means for you | WCAG 2.1 criterion | Planned fix |
|---|---|---|---|---|
| A1 | Answers appear word by word but there is no live region to announce them | If you use a screen reader, you are not told when an Answer starts or finishes | 4.1.3 Status messages (AA) | 31 December 2026 |
| A2 | The question box has a placeholder but no label | Screen readers may not say what the box is for; the placeholder disappears when you type | 1.3.1, 3.3.2, 4.1.2 (A) | 31 December 2026 |
| A3 | Expandable sections inside Answers (processing steps, search summaries, source summaries) can only be opened with a mouse | You cannot reach or open them with the keyboard alone | 2.1.1 Keyboard (A), 4.1.2 Name, role, value (A) | 31 December 2026 |
| A4 | Every screen in the app has the same page title, “ParliView” | Screen readers and browser tabs cannot tell you which screen you are on (sign in, request access, acknowledgement, conversation) | 2.4.2 Page titled (A) | 31 December 2026 |
| A5 | There is no “skip to content” link and no landmark regions (main, navigation) | Keyboard and screen-reader users must move through every control to reach the content | 2.4.1 Bypass blocks (A) | 31 December 2026 |
| A6 | In light mode, links inside Answers and inside the Privacy Notice and Participant Terms shown at the acceptance gate are gold on white (about 2.3:1) | Links, including citations to EP Material, can be hard to read | 1.4.3 Contrast (minimum) (AA) | 31 December 2026 |
| A7 | Some secondary text (captions, hints, placeholder text) is grey at about 2.9:1 to 3.9:1 in both light and dark mode | Text can be hard to read, especially on the cream panels | 1.4.3 Contrast (minimum) (AA) | 31 December 2026 |
| A8 | In dark mode, the main buttons (Submit request, Continue to ParliView, Send) have white text on light blue (about 2.7:1); in light mode the same buttons turn gold with white text on hover | Button labels can be hard to read | 1.4.3 Contrast (minimum) (AA) | 31 December 2026 |
| A9 | In the vote breakdown, the green “For” figures and the grey “Abstain” figures have low contrast; the vote bars have no names | Figures can be hard to read; screen readers announce unnamed progress bars. The figures are also given as text, so no information depends on colour alone | 1.4.3 (AA), 4.1.2 (A) | 31 December 2026 |
| A10 | The Privacy Notice and Participant Terms at the acceptance gate are shown in a scrolling box that may not take keyboard focus | In some browsers, you cannot scroll the documents with the keyboard before ticking the acknowledgement | 2.1.1 Keyboard (A) | 31 December 2026 |
| A11 | Some pop-up panels (citation previews, glossary tips, explain mode, information tips) remove the visible focus outline | You may lose track of where keyboard focus is | 2.4.7 Focus visible (AA) | 31 December 2026 |
| A12 | Quotations from EP Material in other EU languages are not marked with their language | Screen readers may read them with the wrong pronunciation | 3.1.2 Language of parts (AA) | 31 December 2026 |
The website (www.parliview.org)
| # | What does not work | What this means for you | WCAG 2.1 criterion | Planned fix |
|---|---|---|---|---|
| W1 | The gold buttons (“Sign up for research preview”, “Try ParliView”, “Sign up”, “Follow us on LinkedIn”) have white text on gold (about 2.3:1) | Button labels can be hard to read | 1.4.3 Contrast (minimum) (AA) | 31 December 2026 |
| W2 | The word “AI” in the home-page heading is gold on cream (about 2.0:1) | The heading can be hard to read | 1.4.3 Contrast (minimum) (AA) | 31 December 2026 |
| W3 | Grey text (the email label, the sign-up note, the partner line, the page contents list on the legal pages, and the footer copyright line) is between about 3.2:1 and 4.0:1 | Text can be hard to read | 1.4.3 Contrast (minimum) (AA) | 31 December 2026 |
| W4 | The focus ring on the email box is gold on cream (about 2.0:1) | Keyboard users may not see that the box has focus | 1.4.11 Non-text contrast (AA) | 31 December 2026 |
| W5 | There is no “skip to content” link and the navigation and content areas are not marked as landmarks. Headings are present, so you can navigate by heading | Keyboard and screen-reader users must move through the navigation on every page | 2.4.1 Bypass blocks (A) | 31 December 2026 |
| W6 | Three decorative icons on the home page are not hidden from screen readers | Screen readers may announce empty images | 1.1.1 Non-text content (A) | 31 December 2026 |
We do not claim disproportionate burden for any content.
This statement was prepared on 17 September 2026.
The assessment was a self-assessment carried out by UCD. The method was a review of the source code of the website (HTML and CSS) and of the app (React and TypeScript components) against WCAG 2.1 level AA. Colour contrast ratios were calculated from the colour values in the code. The Platform was not tested with screen readers, screen magnifiers, voice control or switch access, and no automated accessibility tool was run.
We plan to test the Platform with assistive technology in Q4 2026 and to update this statement with the results.
This statement was last reviewed on 17 September 2026.
If you find something on the Platform that you cannot use, or if you need information from the Platform in another format (for example, large print or plain text), contact us:
Tell us the web address or the screen you were using, what you were trying to do, and the assistive technology or browser you use, if any. We aim to reply within 10 working days.
If you are not satisfied with our reply, you can make a complaint. Under the Regulations, the enforcement procedure in Ireland is against the NDA model statement:
The National Disability Authority monitors compliance with the Regulations.
Answers and Summaries on the Platform are AI Output. Each carries a visible “AI-generated” label. Article 50 of the EU Artificial Intelligence Act requires that this information is provided in a way that is accessible to people with disabilities. We therefore commit that the label in code:
The Platform also:
We will review this statement whenever the Platform changes in a way that affects accessibility, and at least once a year. The dates at the top of this page show the current version.