asked on February 5, 2025
Hello!
I am part of a team upgrading an existing, widely-used Angular application. The app was reviewed by a professional accessibility auditing company for WCAG 2.1 Level AA compliance. The audit revealed a number of accessibility issues within Flexmonster, even after enabling high contrast and keyboard navigation modes.
There are 10-20 unique issues that we hope to fix and I am including one below as an example. How might we move forward with raising each of these issues?
Packages: ngx-flexmonster 2.9.96. Angular 15.2.
Best,
Erin, Software Engineer
Issue: Filter panel: Search close button needs an accessible name
The button is missing an accessible name/label. As a result its functionality or purpose is not conveyed to screen reader users.
Element description: Close button in the 'Search' field.
See attached image.
⋅ February 6, 2025
Hello Erin,
Thank you for reporting the issue.
Our team will add an accessible name for the search close button with our minor release with the ETA March 3rd. We will notify you about the release.
Regarding further issues, could you please create a text file or an Excel table with all the descriptions and screenshots of the issues? It would greatly help us.
Looking forward to hearing from you.
Kind regards,
Nadia
⋅ February 6, 2025
Hi Nadia,
Thank you for your prompt response! Yes, I can certainly do this. I will create a text document including images for the issues and write back shortly.
Best,
Erin
⋅ February 7, 2025
Hi Erin,
Thank you for getting back to us!
Sure, we will be looking forward to hearing from you.
Kind regards,
Nadia
⋅ February 10, 2025
Hi Nadia,
Attached below as a PDF is the document with the accessibility issues we noticed in Flexmonster.
Please let me know if you have questions about individual issues. Thank you for your commitment to accessibility!
Best,
Erin
⋅ February 12, 2025
Hi Erin,
Thank you for providing us with the report!
We appreciate the detailed information about accessibility improvements for Flexmonster Pivot. Our team will provide updates about these improvements, which will be released gradually in our upcoming minor updates.
Please let us know if any questions arise.
Kind regards,
Nadia
⋅ March 4, 2025
Hello Erin,
We are happy to inform you that the following accessibility improvements were added:
These fixes are provided in the 2.9.98 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-98/
You are welcome to update the component. Check out our updating tutorial for guidance: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
After carefully analyzing the improvements listed in the accessibility report, we are adding the following issues to our backlog without an ETA at the moment: #1, #6, #9, #10, #11, #13, #18, #21, #22, #23, and #25.
Regarding other improvements, our team will provide the fixes with our minor release with the ETA March 17th. We will keep you updated.
Please let us know if it works for you. Looking forward to hearing from you.
Kind regards,
Nadia
⋅ March 7, 2025
Hi Nadia,
Thank you so much for your response!
I do see your changes and it appears to me that #2, #4, and #5 were resolved. Our accessibility auditor will validate this as well.
I noticed that #3 has not been resolved: the attribute “name” was added to the element with a name for the button, but for text to be accessible to screen readers, the attribute “aria-label” must be used instead.
To clarify, do you mean that the issues with numbers not listed in the backlog list and that are not yet addressed will be included in the next minor release?
We are excited to see these changes in Flexmonster and grateful for your commitment to meeting WCAG 2.1 standards.
Best,
Erin
⋅ March 11, 2025
Hi Erin,
Thank you for the feedback!
Our team will add the “aria-label” attribute to the element in our minor release with the ETA March 17th.
You are correct that not listed in the backlog improvements will be included in the next minor releases. Our team will keep you notified of further updates.
Do not hesitate to contact us if other questions arise.
Kind regards,
Nadia
⋅ March 17, 2025
Hello Erin,
We are happy to inform you that the accessibility fixes were added for the following issues:
These fixes are provided in the 2.9.98 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-98/
You are welcome to update the component. Check out our updating tutorial for guidance: https://www.flexmonster.com/doc/updating-to-the-latest-version/.
Improvements not listed in the backlog will be included in the next minor release, which has an ETA of March 31st. We will notify you about the update.
Please let us know if it works for you. Looking forward to hearing your feedback.
Kind regards,
Nadia
⋅ March 27, 2025
Hi Nadia,
I appreciate the update! Our team will review the issues after the March 31st release to verify they have been addressed.
Thank you,
Erin
⋅ 3 days ago
Hi Erin,
We are glad to announce that the following accessibility improvements were released:
button role was added to header cells with measure names.These fixes are included in the 2.9.100 version of Flexmonster: https://www.flexmonster.com/release-notes/version-2-9-100/.
Please note that if you are using Flexmonster via npm, the correct version is 2.9.100-1.
You are welcome to update the component. Here is our updating guide for assistance: https://www.flexmonster.com/doc/updating-to-the-latest-version/
Please let us know if they work for you. Looking forward to hearing from you.
Kind regards,
Nadia