<scribe> scribe: fesch

<richardschwerdtfeger> chair: Rich

looking up

SVG A11y

Fri 11/13/2015 10:00 AM - 11:00 AM

(Repeats)

Attendance is required for Fred Esch

<scribe> Chair:

shepazu@mit.edu

Location:

https://mit.webex.com/mit

This entry has an alarm. The alarm will go off 5 minutes before the entry starts.

Required:

Fred Esch/Arlington/IBM

Repeats:

This entry repeats

Join WebEx meeting

Meeting number:

645 955 799

Meeting password:

w3c

Join by phone

+1-617-324-0000 US Toll Number

Access code: 645 955 799

Can't join the meeting? Contact support.

IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please...

scribe: note that any such recordings may be subject to discovery in the event of litigation.

rs; we are going to need detailed meetings with browser vendors, to get SVG a11y on the radar

rs: need to go back and do changes to SVG ARIA section and sync up with ARIA 1.1

ds: Amelia introduced specs, walked over high level issues with SVG WG, and what the strategy is
... SVG WG seemed to understand, it is important we have them understand what we are publishing, got approval from SVG WG for both pubs :)

rs: Deque is willing to write test cases

<AmeliaBR> Any issues with the new TR stylesheets should be reported on this GitHub repo: https://github.com/w3c/tr-design/issues

how do get implementers to implement it

abr: not sure whether we want implementations, but we want feedback from implementors

ds: we need to decide when the right time to contact them is

chaals: I don't think it is not ready yet, good to contact folks and get them aware of it
... good to get SVG working group aware of what we are doing

abr: at this point it is we just published it and after we work through issues

rs: did you talk with them about text?

abr: everyone understands when using shapes/path's for text
... browsers hesitant to have ARIA change stuff

rs: who was giving the most push back?

abr: that was a few months ago

chaals: usually Mozilla and Google concurs

rs: information too important to not make use

chaals: browser vendors hesitant to change architecture and we want them to change - and we do want them to change and not do a half a**ed job

abr: so little native semantics, so this is really an opportunity
... SVG WG already overwhelmed with other issues
... folks on WG not the folks impacted by what we are suggesting
... do we need anymore changes in Graphics Module?

rs: no

fesch: what is our next goal?

rs: getting browser vendors onboard
... we can certainly work on the graphics module, but that should be a quarter of our time

abr: name computation... will be significant

rs: more on name computation will come up

fesch: I've heard two things on whether we should talk to browser vendors

rs: i think we need get greater browser feedback

chasals: Doug mentioned and I agreed that this isn't fully baked

chaals: need examples
... need SVG 1.0 accessibility stuff implemented

rs: safari doesn't work without voiceover on?

fesch: what should we be doing until the end of the year?

abr: lets start a thread on the list on what needs to be done next
... one item is authoring guidance...

chaals: examples and demonstrate what you can do with it

fesch: taxonomy is still meager..\

chaals: so what... we need clear examples of stuff

fesch: we haven't gone into low vision and color blind support, should that be in examples

chaals: yes

abr: that affects authoring guidance

ds: low vision and color blind is not SVG specific, lets focus on SVG specific

abr: true can point to other docs in authoring guidance

ds: if you are using a magnifier and looking at scatterplot - they might not be able to see the axes - that is SVG specific

fesch: does every graphic must support the lowest common demonstrator?

chaals: SVG may have all the tools to do it

fesch: so what you are saying is color blind and low vision may be authoring guidance?

ds: should not do this unless it is SVG specific, may conflict with other guidance

chaals: but our examples should demonstrate that we can support

abr: think about stuff over the next week and we can decide next week what our priorities are

ds: Leone worried about moving on... we should get everyone to agree

rs: have a lot of week to do...

rrsagent make minutes

This is scribe.perl Revision: 1.140  of Date: 2014-11-06 18:16:30  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: fesch
Inferring ScribeNick: fesch

WARNING: No "Present: ... " found!
Possibly Present: AmeliaBR Location Repeats Required abr chaals chasals ds fesch https richardschwerdtfeger rs shepazu
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Got date from IRC log name: 13 Nov 2015
Guessing minutes URL: http://www.w3.org/2015/11/13-svg-a11y-minutes.html
People with action items: 

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