Title: Accessibility Issues Last modified: February 9, 2025 --- # Accessibility Issues * Resolved [Amber Hinds](https://wordpress.org/support/users/alh0319/) * (@alh0319) * [1 year, 4 months ago](https://wordpress.org/support/topic/accessibility-issues-44/) * Hi Matthias, * We’d like to use your plugin on the WP Accessibility Day and some client websites, but there are some accessibility problems with it. I tried looking for a GitHub repo to open issues but didn’t see one. I can open threads in this support forum, but wanted to check first on if you prefer for all issues to be reported in a single post or if it would be easier for you to track if separate threads were started for each issue. * Your plugin is the best of all the plugins that I tested from an accessibility perspective and I’m hoping you can prioritize accessibility fixes to make it truly useable for all users and conformant with WCAG in advance of the European Accessibility Act enforcement deadline coming up. * Thanks so much for your resposne. * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Faccessibility-issues-44%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 6 replies - 1 through 6 (of 6 total) * Plugin Contributor [Matthias Günter](https://wordpress.org/support/users/mguenter/) * (@mguenter) * [1 year, 3 months ago](https://wordpress.org/support/topic/accessibility-issues-44/#post-18300896) * Hey [@alh0319](https://wordpress.org/support/users/alh0319/) ! * You are welcome to post the accessibility issues here via wordpress.org support forum. If you are a PRO user, you can directly contact us via [https://devowl.io/support](https://devowl.io/support). You do not need to open a new thread per issue, you can combine them into one request. * Thread Starter [Amber Hinds](https://wordpress.org/support/users/alh0319/) * (@alh0319) * [1 year, 3 months ago](https://wordpress.org/support/topic/accessibility-issues-44/#post-18302953) * Thanks for getting back to me, [@mguenter](https://wordpress.org/support/users/mguenter/). I did purchase pro, but for transparency reasons (for other members of the WP Accessibility Day organizing team), I prefer to post issues in a public place. I appreciate that I don’t need to open a new thread for each issue. * We did a comprehensive review of the modal as it is currently configured on [https://template.wpaccessibility.day/](https://template.wpaccessibility.day/). This testing was done by multiple accessibility professionals including one blind screen reader user. These are the issues that were identified: 1. The dialog is not consistently getting focus on load. 2. Modal heading should be an H2 instead of an H3. 3. The `` tag needs `aria-modal="true"` added to it. 4. Show service information “links” (and any others) that expand hidden content need to be buttons. You can correct this by adding `role="button"` to them and adding support for space bar triggering. 5. Show service information buttons (currently coded as ``) should have unique names. 6. Hide the middots from screen readers with `aria-hidden="true"` or by displaying them via CSS (better). 7. All links that have been made buttons with role=”button” need to have space bar handlers added so they can be triggered with the spacebar. [Learn more about keyboard expectations when adding `role="button"`.](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles/button_role) 8. When the “underline” style is set for links, the underline should disappear on hover so color alone is not being used to indicate the hover state. 9. There’s a focus order issue after expanding the individual settings options. This is because the link to configure individual settings is removed from the page when clicked. Removing an element from the DOM causes the keyboard to lose focus. The individual settings button should stay visible in the modal, and all the newly added content should be introduced after it (I.e., it should function like an accordion). 10. Consent choices checkboxes read the label three times because they’re over- engineered. `
Individual Privacy Preferences: Essential
Essential services are required for the basic functionality of the website. They only contain technically necessary services. These services cannot be objected to.  •  
` My recommendation on these is to: 11. - Move the fieldset and legend from being wrapped around the parent input and just wrap it around the group of sub checkboxes. - Remove the aria-labelledby attribute from the input since it’s wrapped in the label tag already. - Remove aria-hidden=”true” from the span around the label text. - Add aria-describedby attributes to the checkbox inputs referencing the helper text. * Thank you very much for your attention to these issues. Please let me know if you have any questions or need more information about any of the listed issues. I’d love to see the plugin made fully accessible — I can see you’ve already put some effort in. * Plugin Contributor [Matthias Günter](https://wordpress.org/support/users/mguenter/) * (@mguenter) * [1 year, 3 months ago](https://wordpress.org/support/topic/accessibility-issues-44/#post-18303256) * Hey [@alh0319](https://wordpress.org/support/users/alh0319/) ! * Thanks for the list. I see you are using the PRO version, and therefore I will close this wordpress.org support thread and reply to you via your support thread, soon. 😊 * Plugin Contributor [Jan Karres](https://wordpress.org/support/users/jankarres/) * (@jankarres) * [11 months ago](https://wordpress.org/support/topic/accessibility-issues-44/#post-18548871) * **We’re pleased to announce that today’s release of Real Cookie Banner v5.1.12 resolves, according to our knowledge, all accessibility issues** originally reported by [@alh0319](https://wordpress.org/support/users/alh0319/) on March 13, 2025( private ticket). - March 13, 2025: [@alh0319](https://wordpress.org/support/users/alh0319/) submits ten accessibility issues. - March 20, 2025: we send follow-up questions after a technical assessment to clarify each point. - April 26, 2025 & May 7, 2025: we receive detailed feedback. - May 9, 2025: we share a pre-release build with [@alh0319](https://wordpress.org/support/users/alh0319/) to verify the fixes. * We sent several reminders but haven’t yet received further feedback on the implemented fixes. [@alh0319](https://wordpress.org/support/users/alh0319/) published her findings at [https://equalizedigital.com/wordpress-cookie-banner-accessibility-lies/](https://equalizedigital.com/wordpress-cookie-banner-accessibility-lies/). * We apologize for the extended timeline due to waiting for feedback and thank [@alh0319](https://wordpress.org/support/users/alh0319/) for her expert guidance. If you spot any remaining or new accessibility issues, please let us know here so we can address them in a timely manner! - This reply was modified 11 months ago by [Jan Karres](https://wordpress.org/support/users/jankarres/). * Plugin Contributor [Jan Karres](https://wordpress.org/support/users/jankarres/) * (@jankarres) * [9 months ago](https://wordpress.org/support/topic/accessibility-issues-44/#post-18628947) * When summarizing the chronological history of the communication process, we made mistakes regarding the dates provided. We apologize for this! * Below you will find a corrected and more complete history of the collaboration: - February 13, 2025: Amber submits the accessibility issues. - February 20, 2025: We implemented the requested changes as far as possible and shared a pre-release version of the fixes with you. In addition, we sent follow-up questions after a technical assessment to clarify each open point. * Most issues were resolved by us within seven days of being reported, as it is important to us that people with disabilities do not experience unnecessary barriers when using our product. - March 1, 2025 until April 22, 2025: We sent Amber multiple reminder, and she promised to test the pre-release version by the dates she suggested. - April 26, 2025: Amber’s college provided feedback to us that with the pre- release from February 20, 2025 “accessibility is greatly improved” and answered some of the open points from February 20, 2025. - April 28, 2025: We asked for clarification because we did not understand some of the feedback. - May 7, 2025: Amber’s college answered some of the open points. - May 9, 2025: We provided another pre-release implementing all left points in accordance with the provided answers. We asked to test the pre-release again if we fixed the open points correctly in their perspective. * The outstanding issues were resolved by us within two times two days of responding to the open questions so that disabled people could receive a more accessible cookie banner as quickly as possible. - May 16, 2025 until June 16, 2025: We sent several friendly reminders and reminded Amber personally at WordCamp Europe, whereupon she promised several times to test the pre-release version on specific dates she had set. - July 10, 2025: We released the fixes, as many disabled people have already waited about five months for the fixes of the accessibility issues. At that point, we expected to receive no further response from Amber or any Equalize Digital employee regarding the outstanding issues. * As of today, we have not yet received any feedback from Amber or her company for the pre-release provided on May 9, 2025. * Thread Starter [Amber Hinds](https://wordpress.org/support/users/alh0319/) * (@alh0319) * [9 months ago](https://wordpress.org/support/topic/accessibility-issues-44/#post-18629443) * For public record, I believe the timeline above has inaccuracies. However, because I don’t believe that WordPress support forum is the appropriate place for personal disagreements, I will leave it at that and not go into detail. Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘Accessibility Issues’ is closed to new replies. * ![](https://ps.w.org/real-cookie-banner/assets/icon-256x256.png?rev=2419813) * [Real Cookie Banner: GDPR & ePrivacy Cookie Consent](https://wordpress.org/plugins/real-cookie-banner/) * [Frequently Asked Questions](https://wordpress.org/plugins/real-cookie-banner/#faq) * [Support Threads](https://wordpress.org/support/plugin/real-cookie-banner/) * [Active Topics](https://wordpress.org/support/plugin/real-cookie-banner/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/real-cookie-banner/unresolved/) * [Reviews](https://wordpress.org/support/plugin/real-cookie-banner/reviews/) ## Tags * [a11y](https://wordpress.org/support/topic-tag/a11y/) * 7 replies * 3 participants * Last reply from: [Amber Hinds](https://wordpress.org/support/users/alh0319/) * Last activity: [9 months ago](https://wordpress.org/support/topic/accessibility-issues-44/#post-18629443) * Status: resolved