Minutes for Teleconference on 23 April 2015

Automated WCAG Monitoring Community Group
Teleconference 2015-04-23, 16:00 - 16:50 h (CET)

Participants: Annika, Birkir, Frank (scribe), Kamyar, Twan, Wilco (chair)

ITEM 1: Action items
See updated list in the wiki [1].

ITEM 2:  Auto-WCAG Workshop
Birkir: Decision still pending.
Kamyar: Will participate online.

ITEM 3: Review SC1-1-1-text-alternative [2]
One more typo. Test case status changed to Completed.

ITEM 4: Review SC1-4-2-audio-control-audio [3]
Twan has already adressed most comments.
Annika: Suggest to add a manual step for checking, if video elements are 
actually playing audio.
Twan: Should be possible automatically.
Wilco: Are methods to check for audio output in scope? What's about
sources of audio outside of the browser?

Wilco: An automatic check that audio is playing can only be done outside 
of the browser. This is beyond the scope of auto-wcag.

Annika: Better to do it manually.
Decision: Add manual step between 4 and 5.

ITEM 5: Review SC2-4-5-multiple-ways [4]
Annika: In step 5 it's checked for G185, which requires links from 
webpages to the the homepage and frome the homepage to all pages on the 
site. Suggest to add an assumption that G185 is not checked, because it 
only applies to very small sites.
Wilco: A site with 5 pages would pass in steps 2 and 3.
Annika: If a menu fulfills step 2 and also 3, this is not meant by 
"multiple ways". Cites example from G185: "A small commercial Web site 
for a consultant contains a home page, a Contacts page for contacting 
the consultant, a page describing the consultant's background, and a 
page with examples of the consultant's work. Each page contains a 
navigation bar that links to all the other pages in the site." [5]
Wilco: Whats about a different division of steps?
Birkir: Sitemaps are a quite outdated concept. Couldn't we compare links 
to other pages on the site? If they are consistent on multiple pages, 
it's a sitemap-like navigation.
Annika: We could use the algorithm from SC3.2.3.
Wilco: We should search for main navigation utilizing 3.2.3 and a search 
field, which is a form with a text field and search button.
Birkir: Maybe we can benefit from an automation of 2.4.5.
Wilco: text field and button can be assumed to be a search field. Twan? 
Is implementation feasible in time?
Twan: Yes, should be possible within 2 weeks.
Wilco: done.

ITEM 6: Final thoughts
Wilco: We got a comment on the blog post. Does anybody know someone 
behind tenon.io? We should try to contact them, as their work is related 
to AutoWCAG.
Birkir: Yes. I know Karl. Can contact him.

Birkir: Google hangouts provide decent accessibility features.
Frank: Hangouts need activation of Google plus on the account used, as 
they are a Google plus app.

Next week we will give Hangouts another try.

REFERENCES:
[1] 
https://www.w3.org/community/auto-wcag/wiki/index.php?title=Action_items&oldid=1497
[2] 
https://www.w3.org/community/auto-wcag/wiki/index.php?title=SC1-1-1-text-alternative&oldid=1489
[3] 
https://www.w3.org/community/auto-wcag/wiki/index.php?title=SC1-4-2-audio-control-audio&oldid=1487
[4] 
https://www.w3.org/community/auto-wcag/wiki/index.php?title=SC2-4-5-multiple-ways&oldid=1484
[5] http://www.w3.org/WAI/GL/2015/WD-WCAG20-TECHS-20150106/G185

SUMMARY OF ACTIONS:
https://www.w3.org/community/auto-wcag/wiki/index.php?title=Action_items&oldid=1423

Received on Friday, 24 April 2015 08:27:19 UTC