HTML Techniques Task Force -- 30 Jan 2012

<Joshue108> agenda, this?

<Joshue108> https://www.w3.org/2002/09/wbs/35422/2012-01_html-techs-tf-sched/

<Joshue108> http://www.w3.org/WAI/GL/wiki/Techniques/HTML5 AND

<Joshue108> http://www.w3.org/WAI/GL/wiki/Techniques/ARIA

<Joshue108> and look for a few techniques you would be interested in writing. We will ask that everyone who is participating chooses 1 technique to start off this effort

<Joshue108> http://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks

<David> Really echoing

<David_> ok is this the place in irc

<Joshue108> scribenick: Leonie

Survey results for meeting times. Please answer the survey before the meeting

<LeonieW> scribenick: LeonieW

<Joshue108> https://www.w3.org/2002/09/wbs/35422/2012-01_html-techs-tf-sched/

JOC: Has everyone filled in the survey?

JN: If there is anyone you think should be here can you let us know?
... People need to be members of either PF, WCAG or both.
... We should be clear which list we use for traffic.
... I think Xtech might be the best option.

JOC: For now everything should go to both lists.

<Joshue108> RESOLUTION: Minutes to go to both group lists for the forseeable future

rssagent, make minutes

First "assignment" of techniques. Please look over the proposed techniques listed at

JN: Cynthia put together a list of ARIA and HTML techniques that need writing.

<Joshue108> http://www.w3.org/WAI/GL/wiki/Techniques/HTML5

<Joshue108> http://www.w3.org/WAI/GL/wiki/Techniques/ARIA

TB: Is there any priority?

JOC: Everyone has carte blanche to offer to tackle techniques.

JN: Some have been assigned. If there isn't a link, work may not have been started.

<Loretta> David, you may have more work on landmarks, too...

<David_> no problem reworking landmarks... i expect that...

<Joshue108> ack, cstrobbe

DM: I can take labelledby and describedby.

DT: I can take maxlink.

MJ: I could take the error identification stuff under 3.3.1.

<Loretta> http://www.w3.org/WAI/GL/wiki/Technique_Instructions http://www.w3.org/WAI/GL/wiki/Technique_Template

<Loretta> These are the links to the current documents describinghow to write WCAG techniques.

CS: I can take 3.1.3.

LGR: Just posted a link to documentation on writing techniques.

JOC: We could collaborate on some techniques.

<jamesn> scribeNick: jamesn

Discussion of ARIA Landmark technique proposed at

JOC: will send out a mail to list to ask for more volunteers!

http://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks

<Joshue108> JN: This is new ARIA techniques

<Loretta> https://www.w3.org/2002/09/wbs/35422/20120126misc/results

<David_> I'm there now

<Joshue108> JN: The fact that we have a bias towards WCAG means we need to do some outreach towards PF.

<Joshue108> JN: This may have to wait until the HTML5 work calms.

LR: we normally visit each comment and see if there is anything actionable in them
... Detlev raises 2 issues. The first is whether there is user agent support. This suprised me as think there is good support for them

JOC: good support 3 back
... in JAWS

LR: an important questions for these technologies. Should be fiulling in the user agent notes for these techniques

TB: More than 1 independant AT? is this sufficient?

LR: WCAG says they won't rule on how much? Just try to capture what is there
... try to give the author a feel about where there may be a problem

JOC: where is the line on when something is accessibility supported?
... where is the line?

LR: ultimeatly the author's responsibility as the author may be writing an intranet app where the platform is known
... try to give the author guidance where something is supported or not

DMD: in general pretty safe if 3 versions back

LR: we will document something in most recent version but will note that

JOC: could perhaps scaffold the techniques??

DMD: a little concerned about that

JOC: are you saying this dilutes it?

DMD: yes

<Zakim> cstrobbe, you wanted to ask what login you need for the wiki

JOC: we have to make sure that what we do is Accessible to developers

DMD: we need to track down people who are doing testing so we aren't reinventing the wheel

JOC: Gez & Steve Faulkner may be able to help

JN: suggest that techniques may want to link to the legacy technique for doing the same thing

LR: sometimes comments get dealt with in advance

CS: 1st comment about applicability

<Joshue108> JN: Are we going to tackle ARIA on other technologies?

CS: there is a role attribute in SVG tiny . but SVG has no accessibility support

LR: sounds like info for the aria technology note

<scribe> ACTION: james to start a page for the aria technology notes section [recorded in http://www.w3.org/2012/01/30-html-techs-tf-minutes.html#action01]

CS: 2nd comment is about the aria landmark roles and whether they are resundant
... is this a bug or a feature

JOC: this is a big can of worms
... a useragent issue?
... brings up semantics issue as to how aria semantics are meant to trump the host language semantic
... but often just ends up getting the same info twice

DMD: my feeling is that 1 extra word - not too bad
... dont thiink will be a big issue

JOC: better to have it than not
... in time will iron out

LR: raises question. Are we writing different html5 VS HTML4 techniques

JOC: very good question...
... we will have to work this out

LR: the aria spec will be done sooner than html5. The spec is html4 oriented I think
... this is why we habve rendundant markup.
... something we need to thrash out

JN: same time next week.

- DRAFT -

HTML Techniques Task Force

30 Jan 2012

Attendees

Contents

Survey results for meeting times. Please answer the survey before the meeting

First "assignment" of techniques. Please look over the proposed techniques listed at

Discussion of ARIA Landmark technique proposed at

Summary of Action Items

Scribe.perl diagnostic output