Meeting minutes
Where we are now
<jtoles> https://
<julierawe> https://
julierawe walked us through some history about how AG activities wrapped the year by wrapping all the Guidelines Test feedback into the upcoming 3.0 draft.
… a survey has been sent out to AG members to get comments on the new draft. Big issues for us to work on will appear as Github issues.
… short names are being updated this week to follow the pattern of {object} {goal}. For example, "image detectable" and "text resizable" (not final wording).
… some of our items might be moved from our group to another group. For example text appearance may move to User Control as it seems to be a better fit for the Control Text section.
… it will be great if everyone on our team could read through section 2.2 Text and Wording. Reading through the rest is a good idea, but our section will be our focus this year.
… the preview doc includes github issue links. Clicking the caret in the preview doc will show you the issue text, going to github will show you the full conversation and status. There are ways to filter for issues associated within our subsection in Github.
… tests are included in some of the developing requirements. Julie walked through 2.2.1 as an examplar.
… we are tasked to fill in the blanks for requirements new to our group. In 2.2.1 there is a table that only includes English characteristics. We'll need to figure out how to complete Arabic, Chinese, Hindi and Russian characteristics.
… Text contrast (minimum) may be moved to a Subgroup working on the contrast algorithm.
… we're still working on where requirements live in WCAG 3.0 (not just which subgroup is working on them).
… Text to speech is in pretty good shape. There is only one known issue in the preview doc.
… Clear Language. As you read through the doc be on the look out for missing definitions. We have New Definitions tabs in our document to collect them and start working on them. 'Nested clauses' is new for us and needs all of our brains for assessing it, review and wordsmithing.
… another example was 'common words'. Do we need to define it or is the context strong enough?
… NEXT STEPS
- Rename IRC channel #text-wording
- Read preview version of our three subsections and add comments to the google-doc versions?
- Identify terms we need to create definitions for and add to “Definitions” tab of Text and Wording doc— placeholders needed by Jan 18th.
- Internationalization outreach?
kirkwood may need to consider Urdu in the back of our minds as we work with the languages in our list.
julierawe good news our scope is just the 5. We had to pick something to get this work defined and released. We will definitely get those questions about other langauges and we'll have to work out a way to expand over time.
LenB I can start getting some contacts to help with the completing our langauge characteristic tables.