Re: Agenda January 26, 2016 SVG accessibility Task Force meeting

Amelia,

Rich, Doug and I were the only ones present so we instead of having a
meeting we did housekeeping and reviewed Rich's 2015 actions.  I felt safe
reviewing and closing uncontroversial actions that didn't need editorial
review. We created a new 'SVG Next' product in the tracker to tag actions
in a wait state. Action-1601 and Action-1704 were moved to SVG Next.  We
got as far as Action-1704 in Rich's actions.

I did ask for an explanation of an issue Joanie Diggs raised via github,
the issue being - the documentation allows for multiple titles and desc
children and we did not have a test for it.  I am going to raise Joanie's
issues in another email.


                                                              
     Regards,                                                 
                                                              
    Fred Esch                                                 
 Watson, IBM, W3C                                             
  Accessibility                                               
                                                              
 IBM Watson       Watson Release Management and Quality       
                                                              






From: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
To: Fred Esch/Arlington/IBM@IBMUS
Cc: SVG WG axs TF TLA п╖-f ... <public-svg-a11y@w3.org>
Date: 01/26/2016 02:29 PM
Subject: Re: Agenda January 26, 2016 SVG accessibility Task Force
            meeting



Apologies for missing the call.  Got mixed up about time zones, thought it
wasn't until 1pm my time.

Were there enough participants to have a meeting? Any minutes/decisions?

~Amelia

On 21 January 2016 at 07:57, Fred Esch <fesch@us.ibm.com> wrote:
  Meeting info
  This is a Tuesday 1pm Boston time meeting
  Join WebEx meeting Meeting number: 645 955 799
  irc: #svg-a11y
  Meeting password: ping on IRC

  Join by phone
  +1-617-324-0000 US Toll Number
  Access code: 645 955 799

  minutes from last meeting
  https://lists.w3.org/Archives/Public/public-svg-a11y/2016Jan/0018.html


  Issue and Action Tracker https://www.w3.org/WAI/PF/svg-a11y-tf/track/


  Agenda

  Topic Amelia clarified textPath should be treated like tspan in the AAM
  Rich, Amelia and I believe this is true want to bring it before the group


  Topic Action/Issue Review
  Issue and Action Tracker https://www.w3.org/WAI/PF/svg-a11y-tf/track/


  ACTION-2005: Add testable statements for empty or whitespace names and
  descriptions
  ACTION-1758: Expand testable statements to include roles.
  ACTION-1746: Work on developing test cases for svg 2 accessibility &
  svg-aam
  ACTION-1635: Make sure that name computation include inheriting title
  from parents
  ACTION-1663: Get with aria task force and steve faulkner to see if
  <figure> can reference the graphics spec. or move it to aria as a region
  subclass
  ACTION-1664: Change the inheritence in role=Б─°graphicaldocБ─² from document
  to structure
  ACTION-1665: Change roles to have graphics- as the prefix

  Please bring up actions you closed so we can close related issues, please
  send me or bring up any additional actions that need to be reviewed or
  discussed

  Topic Global ARIA attributes and SVG
  I hope we can buzz though the action and issue review since the issues
  and actions were discussed last week or are old. I expect most of the
  meeting to used on this topic - how global ARIA attributes should/should
  not affect SVG. This can be a complicated topic since it involves several
  documents and working groups. I am hearing questions like - what if an
  SVG element has aria-* on it then will it appear in the accessibility
  tree since aria properties are part of the API? And requests like, please
  make a test case where the SVG has an aria-flowto in it. I am reluctant
  to make a test case where I don't know what should happen and where I
  can't find in a document where it says what should happen.

  Global ARIA states and properties are defined in ARIA in HTML Section 4.
  https://www.w3.org/TR/html-aria/#index-aria-global and provided below.
  Note drag and drop attributes may be dropped.
              aria-atomic
              aria-busy (state)
              aria-controls
              aria-describedby
              aria-disabled (state)
              aria-dropeffect
              aria-flowto
              aria-grabbed (state)
              aria-haspopup
              aria-hidden (state)
              aria-invalid (state)
              aria-label
              aria-labelledby
              aria-live
              aria-owns
              aria-relevant
                                                     
     Regards,                                        
                                                     
    Fred Esch                                        
 Watson, IBM, W3C                                    
  Accessibility                                      
                                                     
 IBM Watson       Watson Release Management and      
                  Quality                            
                                                     









т