W3C home > Mailing lists > Public > public-silver@w3.org > May 2020

Re: Scoring and Dashboards

From: jake abma <jake.abma@gmail.com>
Date: Tue, 12 May 2020 10:00:50 +0200
Message-ID: <CAMpCG4HjV3YFZsFHz-LRSA22V4-qmaU-O2021idVB0hPV-mLOg@mail.gmail.com>
To: John Foliot <john.foliot@deque.com>
Cc: Silver TF <public-silver@w3.org>, WCAG <w3c-wai-gl@w3.org>
Ow, and we're not the body to judge about when something "deteriorate".

If at all, that is up to the tester / auditor OR if wished up to the
dashboard maker / settings.

Op di 12 mei 2020 om 09:58 schreef jake abma <jake.abma@gmail.com>:

> I don't see any issues here by adding dates / time stamps to a conformance
> claim.
>
> - First of all for the specific conformance claim / report
> - If other reports are included with another time stamp, mention it (also
> the time stamp and which part it is)
> - The responsibility is up to the "conformance claimer" if he chooses a
> report to include but didn't check if it's still actual.
>
> We only provide guidance for how to test and score and ask for time stamps.
>
> How a tool vendor places it in a dashboard is totally up to the tool
> vendor.
>
> Cheers!
> Jake
>
>
>
>
>
> Op ma 11 mei 2020 om 18:10 schreef John Foliot <john.foliot@deque.com>:
>
>> Hi All,
>>
>> During our calls last week, the use-case of monitoring conformance
>> dashboards was raised.
>>
>> One important need for *on-going score calculation* will be for usage in
>> these scenarios. After a bit of research, it appears that many different
>> accessibility conformance tools are today offering this
>> feature/functionality already.
>>
>> Please see:
>>
>>
>> https://docs.google.com/document/d/1PgmVS0s8_klxvV2ImZS1GRXHwUgKkoXQ1_y6RBMIZQw/edit?usp=sharing
>>
>> ...for examples that I was able to track down. (Note, some examples today
>> remain at the page level - for example Google Lighthouse - whereas other
>> tools are offering composite or aggregated views of 'sites' of at least
>> 'directories' [sic].)
>>
>> It is in scenarios like this that I question the 'depreciation' of
>> user-testing scores over time (in the same way that new cars depreciate
>> when you drive them off the lot, and continue to do so over the life of the
>> vehicle).
>>
>> Large organizations are going to want up-to-date dashboards, which
>> mechanical testing can facilitate quickly, but the more complex and
>> labor-intensive tests will be run infrequently over the life-cycle of a
>> site or web-content, and I assert that this infrequency will have an impact
>> on the 'score': user-test data that is 36 months old will likely be 'dated'
>> over that time-period, and in fact may no longer be accurate.
>>
>> Our scoring mechanism will need to address that situation.
>>
>> JF
>> --
>> *John Foliot* | Principal Accessibility Strategist | W3C AC
>> Representative
>> Deque Systems - Accessibility for Good
>> deque.com
>> "I made this so long because I did not have time to make it shorter." -
>> Pascal
>>
>>
>>
>>
Received on Tuesday, 12 May 2020 08:01:16 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 12 May 2020 08:01:17 UTC