Meeting Minutes 2015-03-12

Automated WCAG Monitoring Community Group
Teleconference 2015-03-12, 16:00 - 17:00 h (CET)

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

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

Annika: Birkir added a new test [2]

Wilco: What is new on the website templates?

Annika: I have been in touch to add Twitter link and will see what is the
email address.

Wilco: And I have a draft of the proposed blog post, does anyone want to
review?

Twan: Will contact team-community-process@w3.org to see how to get posted.

Wilco: I had a look at 3.2.3 [3] and made a few minor changes. Annika, your
comments?

Annika: First was about the wording of the selector, I think it needs to be
a more formal reference. Then I was looking at a scenario where menu items
are the same but have different locations on different pages.  Currently it
would be a pass but I think that is not correct.

Wilco: But since it conforms to a consistent order of presentation, it my
opinion it is good, it should pass.

Sharron: While that makes sense from a logical standpoint and for AT
devices that read in code order, the reality is that for people with low
vision using magnification and those with cognitive issues - the change of
layout is a barrier. I agree with Annika.


Wilco: looking at text of the SC, it refers to the order of navigation
elements.


Annika: The list may be in the same order, but what about the entire page
content, something different might now be at the top. ...so the case where
navigation is on a completely different section in different pages may be a
fail according to G61[


Wilco: I think that aspect may need to be covered in a different test case.

Annika: These are the relevant passages: 2. For each component, check that
it appears in the same relative order with regard to other repeated
components on each Web page where it appears. 3.For each navigational
component, check that the links or programmatic references are always in
the same relative order. So the concept is applied in two ways. The
relative order of individual component as well as within page context.

Wilco: Will you take on the test case Annika?


Annika: OK I will put at the bottom of my list.


Wilco: There is the next open comment from Frank.


Frank: I am wondering about the alignment of step 1 and step 2?


Wilco: Did it seem to be sufficiently explained?


Frank: Not really, I had big misunderstanding and think this may need
better explanation. Maybe big lists would be sufficient and that we may
need to check for relative position on page. I will give this more thought
and may come up with a suggested solution.


Wilco: OK we will keep open for another round of review.


Frank:  That would be good.


Wilco: Looking at the test case for SC 1.1.1 [5] it seems there are
assumptions that sibling elements are the only way to group elements. That
may not be necessary.

Frank: For example, elements wrapped in other elements?

Wilco: Yes and we should consider including in the test case the fact that
an image gets empty alt text when adjacent text is serving as alt.


Wilco: There was also your comment Frank, wondering about relationship of
13 to step 14. Are you suggesting to combine them?


Frank: yes


Wilcon: And in step 15, does x sufficiently describe element where x is
replaced with whatever is being offered as text alternative. It has been
suggested to exclude longdesc from this test case, since it is included
elsewhere


Kamyar: I wanted to ask about step 4, what about the test in G196? should
it be included?


Frank: And should step 10 include a separate test for placeholders (failure
49)


Annika: Since 13 and 14 will be merged it may address that.

Wilco: Every output should have a distinguishing identifier


Frank: OK and I will also add in step 10


Wilco: Really good work here Frank, anyone have closing remarks?


[1] https://www.w3.org/community/auto-wcag/wiki/Action_items

[2]
https://www.w3.org/community/auto-wcag/wiki/2.4.4_Link_Purpose_%28In_Context%29
[3]
https://www.w3.org/community/auto-wcag/wiki/SC3-2-3-navigational-links-across-pages

[4] http://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140408/G61

[5] https://www.w3.org/community/auto-wcag/wiki/SC1-1-1-text-alternative

[6] https://www.w3.org/community/auto-wcag/wiki/SC3-1-1-text