See also: IRC log
<shadi> https://www.w3.org/2002/09/wbs/93339/availability/
wilco: There were a couple of responses on the ACT Framework Requirements reviews.
Charu: Thinks it looks clear and crisp and everyone has captured the points.
wilco: Mary Jo and Jemma made comments. Updates have been made and will check with Jemma to make sure the updates address her comments.
Shadi: Will work on some editorial changes, but nothing substantive.
Wilco: We are pretty well on schedule and will try to get approval to send it off to the WCAG working group in about a week once the editorial edits are complete.
Shadi: Today we should give the WCAG WG chairs a heads-up that we plan to send to them next week or give them a date when we want approval so they can plan.
Wilco: Next thing to work on is the first
draft.
... First draft of the spec typically starts of with an empty draft or
template with the chapters or an outline defined.
Shadi: In the skeleton document, also add
editor notes for each section to show the thoughts of the editor on the
contents of each section.
... We are trying to find additional people to get involved and help
with our TF work.
<scribe> scribe: maryjom
<Wilco> https://github.com/auto-wcag/auto-wcag/blob/master/_rules/SC1-1-1-aria-describedby.md
shadi: ARIA 1.1 had an aria-describedby (one of the test ruled developed by auto-wcag) which had automatic steps and semi-automatic steps. Some tests are non-trivial and more sophisticated. We can use it as an example to start with so TF members know what kinds of things should be addressed.
<shadi> https://www.w3.org/community/auto-wcag/wiki/Test_template
Shadi: The above link is a description of the format and template
wilco: The above link is an updated version of the template.
shadi: This template could be an appendix
in the spec or a side-document that goes with the spec. Every part of
the template will need a description of the expected format, such as the
format of the date and so forth.
... In the description there should be some specific points included,
such as the specific part of the WCAG specification. It should also
include the functional requirements for clarity, etc.
wilco: Not sure how you would reference the criteria. There's more to it than simply the WCAG SC. It may be applicable to multiple standards.
shadi: Would have to check how EARL handles that.
charu: We have all of the programmatic rules, but we don't have an verbal description of all of the rules.
shadi: One requirement we have is to try to be as open as possible so people can easily port and not make a lot of changes to their own rules.
charu: Can provide a generic description for how our rules are written
wilco: Can also do that for AXE so we can compare notes.
<Wilco> ACTION: Wilco to create a plain English description of axe rule structure [recorded in http://www.w3.org/2016/10/19-wcag-act-minutes.html#action01]
<trackbot> Created ACTION-8 - Create a plain english description of axe rule structure [on Wilco Fiers - due 2016-10-26].
<cpandhi> ACTION: Charu to create a plain English description of DAP rule structure [recorded in http://www.w3.org/2016/10/19-wcag-act-minutes.html#action02]
<trackbot> Created ACTION-9 - Create a plain english description of dap rule structure [on Charu Pandhi - due 2016-10-26].
shadi: There is typically a status of this document section at the beginning of a draft where we communicate with the reader that this is a first draft outline and we are looking for other formats as an editor note in the introduction.
wilco: EPUB rules work has not been started.
<Wilco> https://lists.w3.org/Archives/Public/public-wcag-act/2016Oct/0017.html
wilco: Gemma sent us the above note (see
link) on the Open Ajax Alliance ruleset. It doesn't have information on
the specific procedure.
... It also has some things that we don't have listed in our auto-wcag
rules.
... Element or page level information doesn't exist in auto-wcag rules.
shadi: The results are also different.
wilco: The unique thing about auto-wcag descriptions is that it is only a procedural desription which was something that caused fairly complex test procedures which Alistair had commented on.
<rdeltour> the tools are respec or bikeshed
<Wilco> https://www.w3.org/WAI/GL/task-forces/conformance-testing/track/actions/open
shadi: Above tools will help in the development of the draft spec.
<shadi> https://www.w3.org/Guide/
Charu: Action 4 on reviewing Alistair's input is still in progress.