Closed jaimeiniesta closed 7 years ago
That is not a bug; those are for our internal software. You can disregard those tags.
@jaimeiniesta you could also use the tags yourself. They are simply categories into which the different rules belong so that you can sort the issues by category. It should be quite straightforward to understand what these categories mean.
If you want to submit a documentation PR to document these that would be appreciated because we had not planned to do that in the short term.
@dylanb I see that these cat.*
tags are not being shown on the results by the Chrome extension:
But if I check the raw results by axe-core I do see they're included (cat.forms
) in this case.
So to keep our Rocket Validator integration in tune with the Chrome extension, I think it will be best to hide the cat.*
tags by now.
I would document this but I'm not sure I fully understand the topic :) I mean, if as @marcysutton says these are only used for your internal software, then it's OK to not document them, I guess.
@jaimeiniesta They aren't in there yet because we haven't updated the extensions yet. I think Marcy is doing that this week.
@WilcoFiers, ah, cool, then they don't need to be hidden, they're going to be public. Then yes, we do need to document what they are :)
axe https://decide.madrid.es/participatory_budget --save decide.json
Will return the following JSON:
Is it a bug that
cat.text-alternatives
andcat.language
are being included in the tags? I thought the tags would only refer to the rules being applied.