See also: IRC log
trackbot, start meeting
<scribe> meeting: ARIA Testing
<scribe> scribe: jongund
FE: Update on script
https://www.w3.org/wiki/ARIA_1.1_Testable_Statements_JSON
JG: Sent an e-mail the deque
people about creating test cases
... Hopefully hear back from them soon
<ShaneM> oops - I assumed we werent meeting 'cause of cynthia. brt
Are you coming Shane
JG: What do got shane?
SC: I sent out some e-mails with
links
... We could talk through the concepts
JD: I would love too
<ShaneM> https://www.w3.org/wiki/ARIA_1.1_Automated_Testing#Proposed_Architecture
SC: What I am thinking was documented a while back, I have added additional informatino
JD: I remember from the previous
meeting a shim, the hareness is making a series of
sockets
... There would be one generic socket..., accessible socket,
figure out what Shim is being used, send dictionary to
shim
... It would return pass/fail
SC: You can't assume the shim will have access to the accessibility information
<ShaneM> The local ATTA is an "Assistive Technology Test Adapter"
SC: I have named the shim
"Assistive Technology Test Adapter "
... Last week stanley said they could add a accessibility
server...
... I have been writing the code to talk to the ATTA
... The proposal is that the test window, that child window
including HTML and JSON strucuture
... That window connects to local ATTA, sending a start command
with some info
... The ATTA can find the right window and then say I am ready,
it can then evaluate a set of things, so that more specific
failure information
JD: If what you send a dictionary,why not send a dictionary back
SC: We may want to do some interactive stuff
JD: I was thinking about the work done to find things
SC: That's why we have the start
command
... Then when it is done it cycles to the next test
... I have almost finished with the WPT script and then I will
build a test ATTA to test my scripts
JG: Sounds great!
JD: As soon get something I can build the ATTA for ATK
SC: It is a RESTFUL ATTA commands
<ShaneM> https://www.w3.org/wiki/ARIA_1.1_Automated_Testing#ATTA_Commands
SC: Reviewing the API
... I will put in port information
FE: Many ports under 1024 are reserved
SC: I will send a link to the repo
JG: What happens if it doesn't hear?
SC: It will require a manual test
JG: You may also want to make "NOTRUN" also resort to a manual test
<ShaneM> https://www.w3.org/wiki/ARIA_1.1_Testable_Statements#cell
SC: Talking about an an example
of reviewing a cell
... There are three items in AXAPI to test
... If the ATTA says it can't do it then we should go into
manual testing mode
... We should have a special result called ERROR
JD: Depending on which testable
statement, there will want to test for the absence of
something
... We need to be able to check for the absence of stuff
SC: Thank you JD for that
... How do we represent that?
FE: We have taken some stuff, we have put in NOT
JD: I don't know the exact way,
the state of a name value, the absolute must not be there
... We need to specify the property and what must be there and
not be there
<fesch> https://www.w3.org/wiki/ARIA_1.1_Testable_Statements_JSON
Reviewing ATK accessibility API
<ShaneM> https://www.w3.org/wiki/ARIA_1.1_Testable_Statements#aria-busy.3D.22true.22_on_a_listbox_Rich_Start
JD: You would have to programmatically change the selection and false should be returned
<ShaneM> +1 to what joanie is saying
<joanie> ShaneM: property
<joanie> ShaneM: property (role, state, interface), value (ROLE_CHECKBOX)
<joanie> has_state, lacks_state
<joanie> state_contains, state_lacks
<ShaneM> when something is not present it is "undefined"
<ShaneM> state | state_system_checked | undefined
<ShaneM> role | role_sytem_checkbutton _ true
<ShaneM> FWIW this is EXACTLY why I didn't want the ATTA to do the checking
JG: We will meet next week
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/Por/Many por/ Found Scribe: jongund Inferring ScribeNick: jongund WARNING: No "Topic:" lines found. Present: Joanmarie_Diggs fesch jongund Found Date: 07 Sep 2016 Guessing minutes URL: http://www.w3.org/2016/09/07-aria-test-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]