Hello, we are looking at moving our support system to use Zammad, and as such are going through some tests. Most issues are manageable, but there are some quite important accessibility issues we have come across to resolve.
Can I propose that a new category of “Accessibility” is created on the community board, and that as we find things we create issues to hopefully help resolve things and get things back into Zammad core. In most cases these may include our workarounds which hopefully can get removed once Zammad becomes more accessible. We are happy to patch or do this in whatever format is preferred.
If not a category, then what would be a better approach to getting these logged in a useful manner (maybe a tag for accessibility instead)?
I think that could work, I am probably going to create a set of ticket (6-12 at first), most with proposed ideas on there with code.
The only issue with tags may be my misunderstanding of this forum, I cannot see how to attach a tag to a post, does someone else have to come in and tag them, or can I do it with some html in the body?
Sadly that doesn’t appear to have worked either, and looking at Disourse posts elsewhere, I think only admins can create tags, and also there is a “post edit” option, which may have also been disabled for non-admins on this forum.
Once we have this tagging, I will create some tickets with feature requests. I just don’t want to create them first in case we need to delete and recreate the tickets after we know how tags work.
We use tagging of posts for feature requests, generally for nothing else. Even though it’s not forbidden to use them on other parts. Right now I don’t understand how this tag will help you, if you’re not going to create feature requests.
We generally have an issue on this open already (zammad barrier-free? (WCAG 2.0 AA) · Issue #3067 · zammad/zammad · GitHub ), it is part of the UI rewrite to the new tech stack and thus will take time. Personally, I wouldn’t waste time on the old tech stack / view we have in place now, as it’s unlikely it will get love on that regard.
@MrGeneration Sorry, I think there is a misunderstanding, I was intending to create feature requests, I was just holding back as didn’t want to flood the board if I should be tagging appropriately.
Personally, I wouldn’t waste time on the old tech stack / view we have in place now, as it’s unlikely it will get love on that regard.
I am not sure this is an options for us, as accessibility can be quite a serious barrier to usage for people, and the new frontend build having accessible appears slow and with no deadline as yet.
We have patches and workarounds, so will just assume we need to have those for now. I will create feature requests anyway though for them later this week, and try to include the [WCAG] in the title, as feel that may help you with tagging them.
