anzelkiel → created an issue.
Hello, I was planning to work on the development this month and next month. With my job, I’m doing this in my free time, which is unfortunately quite limited. Should we wait before approving the application, or can the changes be made later on?
ok thanks
compatibility with Drupal 10 and 11. I will add more accessibility features later on.
I should delete the a11y directory if I understand correctly?
Points 2, 3, and 4 are now fixed.
change done
Hello, I have now fixed the indicated errors, and the pipelines for composer-lint, cspell, eslint, phpcs, phpstan, and stylelint are all OK.
I have also addressed the feedback provided in the comments. Everything is available in the 1.1.x branch. Is this good to go now? Should I create a 1.1.0 branch?
Thank you for your feedback and responses!
Thank you for republishing it. I don’t understand why it was unpublished either. I also didn’t see the option to publish it myself, so ... Thank you.
I’ll take note of the procedure in case this happens again.
I’m now waiting for security advisory coverage application’s approval.
anzelkiel → created an issue.
Thank you for the responses. I duplicated the project: https://www.drupal.org/project/accesstools → . Currently, the project is private; I’m not quite sure why, probably pending validation. I’m also waiting for it to be covered by the security advisory policy.
anzelkiel → created an issue.
anzelkiel → created an issue.