- From: Fred Esch <fesch@us.ibm.com>
- Date: Tue, 23 Aug 2016 09:54:00 -0400
- To: "Shane McCarron" <shane@spec-ops.io>, "Richard Schwerdtfeger" <schwer@us.ibm.com>
- Cc: "Michael Cooper" <cooper@w3.org>, public-aria-test@w3.org
- Message-Id: <OF3E4ADB8B.89E81E67-ON85258018.00483CC9-85258018.004C5B22@notes.na.collabserv.c>
Hi Rich and Shane,
Rich modified the ARIA 1.1 testable statements lets talk about the format.
MSAA and IAccessible2 are separate rows. +1
Objects (with attributes) are noted as a table column and when converted
to JSON will make an object - named object
How should objects from methods be described (with parens or without)?
Shane does the overall organization work for you, when converted to a JSON
object?
Do we want the parens in objects from methods (groupPosition or
groupPosition())?
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
If they are testable lets figure out a format that Shane can extract
what needs to done from the JSON.
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.
Regards,
Fred Esch
Watson, IBM, W3C
Accessibility
IBM Watson Watson Release Management and Quality
Attachments
- image/gif attachment: 10867617.gif
Received on Tuesday, 23 August 2016 14:01:43 UTC