Meta - accessibility issues

[saghul]

#5992
#5852
#5817
#5789
#5739
#5681
#5308
#3590
#6089

[mgifford]

It seems like there should be an accessibility label that could be used to aggregate these issues in the future. We know that there are going to be more issues.

[missmatsuko]

Should those issues be closed or not? I thought they should stay open until they're actually resolved.

[luixxiul]

I would agree with @missmatsuko; only duplicates should be closed.

[l3d00m]

Just discussed it, closing this issue as we used it basically as a label. This has now been replaced by adding a accessibility label to any issues in question. They have been reopened @missmatsuko. Sorry for any confusions caused!

[Echolon]

But let us keep this issue pinned, because people hopefully address existing issues first.

[l3d00m]

I disagree, nobody will look through a closed pinned issue that only contains the issue numbers. It's much easier to use the search for it. I'd also say that that logic could apply to any issue, not just accessibility, as they aren't really different.

[skolmer]

This one fixes a lot of accessibility issues related to outdated atlaskit components: #8423

[skolmer]

This will fix the rest of the accessibility issues in jitsi-meet web #8921