Re: a11y tag in bug tracking system?
Mario Lang, le Mon 17 Mar 2008 09:19:29 +0100, a écrit :
> Samuel Thibault <firstname.lastname@example.org> writes:
> > On my FOSDEM slides, I mentioned the idea of adding an "a11y" tag to
> > bugs, just like there is already an l10n tag. That would probably help
> > tracking bugs like #380612 (colorblind support in crack-attack), and
> > maybe they could be automatically forwarded to the debian-accessibility
> > list to help triggering discussions?
> One problem I see is that submitters will usually not know they are
> supposed to use the a11y tag.
I also wondered about that, but reportbug is indicative about it: for
instance, for l10n, it says
1 l10n This bug reports a localization/internationalization issue.
We could have a similar description for a11y.
> But if they do, why not. AIUI, tags can just be used and do not
> have to be specially created, but I might be wrong. Did you already
> investigate this?
bts tags refuses to add "a11y", so I guess there is an official list.
> I hope this doesn't lead to: "Oh, this is an a11y bug, I dont
> need to care about this."
> Most real accessibility issues will be bugs against upstream anyway, I
> wonder if it makes much sense to load the Debian BTS up with stuff the
> maintainer would need to forward...
Well, the problem is that in general it is often not so easy to find
the upstream contact, and thus even less for disabled people, who would
be glad to be able to just use reportbug. By tagging a11y, maybe that
would mark them as "don't care" for some maintainers indeed, but that
may mark them as "do care" for others, like those who recently joined
the list after my FOSDEM talk for instance ;) and who could do the work
of reporting upstream, etc. Just like the l10n tag actually.