Please check: hidden link
Your default banner for in development sites is not accessible. contrast ofcolor and background color is not enough: hidden link
Please fix this so we can focus on messages that are from our website, not added by WPML.
I’m Prosenjit from the WPML Development Team, and I’ll be happy to assist you with this.
I completely understand the issue, and I’d like to let you know that I was able to replicate it in my local development environment.
The issue is caused by the color contrast used in the development site banner. At the moment, the contrast ratio between the text and background is 3.24:1, while the accessibility guidelines require a minimum of 4.5:1 for normal text. Because of that, Lighthouse / PageSpeed reports a lower accessibility score for the banner.
The good news is that the fix is very simple. I tested it locally, and after adjusting the colors, I was able to reach 100% accessibility without affecting the rest of the page. Please have a look at the attached screenshot.
Here's what you need to do:
- From the admin Dashboard, please go to Appearance > Customize > Additional CSS
- Paste the following CSS code and save the changes.
/* Improve contrast for WPML development banner */
.otgs-development-site-front-end {
background-color: #235D6D !important; /* Darker blue for better contrast */
color: #ffffff !important;
}
.otgs-development-site-front-end a {
color: #ffffff !important;
text-decoration: underline !important; /* Adding underline also helps accessibility for links */
}
Once that’s done, please run the PageSpeed test again. The Accessibility score should then show 100, and the banner-related accessibility warning should no longer appear.
Rest assured, we’ll do our best to include this fix in an upcoming version of WPML.
Please let me know if you have any other questions or need any clarification. I’ll be happy to help.
I hope you’re doing well, and I’m sorry for the delayed reply due to the weekend.
Please note that this issue has already been escalated internally, and we are currently reviewing the best way to handle it in the core plugin.
Once a proper fix is ready in WPML, it will be included in a future update. However, at the moment, we do not have a confirmed ETA or a specific version planned yet, so I can’t provide a solid timeline for when the fix will be released. I’m sorry for the inconvenience.
Until we release an official fix, please continue using the workaround I shared in my previous message. That should definitely help avoid the negative impact on the accessibility score.
I hope that makes sense, and thank you for your understanding.
If you have any questions or need any clarification, please feel free to let me know. I’ll be happy to help.
