<scribe> scribe: Wilco

JYM: Carlos sent us results from Knowbility
... The output is very compact. There isn't always an indication of what page had the problem, and what the problem was.
... It's not very granular, but it's a start. The site version seems to have been frozen.
... The data is in Excel, we'd need to extras the information.

Daniel: Carlos, Sharron and I discussed this last week.

JYM: Maybe next step would be to turn this sheet into something programmatic, or to start running tools against the websites.

Wilco: Should we start by storing the pages?

<dmontalvo> Wilco: We may want to secure the websites, storing them somewhere

JYM: I'm not sure how to archive. Scripting is not part of the archive format.

Andrew: Is it reliable to use the way-back machine?

JYM: Web archive doesn't archive each page every day. If they only get archived once a year we might not get the version we want.

Wilco: I think you can ask web archive to tell it to store a page.

JYM: The other way is we could save the page in a web archive format. But this does not grab the scripts.

Helen: Should we take some examples and see if we can get those from the internet archive?

JYM: Seems you can let way-back machine save URLs

Daniel: Even though we can save specific dates, how much of the work would be impacted by us not having all the assets?

Jean-Yves. The main problem would be to track the evolution of our ruleset.

scribe: Manual testing is costly. If we run an automated test on a version that is different comparing results does not make sense.
... For an initial exploration, we don't really need to archive. We have manual tests from November, we do what comparison we have. I think that's alright for a first try.
... So should we from the report try to extract which criteria are failing on different sites.
... OK I'll try to do that for one or two and share the results.
... Putting this into WCAG-EM gives us a format we know. I'll do that.
... Then we can try to run the tools.

Andrew: I'm happy to reach out to WebAIM about their million pages data.

JYM: Could someone explore way back, look at how to solve storing challenges

Andrew: There are a few others to consider.

JYM: I was able to capture something.
... I'm getting some dynamic data too.

Daniel: I haven't written the e-mail for WAI-IG yet.

JYM: Maybe we don't need to reach out until we have a more refined process.

Daniel: That's my understanding,

JYM: It's a good idea to have something to showcase. That might make it easier to to get people to share some data.

Daniel: It's not just about people giving us their data. It's a shared effort.

JYM: We'll meet back in 2 weeks.

This is scribe.perl Revision VERSION of 2020-12-31
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/page/pages/
Default Present: (no one)
Present: (no one)

WARNING: Fewer than 3 people found for Present list!

Found Scribe: Wilco
Inferring ScribeNick: Wilco

WARNING: No "Topic:" lines found.


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)