Alt text generator module generates alt text for images using AI. You can choose language of alt text generation from the configuration dashboard of the module.
To test it, please follow the steps below:
1. Install module
2. Access the settings page at /admin/config/content/alt-text-generator to choose the language for alt text and add the API key for alt text generation. A button will then appear on image fields for generating alt texts.
3. You can use this API key for testing: b2MY5gAj4WcaFn8RU1itRWeRHej1
Project link
| Comment | File | Size | Author |
|---|---|---|---|
| Screenshot 2025-07-08 at 4.37.47 PM.png | 62.33 KB | balt1794 | |
| Screenshot 2025-07-08 at 8.46.49 PM.png | 171.38 KB | balt1794 |
Issue fork projectapplications-3534979
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
vishal.kadamComment #3
avpadernoThank you for applying!
Please read Review process for security advisory coverage: What to expect for more details and Security advisory coverage application checklist to understand what reviewers look for. Tips for ensuring a smooth review gives some hints for a smoother review.
The important notes are the following.
To the reviewers
Please read How to review security advisory coverage applications, Application workflow, What to cover in an application review, and Tools to use for reviews.
The important notes are the following.
For new reviewers, I would also suggest to first read In which way the issue queue for coverage applications is different from other project queues.
Comment #4
vishal.kadam1. FILE: alt_text_generator.info.yml
core_version_requirement: ^9 || ^10 || ^11FILE: composer.json
A new project should not declare itself compatible with a Drupal release that is no longer supported. No site should be using Drupal 8 nor Drupal 9, and people should not be encouraged to use those Drupal releases.
2. FILE: alt_text_generator.libraries.yml
version: VERSIONVERSION is only used by Drupal core modules. Contributed modules should use a literal string that does not change with the Drupal core version a site is using.
Comment #5
balt1794 commentedThank you for the review. I've addressed the issues in version 1.0.2:
1. Removed Drupal 9 support from both info.yml and composer.json as it's no longer supported
2. Updated VERSION placeholder in libraries.yml to use literal version string '1.0.2'
These changes have been committed and released in version 1.0.2.
Comment #6
balt1794 commentedThank you for the review. I've addressed the issues in version 1.0.2:
1. Removed Drupal 9 support from both info.yml and composer.json as it's no longer supported
2. Updated VERSION placeholder in libraries.yml to use literal version string '1.0.2'
These changes have been committed and released in version 1.0.2.
Comment #7
vishal.kadamAs a side note: These applications do not require that new releases are created after reviews.
Rest looks fine to me.
Please wait for a Project Moderator to take a look and if everything goes fine, you will get the role.
Comment #8
avpadernoTruly, this application should wait for other reviewers.
Comment #9
bbu23It seems to me that this module contains too few code to be able to properly review.
Though, as a quick look, the config/install folder with the default module settings file is missing.
In README.md and composer.json, there are strings like "[Your Name] - https://www.drupal.org/u/[your-drupal-username]" which need replacing.
Comment #10
bbu23Comment #11
balt1794 commentedI've fixed the issues mentioned. Please review now.
Thanks!
Comment #12
balt1794 commentedComment #13
bbu23Updating priority according to issue priorities.
Comment #14
balt1794 commentedThis is ready for review
Comment #15
vishal.kadamThere are phpcs errors in the code. Please enable GitLab CI for the project, and fix what reported from the phpcs job.
Comment #16
avpadernoIf there are PHP_CodeSniffer errors/warnings, the review should at least say which ones they are.
Comment #17
avpadernosrc/Controller/AltTextGeneratorController.php
Since that class does not use methods from the parent class, it does not need to use
ControllerBaseas parent class. Controllers do not need to have a parent class; as long as they implement\Drupal\Core\DependencyInjection\ContainerInjectionInterface, they are fine.alt_text_generator.module
For a new module that aims to be compatible with Drupal 10 and Drupal 11, I would rather implement hooks as class methods as described in Support for object oriented hook implementations using autowired services.
It would require increasing the minimum Drupal 10 version supported, but Drupal 10.1 is no longer supported.
Comment #18
vishal.kadamFix phpcs issues.
Note: It is better to enable GitLab CI for the project and fix the PHP_CodeSniffer errors/warnings it reports.
Comment #19
vishal.kadamI am changing priority as per Issue priorities.
Comment #20
avpadernoThis thread has been idle, in the needs work state with no activity for some months.
May you confirm you are still pursuing this application? If this is the case, and you made commits basing on what previously reported, or you can answer the questions previously asked, please change the status to Needs review.
Comment #21
avpadernoThis thread has been idle, in the Needs work state with no activity for about six months or more; the application has been created about 11 months ago or more. Therefore, I marked it as Closed (won't fix).
If this is incorrect, and you are still pursuing this application, please feel free to re-open it and set the issue status to Needs work or Needs review, depending on the current status of your code.