Should there be (a11y) commit type? How do you address accessibility UI related changes? #202

New Issue

GiteaMirror · 2026-02-17T11:53:19-06:00

GiteaMirror commented

2026-02-17 11:53:19 -06:00

Originally created by @webmatrixxxl on GitHub (Mar 15, 2024).

Hello!

In the Front-End world recently because of the European Accessibility Act, we have been required (for good) to implement a lot of accessibility across components and pages.

And I started wondering how we should address accessibility in the commit messages.

a11y(checkout): add alt text to card types in checkout

or

accessibility(checkout): add alt text to card types in checkout

or we can stick to

feat(checkout): add alt text to card types in checkout

or maybe

chore(checkout): add alt text to card types in checkout

Personally, I kind of prefer the first one. I'm thinking about the feat and fix in the scope of functionality and accessibility is on top of that.

I have seen this in another project as well: link

What do you think?

Originally created by @webmatrixxxl on GitHub (Mar 15, 2024). Hello! In the Front-End world recently because of the European Accessibility Act, we have been required (for good) to implement a lot of accessibility across components and pages. And I started wondering how we should address accessibility in the commit messages. ` a11y(checkout): add alt text to card types in checkout ` or ` accessibility(checkout): add alt text to card types in checkout ` or we can stick to ` feat(checkout): add alt text to card types in checkout ` or maybe ` chore(checkout): add alt text to card types in checkout ` **Personally, I kind of prefer the first one.** I'm thinking about the `feat` and `fix` in the scope of functionality and accessibility is on top of that. I have seen this in another project as well: [link](https://gist.github.com/rishavpandey43/84665ffe3cea76400d8e5a1ad7133a79 ) What do you think?

GiteaMirror commented

2026-02-17 11:53:20 -06:00

@henrikhelmers commented on GitHub (Mar 26, 2024):

On the one hand, accessibility should be part of code quality (be it by adding alt text or correctly implementing design), which would make "chore" correct.

On the other hand it would be valuable to be able to point at commits related to accessibility to document effort in that area. I also belive that as the amount of awareness (and legislation) increase, the amount of commits directly related to accessibility will as well.

@henrikhelmers commented on GitHub (Mar 26, 2024): On the one hand, accessibility should be part of code quality (be it by adding alt text or correctly implementing design), which would make "chore" correct. On the other hand it would be valuable to be able to point at commits related to accessibility to document effort in that area. I also belive that as the amount of awareness (and legislation) increase, the amount of commits directly related to accessibility will as well.

GiteaMirror commented

2026-02-17 11:53:21 -06:00

@gekoke commented on GitHub (Jul 24, 2025):

chore(a11y):

@gekoke commented on GitHub (Jul 24, 2025): `chore(a11y):`

GiteaMirror referenced this issue

2026-02-17 12:00:20 -06:00

[PR #202] [MERGED] fix: 'ci:' type markdown syntax #355

Sign in to join this conversation.