Re: ARIA 1.1 testable statements

Shane,

Thanks for the quick feedback. For objects from methods like groupPosition
(), we can leave the () in the table if it helps readability, and not
include it in JSON.

I don't know what pattern means either.

Rich,

Who can we ask about testing UIA patterns
How do you test a ZZZ pattern?
How can you test MUST NOT support the YYY pattern?

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






From:	Shane McCarron <shane@spec-ops.io>
To:	Fred Esch/Arlington/IBM@IBMUS
Date:	08/23/2016 10:28 AM
Subject:	Re: ARIA 1.1 testable statements



Comments inline:

On Tue, Aug 23, 2016 at 8:54 AM, Fred Esch <fesch@us.ibm.com> wrote:
  Hi Rich and Shane,


  Rich modified the ARIA 1.1 testable statements lets talk about the
  format.
     1.	MSAA and IAccessible2 are separate rows. +1
     2.	Objects (with attributes) are noted as a table column and when
        converted to JSON will make an object - named object
that's fine.
     2.	How should objects from methods be described (with parens or
        without)?
Without.

  Shane does the overall organization work for you, when converted to a
  JSON object?

I am not the final arbiter here, but I imagine we can make it work.

  Do we want the parens in objects from methods (groupPosition or
  groupPosition())?

No.  JSON doesn't like that.  Unless you are going to put it into a string
anyway.


  On role cell Rich added Selection pattern and MUST NOT support the invoke
  pattern. I don't know how Shane can take strings like that in a JSON
  object and turn them into automated tests. My suggestion is
        If they are untestable with an automated test - lets omit them from
        the table

Hmm.  If you can define the "pattern" then maybe there is a way to
automatically test it.  Basically we want to test everything that is an
assertion...

        If they are testable lets figure out a format that Shane can
        extract what needs to done from the JSON.


Agreed.  Some syntax that would mean something is not present in the tree.

  The roles are going much slower than I thought as they are not just cut
  and paste. And I can't document the format of the testable statements
  until we decide on a format and Shane thinks it will produce a usable
  form in JSON.


Don't let me / us stop you.  I expect this will be a little iterative.


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









--
Shane McCarron
Projects Manager, Spec-Ops