<scribe> Scribe: Jan

http://lists.w3.org/Archives/Public/w3c-wai-au/2013AprJun/0071.html

1. Re-chartering update (Jeanne)

JS: There is no news...charters are out for approval
... I expect to have news next week

2. SURVEY:

Topic 2. SURVEY:

3. Proposals arising from the Survey discussion:

Results: https://www.w3.org/2002/09/wbs/35520/20130523/results

http://lists.w3.org/Archives/Public/w3c-wai-au/2013AprJun/0067.html

B.4.1.2 Option to Reactivate Features:

Greg's wording: B.4.1.2 Option to Reactivate Features: The authoring tool does not include the option to permanently turn off its accessible content support features. (Level A)

<jeanne> +1 to greg's wording

JR: Alastair agreed with the wording

Proposal from the survey: B.4.1.2 Option to Reactivate Features: The authoring tool does not include the option to turn off its accessible content support features or the features can be turned back on. (Level A)

AL: Personally prefers the original proposal

JR: I will follow-up with Greg on this.

JS: I could do a survey.

B.4.1.3 Feature Deactivation Warning:

Proposed: B.4.1.3 Feature Deactivation Warning: The authoring tool does not include the option to turn off its accessible content support features or, when turning off these features, authors are informed that this may increase the risk of content accessibility problems (WCAG). (Level AA)

Greg proposed this: B.4.1.3 Feature Deactivation Warning: The authoring tool does not include the option to turn off its accessible content support features or, if these features can be disabled, authors are informed that this may increase the risk of content accessibility problems (WCAG). (Level AA)

SN: OK with Gregs wording

TB: OK with it

JS: improvement

Resolution: Change B.4.1.3 wording to: B.4.1.3 Feature Deactivation Warning: The authoring tool does not include the option to turn off its accessible content support features or, if these features can be disabled, authors are informed that this may increase the risk of content accessibility problems (WCAG). (Level AA)

What to do with B.2.4.4 Identify Template Accessibility (Enhanced)

'http://lists.w3.org/Archives/Public/w3c-wai-au/2013AprJun/0073.html

JS: I'd like to see if we can address this a different way
... Though I know "all templates" accessible isn't feasible

JR: Maybe for the survey?

AL: Yes, would like to chew on it

4. Implementation report (Jan)

http://www.w3.org/WAI/AU/2013/ATAG2ImplementationReport.html

JR: Reminder to Microsoft and IBM
... Next meeting June 17

This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: Jan
Inferring ScribeNick: Jan
Default Present: Jeanne, Jan, Alex, Tom, Sueann
Present: Jeanne Jan Alex Tom Sueann
Regrets: Greg_P. Jutta_T._(partial) Tim_B._(partial) Alastair_C
Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2013AprJun/0071.html
Got date from IRC log name: 10 Jun 2013
Guessing minutes URL: http://www.w3.org/2013/06/10-au-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.