W3C

- DRAFT -

SV_MEETING_TITLE

23 Feb 2016

See also: IRC log

Attendees

Present
AmeliaBR, MarkSadecki, Rich_Schwerdtfeger
Regrets
Jason
Chair
fesch
Scribe
Rich

Contents


<fesch> agenda https://lists.w3.org/Archives/Public/public-svg-a11y/2016Feb/0041.html

<shepazu> regrets for today, I'm at a f2f meeting

<scribe> scribe: Rich

Open Actions

<fesch> https://www.w3.org/WAI/PF/svg-a11y-tf/track/

Amelia: My open actions tie into SVG-AAM based on feedback. I have started it but I am not yet ready to share it.
... Regarding clearer documentation in SVG2 it will make it easier to address issues with focus management in SVG2

Rich: there are issues with HTMl vs. SVG2 where both don’t match

Amelia: I agree for focus management. They links and definitions are inconsistent and we can’t fix the HTML side
... I am going to make sure we have clear directions on the SVG side to ensure Focus navigation is consistent.
... what elements can be accessible with tabindex. What element are focusable, etc.
... I agree with your issue filed.

Action 2003

<fesch> action-2003

<trackbot> action-2003 -- Richard Schwerdtfeger to Investigate how role=none interacts with other aria- attributes, in other aria specs. -- due 2016-02-16 -- OPEN

<trackbot> http://www.w3.org/WAI/PF/svg-a11y-tf/track/actions/2003

Action-2003?

<trackbot> Action-2003 -- Richard Schwerdtfeger to Investigate how role=none interacts with other aria- attributes, in other aria specs. -- due 2016-02-16 -- OPEN

<trackbot> http://www.w3.org/WAI/PF/svg-a11y-tf/track/actions/2003

Amelia: if something has role=“none” and they have an aria-label that they not put in the a11y tree. Rich to check with ARIA 1.1

Action 2010

Action-2010?

<trackbot> Action-2010 -- Richard Schwerdtfeger to Update svg-aam and svg 2 to include the new roles from the aria graphics module -- due 2016-02-16 -- OPEN

<trackbot> http://www.w3.org/WAI/PF/svg-a11y-tf/track/actions/2010

<fesch> action-1004

<trackbot> Sorry, but action-1004 does not exist.

<fesch> issue-1004

<trackbot> issue-1004 -- The Use element should default to graphics-symbol and also graphics symbol should subclass graphic -- open

<trackbot> http://www.w3.org/WAI/PF/svg-a11y-tf/track/issues/1004

RESOLUTION: Close Action 2010 and issue 1004

<scribe> completed

Action 2011

<fesch> action-2011

<trackbot> action-2011 -- Fred Esch to Review svg 2 section on multi-lingual title/desc & identify any under-specified conditions or edge cases -- due 2016-02-16 -- OPEN

<trackbot> http://www.w3.org/WAI/PF/svg-a11y-tf/track/actions/2011

Fred: One of the things taht we found was an empty title
... with an empty tooltip or a white spaced tooltip none show a tooltip

Amelia: Rich and I udpated them on the call and there is nothing in the spec. about it. They are deferring to us in accessibility matters

Fred: We would put it in the accessibility tree if they showed a tooltip

Rich: I spoke with the core mapping team and they agreed that if they put in an empty title and then we do nothing special in the name computation.

Fred: what about whether we keep the element in the tree?

Rich: we keep it as we have it

Amelia: we put these issues in authoring tools to warn the author

RESOLUTION: If an empty title or a title with all whitespace is used then the element is put in the accessibility tree for elements that are considered renderable.

Amelia: we assume the attribute exists aria-label=“” then it is consistent. However, aria-labelledby must point to a a valid id.
... the <desc> element must be treated the same way
... we might want to up this to a normative rule for authors.

<scribe> ACTION: Amelia: modify the SVG2 spec. to require authors when useing <title> or <desc> to not leave them empty or with only white space. An author MUST [recorded in http://www.w3.org/2016/02/23-svg-a11y-minutes.html#action01]

<trackbot> Created ACTION-2015 - Modify the svg2 spec. to require authors when useing <title> or <desc> to not leave them empty or with only white space. an author must [on Amelia Bellamy-Royds - due 2016-03-01].

RESOLUTION: <desc> must follow the same rules for <title> regarding empty or whitespace only strings

Action 2012

<MarkS> action-2012

<trackbot> action-2012 -- Richard Schwerdtfeger to Change mesh in aam to map to image -- due 2016-02-23 -- OPEN

<trackbot> http://www.w3.org/WAI/PF/svg-a11y-tf/track/actions/2012

https://svgwg.org/svg2-draft/struct.html#implicit-aria-semantics

Rich: for mesh: none role provided no associated ‘title’ element, ‘desc’ element, ‘aria-label’ attribute, ‘aria-labelledby’ attribute, ‘aria-describedby’ attribute; or ‘tabindex’ attribute; otherwise, img role

RESOLUTION: close Action 2012

close action-2012

<trackbot> Closed action-2012.

<AmeliaBR> Relevant text from SVG 2 "Unlike other paint servers, a mesh defined outside of a ‘defs’ section is rendered. In this the case, the mesh has a bounding box determined by its maximum extent, taking into account all of its patches."

Action 2013

<fesch> action-2013

<trackbot> action-2013 -- Richard Schwerdtfeger to Update allowed roles in svg-aam & svg 2 to include new graphics module roles -- due 2016-02-23 -- OPEN

<trackbot> http://www.w3.org/WAI/PF/svg-a11y-tf/track/actions/2013

<fesch> close action-2013

<trackbot> Closed action-2013.

RESOLUTION: Close Action 2013 as completed

Action 2009

<MarkS> action-2009

<trackbot> action-2009 -- Fred Esch to Create testable statements with multiple title/desc elements -- due 2016-02-09 -- PENDINGREVIEW

<trackbot> http://www.w3.org/WAI/PF/svg-a11y-tf/track/actions/2009

Meeting Time

<fesch> http://doodle.com/poll/zxmyzm728qr4chatnnhunhch/admin#table

RESOLUTION: Move meeting times to 2PM EST

Text with multiple elements

Tests with multiple elements

<fesch> https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions

Fred: There are a few test assertions that are purposeful
... If you look where teh test element is the second element

<fesch> test element is second element

Fred: that is one
... how many tests do we need to do before we know it is OK?

Amelia: We can’t test everything but we have to test the main branches of a decision tree to make sure we have a decision for that

<fesch> https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions/Language

Fred: on the other pages we have the language test
... they have lots of things like multiple titles
... They have groups around multiple things that are being tested to have a non-english example
... are we ok with that? If we want more can we just put that in?

Amelia: Where specific edge case are needed we do that.
... I need to read through what you have

Fred: Charles said when you annotate things with an accessible name and it just stops

Amelia: We need to make sure we have multiple elements in the test. then we do that.

Rich: we could have a 2 page test with all the the element to test if in or outside the tree

Fred: we need a unique id for the test in the page. so, each one has to be on separate pages

SVG Spec. Ambiguous issues

Amelia: we have discussed all of these but we do not have resolutions for all of these
... We briefed the SVG2 working group and they left it up to us to deal with a11y issues

Graphics-AAM

Amelia: I gave it a quick overview but I am not an expert.

Rich: I gave the graphics spec. to James Craig at Apple and Joanie Diggs at Igalia and they will come back with Mac and Linux mappings

Inline in SVG and W3C documents

Fred: If you have an SVG document and the first element is <g> and it has an aria-label of “bob” it just says bob.

Rich: where was that tested?

Amelia: we shoudl be giving advice for maximum reasonable accessibility

s/shouldl/should/

Fred: I have a perl script that has an SVG document and an HTML file that makes the SVG document in line

Rich: every platform has a different set of APIs

https://www.w3.org/WAI/PF/testharness/testcases?testsuite_id=4

https://www.w3.org/WAI/PF/testharness/testcases/edit?testsuite_id=4&testcase_id=76

https://www.w3.org/WAI/PF/testharness/testcases/edit?testsuite_id=1&testcase_id=80

<scribe> chair: Fred

Summary of Action Items

[NEW] ACTION: Amelia: modify the SVG2 spec. to require authors when useing <title> or <desc> to not leave them empty or with only white space. An author MUST [recorded in http://www.w3.org/2016/02/23-svg-a11y-minutes.html#action01]
 

Summary of Resolutions

  1. Close Action 2010 and issue 1004
  2. If an empty title or a title with all whitespace is used then the element is put in the accessibility tree for elements that are considered renderable.
  3. <desc> must follow the same rules for <title> regarding empty or whitespace only strings
  4. close Action 2012
  5. Close Action 2013 as completed
  6. Move meeting times to 2PM EST
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.144 (CVS log)
$Date: 2016/02/23 19:09:48 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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/great//
Succeeded: s/no//
Succeeded: s/3 elements in the spec/multiple elements in the test/
FAILED: s/shouldl/should/
Succeeded: s/pearl/perl/
Found Scribe: Rich
Inferring ScribeNick: Rich
Present: AmeliaBR MarkSadecki Rich_Schwerdtfeger
Regrets: Jason

WARNING: No meeting title found!
You should specify the meeting title like this:
<dbooth> Meeting: Weekly Baking Club Meeting

Got date from IRC log name: 23 Feb 2016
Guessing minutes URL: http://www.w3.org/2016/02/23-svg-a11y-minutes.html
People with action items: amelia

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


[End of scribe.perl diagnostic output]