Marek Lewandowski

Failed assessment provides some nice information in `info` property, that might be used in a Quick Fix.

# General While analysing [G140](https://github.com/cksource/quail-enhancement/blob/master/G140.md) I thought about a feature that would allow easily preview the content without any style at all. The purpose is that content author will have...

We should disable (or hide) navigation buttons when there is only one issue found. Based on AC feedback: > When I had only one issue, I could still click on...

We should include a link to more information about the problem if possible. E.g. facing a failure F89 should result with adding a link to [F89 at WCAG2](http://www.w3.org/TR/WCAG-TECHS/F89.html).

Checking engine for each test should ask ACF if tested elements are allowed by the ACF. ## Sample Case E.g. Imagine that we have a test for Techinque [H49: Using...

We need to cleanup the code after #106 - it was a quick fix without testing just to make AC more resistant to Quail results.

Developer docs

7

We need to think about dev docs - how do we want generate them etc. Because we're unlikely to publish API docs inside [CKEditor API](http://docs.ckeditor.com/#!/api) docs.

This issue is reminder rather than task. We're interested if IE8 will be supported by Quail. Issue was already reported as quailjs/quail#287.

Quail issues during a full check

2

Quail seems to hang when we'll use all of its tests to check our sample. We need to investigate what's the reason for that. **Update**: It seems that Quail simply...

Provide a subtle highlight also in listening mode

8

# Overview Actually I came with that idea while working on #27. We might leave subtle highlight for issue elements in listening mode. That will allow end users to have...