<Joshue108> Survey: https://www.w3.org/2002/09/wbs/35422/NewWCAGEditRec/

<AWK> +AWK

<Joshue108> Scribe list: https://www.w3.org/WAI/GL/wiki/Scribe_List

<kirkwood> JF: waiting for feedback from others, hoping by next week to have something to report

<kirkwood> scribe:kirkwood

John Kirkwood scribing

Sarah can do next week

Wayne can do week after

Publishing new WCAG edited recommendation

<Joshue108> Scribenick: John Kirkwood

<AWK> survey link?

<AWK> https://www.w3.org/2002/09/wbs/35422/NewWCAGEditRec/

<kirkwood> Regarding: Current 1.4.3 to 1.4.3.6, any objections to Makoto edits?

<kirkwood> MichaelC: Working group has approved to progress WCAG 2.0 proposed edited recomendations?

<kirkwood> Joshue: looking for approval for edited recommendation

<kirkwood> No objection to edits published edited recommendation

RESOLUTION: CFC to go to working group list regarding Mikota’s edit and working group approval

New draft techniques from Low Vision TF

<kirkwood> Laura: says good on 5

<Joshue108> https://www.w3.org/WAI/GL/wiki/Using_a_Decorative_Icon_Font

<kirkwood> AWK: example using icon font?

<kirkwood> Laura: style in example /24 ‘black backward arrow head’

<kirkwood> AEK: Does unicode symbols count as an icon foNT?

<kirkwood> JF: are we back to square one?

<kirkwood> JF: when a symbol is produced from a font family, what do we do then? Its more about getting a clear definition of what we are talking about. It’s aterminology issue.

<kirkwood> Greg: unicode glif app such as accomidtion aids like screen reader. Wher glif desn’t correspond to a unicode standard where problems occur

<kirkwood> Accessibility aid won’t have abilty to read when using glifs of other than standrd unicode

<kirkwood> Wayne: thinks gathered together in fonts think one is called ‘awesome’

<kirkwood> Wayne: there are families, things dropped in in unicode, but there are formal fonts.

<Joshue108> http://www.sitepoint.com/introduction-icon-fonts-font-awesome-icomoon/

<kirkwood> JF: not always just visual decoration

<kirkwood> AWK: Addding on to greg saying. Are unicode symbols that assistive technologies do recognize.

<kirkwood> AWK: if using name in unicode they will probaly read a small set of characters s.a. right arrow and left arrow. Can use litigers in in font assign it to a code related to a font. Is a case we should capture

<kirkwood> Poorly supported characters and icon font should be able to distinguish

<kirkwood> Josh: don’t have to do in unicode if we know

<kirkwood> Laura: if expand to include real icon fonts not just unicode. We did this before

<kirkwood> Joshue: bundle all together or do sperate techniques?

<JF> +1 for separate techniques based on situation

<Wayne> +1 multi technique

<kirkwood> Aliastirc: replacing default unicode characters might replace with a different symbol entirely. Could have one technique poss.

<kirkwood> joshue: if we’re confused it may still be confusing...

<Joshue108> https://www.w3.org/WAI/GL/wiki/Using_a_Decorative_Icon_Font

<kirkwood> Technique 5 using a decorative icon font using unicode fonts have techniques reference other

<kirkwood> Alastair: when specifying icon font, ubut with private use area different issues with mobile and unicode and assitive tech’

<kirkwood> Alastair: important to use aria hidden and aira labels

<AWK> +1 to James but that is still an accessibility support issue

Some questions left from previous meeting

<AWK> https://www.w3.org/2002/09/wbs/35422/5April2016_misc/results

<kirkwood> did we finish current survey?

RESOLUTION: Laura to rework techniques based on working group review

<Joshue108> Editorial changes to Understanding 1.4.3 #177

<Joshue108> https://github.com/w3c/wcag/pull/177

RESOLUTION: accepted editorial changes

<Joshue108> Need to change "Understanding SC 3.3.2" as it does not accurately reflect what the SC says.(related to #164)

<kirkwood> Andrew suggested to remove 3rd paragraph, new example rqts. Greg, to speak to comments

<kirkwood> Greg: new text doesnat’ apply to hyperlinks, doesn’t take into account simple actions like clicks

<kirkwood> Greg: some abinguity form require type in a passord, asume original contraols specifically to take input vs controls to display information

<kirkwood> AWK: Is input suggesting that cliking on link is the other form you a re referring to?

<Joshue108> https://www.w3.org/TR/UNDERSTANDING-WCAG20/minimize-error-cues.html

<Joshue108> https://github.com/w3c/wcag/issues/164

<jamesn> it is not linked in the issue

<kirkwood> Greg: changing FC is not on table, not something to deal with right now. ‘When content requires user input.’ nothing in FC would mean?

<kirkwood> AWK: i wouldn t rquire user input as just clicking on a link

<kirkwood> Greg: typing and that distintion making a point about reality of selecting an itme in a list is just as much as entering data as typing into a text box. From my perspective user input is very broad. My reading and UAAG working group doesn’t match intent of WCAG working group.

<kirkwood> Greg: relunctant to hold up process due to my concerns. Having not worked on document for quite a few yeard. I am concerned that the document doesnt acutlly math FC in my reading. I fyou want to work on revise understanding based on an outsiders reading of the FC I’d do that as well

<kirkwood> AWK: content is usually stuff that is just there, greg do you have objection with what Andrew is suggesting

<kirkwood> David: in wcag when think about content all lthings on page is considered content

<kirkwood> AWK: concerning that the whole point is to provide a lear label. It should be associated with content. There are situations where text alludes to 3.3.2 you’ve got differnet options. Interested in others reading on this.

<kirkwood> Jamesn: I was reading it and lot of information 4.1.2 not strictly relevent. In order to meet 4.1.2 could do this part but doesn’t meet particular criteria

<kirkwood> JF: lot of private comments in que, what problem are we trying to solve

<kirkwood> JF: my concern is that trying to maneuver authors to da a specif way

<kirkwood> AWK: maybe we should go back to clearly and crisply identify problem. Feel like he’s I’m happy to get Sailesh's opinion

<kirkwood> Moe: tkaing look issue 164, wanted to recommend on Feburary 25th posted workd doc may hep us move forward

<MoeKraft> https://github.com/w3c/wcag/issues/164

<MoeKraft> And Josh has included contents of Sailesh's explanation in the GitHub Thread on 2/29

<kirkwood> Josh: Trying to unserstan quest in succinct in a simple way

<kirkwood> Joshue: submit new issue and outline and we’ll come back

RESOLUTION: leave open need more info

<kirkwood> Lack of understanding and need to go back to get

New Pull requests

Remaining survey items from last week

<kirkwood> Joshue; going to continue with remaing survey items from last week

<Joshue108> https://www.w3.org/2002/09/wbs/35422/5April2016_misc

<AWK> https://www.w3.org/2002/09/wbs/35422/5April2016_misc/results

<Joshue108> Issue 169

<Joshue108> Please review

<Joshue108> https://github.com/w3c/wcag/issues/169

<kirkwood> AWK: tried to talk about it las week

<kirkwood> Joshue: james important michael didn’t agree redunday, this could be clearer, James have you thought about this?

<Joshue108> https://www.w3.org/TR/WCAG20-TECHS/G10.html

<Joshue108> G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes

<kirkwood> James: similar but not redundant what michael says is yue they are bvery simialr but not the smae thing. Going to make it more complicated.

<Wayne> +1 James and Michael

<JF> +1 to James

<kirkwood> Jame; don’t need to spend time wondering aobout this

<Joshue108> G10: Creating components using a technology that supports the accessibility API features of the platforms on which the user agents will be run to expose the names and roles, allow user-settable properties to be directly set, and provide notification of changes

<Joshue108> Using the accessibility API features of a technology to expose names and roles, to allow user-settable properties to be directly set, and to provide notification of changes

<Joshue108> G135

<kirkwood> James: poorly written example

<Joshue108> https://www.w3.org/TR/WCAG20-TECHS/G135.html

<kirkwood> awk: both using accessbility api, both names and roles, in 10 using both. Not sure why created differnetly

<kirkwood> Joshua: no point in bring all together, if we could work on it . James interested in working on it?

<kirkwood> James: no

<kirkwood> AWK: getting rid of techniques is a step backwrs , but removing would remove bookmarks provide

<kirkwood> g10 has mre fleshed out procedure than 135. Feel 153 is inaducate to meet what is idnetified in title

<kirkwood> AWK: maybe needs a bit of a regrash

<kirkwood> s/regrash /refresh

<kirkwood> Joshue: more of reason to keep may have value in time

<Wayne> +1 Close and defer

<kirkwood> awk: likely to get deferred and closed later. Working group feel like value in haveing two techniques using acccessibility feature. Looking for vlunteers to suggest changes to make that happen. We don’t have bandwitdth to work on it right now

<kirkwood> Joshue: why dont we make that a resolution

<kirkwood> MichaelC: looks like eric took on itself to file this, he himself hasn’t engagted in this.

<KimD> +1 to close/defer, accept response

<kirkwood> working group to defer issue no objections

<Sarah_Swierenga> no objections

RESOLUTION: defer response

<alastairc> no objections, it's java, let us move along

<MoeKraft> +1

<Joshue108> Issue 167

<Joshue108> https://github.com/w3c/wcag/issues/167

<Joshue108> https://www.w3.org/TR/WCAG20-TECHS/H91.html

<kirkwood> awk: don’t have a current resoltion for this

<kirkwood> Joshue: up in the air

<kirkwood> awk: answer the question of ‘Why do we want to cover this’ an aproch is not change anything

<kirkwood> Joshue: keep it clean and don’t do it right now

<kirkwood> awk: we could use recommendation aria for every technique, I am agreement with what Maichael is saying, I could go ther way

<kirkwood> wayne: stand alone, aria is aria

<jamesn> now, it does need updating for new HTML input types

<AWK> OTOH ARIA is now allowed by the HTML5 spec

<AWK> ACTION: AWK to look back to see if we added new input types to H91 [recorded in http://www.w3.org/2016/04/19-wai-wcag-minutes.html#action01]

<trackbot> Created ACTION-322 - Look back to see if we added new input types to h91 [on Andrew Kirkpatrick - due 2016-04-26].

<Joshue108> https://www.w3.org/TR/WCAG20-TECHS/aria#ARIA14

<Joshue108> https://www.w3.org/TR/WCAG20-TECHS/aria#ARIA16

<kirkwood> check input type and see if everything is there. Like using html whenever we can and aria when we cant

<kirkwood> wayne: check input type and see if everything is there. Like using html whenever we can and aria when we cant

<Joshue108> https://www.w3.org/TR/aria-in-html/

<JF> ++1 to James

<kirkwood> Joshue: don’t have a desire to do a lot with this. Yes lets arddd aria to page 91?

<kirkwood> James: Happy to add related technicques

<AWK> I'm ok with James's suggestion to add related resources and nothing else

<alastairc> +1

<kirkwood> Joshue: option do nothing or add link to aria techniques

<AWK> I'm happy to write a response and add the aria technique references for this and we can survey the change

<marcjohlic> +1 to adding links to ARIA14 and aria16 in Related Techniques

<kirkwood> JF: if we know teniques that esxist why not point to them

RESOLUTION: link page 91 ith related aria techniques

<Wayne> +1

<kirkwood> Trackpot,end meeting

<Joshue108> trackbot, end meeting

This is scribe.perl Revision: 1.144  of Date: 2015/11/17 08:39:34  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/+!/+1/
Succeeded: s/borad/broad/
Succeeded: s/aentering/as entering/
Succeeded: s/tect bos/text box/
Succeeded: s/UAG working/UAAG working/
Succeeded: s/contgent/content/
Succeeded: s/criply/and crisply/
Succeeded: s/get _/get Sailesh's/
Succeeded: s/oreder to meat/order to meet/
Succeeded: s/ makrs/marks/
FAILED: s/regrash /refresh/
Found Scribe: kirkwood
Inferring ScribeNick: kirkwood
WARNING: No scribe lines found matching previous ScribeNick pattern: <John\ Kirkwood> ...
Found ScribeNick: John Kirkwood
WARNING: No scribe lines found matching ScribeNick pattern: <John\ Kirkwood> ...

WARNING: 3 scribe lines found (out of 268 total lines.)
Are you sure you specified a correct ScribeNick?

ScribeNicks: John Kirkwood, kirkwood
Default Present: AWK, JF, Josh, kirkwood, Sarah, Swierenga, MichaelC, Makoto, alastairc, Laura, KimD, allanj, marcjohlic, moekraft, Wayne, Kathy
Present: AWK JF Josh kirkwood Sarah Swierenga MichaelC Makoto alastairc Laura KimD marcjohlic moekraft Wayne Kathy

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 19 Apr 2016
Guessing minutes URL: http://www.w3.org/2016/04/19-wai-wcag-minutes.html
People with action items: awk

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