Hi there,
So I've been doing some testing and it seems to me that this could be an issue further down (like the HTMLCS.js), but I wanted to get your take on it and see if this issue is something you have seen. Appreciate taking the time to review and respond.
I was interested in the data coming out in the CLI version of the tool, as a result I noticed that it doesn't really give us details, only a summary. So after a little poking around, I added some code to the sanitizeMessages() function in handle-result.js ( see attached screenshot ), that essentially converts the message to a string and add's it to the 'raw" property of the returned message object.
I did this so I could look at the data coming back and see if we could add a verbose function here to give instance specific details of each reported error in the CLI
I then added a custom reporter:
This reporter is essentially the standard reporter, but if there is multiple messages, and the message is different from the first, it outputs the raw data attribute which my last screen shot shows.
So the reason for this, is some messages are very vague and cryptic in the CLI, like the error in the output:
{ code: 'WCAG2AAA.Principle1.Guideline1_3.1_3_1.H44.1.Before',
element: null,
msg: 'The label element for this control should be placed before this element.',
type: 1 }
It's great that I should place a label control in front, but which element is it referring too?
Other examples include when it suggests I should change the contrast color on an element...suggests the new value, but I'm not sure what element it was referencing, since the output didn't include it.
Any reason why, or had you encountered this case already where the data in the messages are actually empty?