Skip to content
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

Idea to enforce the use of alt attributes #496

Open
robdekort opened this issue Mar 24, 2021 · 3 comments
Open

Idea to enforce the use of alt attributes #496

robdekort opened this issue Mar 24, 2021 · 3 comments

Comments

@robdekort
Copy link

Clients rarely add ALT attributes. Now there are drastic tricks like not showing the image if it doesn't have an alt text, but maybe we can be try to enforce it in the asset browser.

I was a small tweak first. How about a column Alt text with a green checkmark if you got it, and a red cross if you don't.

This could be extend to the appearance of the asset field.

@stefankempf
Copy link

I would also have two other suggestions:

  1. show an input field during initial upload, where the alt text can be stored. Then at least, the user sees the alt text input once.
  2. have an option to make an alt text required. If a user tries to publish an article containing images without alt text, show an error warning (for example: "alt text not set") like the usual required warning. Maybe add a link to open the image detail stack, where the alt text can be set.

@andjsch
Copy link

andjsch commented Apr 11, 2022

Totally agree. In the mean time you could take a look at the widget from the Peak starter kit. It shows all the images that don't have an alt text yet.

@Alpenverein
Copy link

We are running in simular problems aswell.. We use different required fields in our assets' blueprint. While required fields are not validated during upload the image was available to users even without copyright or legal information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants