-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow for customization of aria-labels added with plugin #19
Comments
@gnarlyskigirl I think that is very possible. Thanks for the feature request. |
How can I help? I’d love to get involved. I’m so glad you have created this plugin!
From: Alex Stine <[email protected]>
Sent: Thursday, July 26, 2018 11:16 AM
To: campuspress/divi-accessibility <[email protected]>
Cc: Cindy Conlin <[email protected]>; Mention <[email protected]>
Subject: Re: [campuspress/divi-accessibility] Allow for customization of aria-labels added with plugin (#19)
@gnarlyskigirl<https://github.com/gnarlyskigirl> I think that is very possible. Thanks for the feature request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#19 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AE3NNNQphmw_NO8XU1nNo4GBXVZl6oSjks5uKd0agaJpZM4ViAnJ>.
|
@gnarlyskigirl Pull requests and feature requests are always welcome. The plugin was needed for our Divi themes on https://edublogs.org and https://campuspress.com. The code was already created, making it public was just a good way to give back to the community. |
Hi everyone! Has there been a fix/workaround for this please? How can we help? |
I no longer work for Incsub. CC: @vladislavbailovic to take ownership. |
The plugin adds predefined aria-labels required for accessibility, but the text is also predetermined and not necessarily descriptive.
Example: area-label="Wide Header0"
It would improve accessibility if we could customize the text of the aria-labels added with this plugin. Can we add a field to configure the label text to be more descriptive in the next release?
The text was updated successfully, but these errors were encountered: