Evaluators may complete only some of the test book sections. There may be multiple tests of the same reading system using different AT. This leads to a very cluttered and confusing results table.
The results for a reading system can be consolidated into a single row. At its simplest, the results for [basic and non visual] can be together with [visual adjustments and read aloud].
If there are multiple test results, they can be presented as a range, e.g. 54%-67%.
For native apps the row would be different for each OS (so, Kortext on Android, then Kortext on iOS).
For browser based reading systems, the row would be different for each browser (so, Redshelf via Chrome, Redshelf via Firefox).
It should be possible to drill down to the individual tests from the table.
Evaluators may complete only some of the test book sections. There may be multiple tests of the same reading system using different AT. This leads to a very cluttered and confusing results table.
The results for a reading system can be consolidated into a single row. At its simplest, the results for [basic and non visual] can be together with [visual adjustments and read aloud].
If there are multiple test results, they can be presented as a range, e.g. 54%-67%.
For native apps the row would be different for each OS (so, Kortext on Android, then Kortext on iOS).
For browser based reading systems, the row would be different for each browser (so, Redshelf via Chrome, Redshelf via Firefox).
It should be possible to drill down to the individual tests from the table.