Re: Testable statements assignments

Hi Bryan.

Regarding the "odd" intro: I'm afraid that's my fault. The reason that
example is there is that I had been asked harness-specific questions
about how to write a test case, including:

1. How do I test accessibility events expected on a platform?
2. How do I test multiple elements in a single test case?

Because my platform expects multiple accessibility events from multiple
elements when the selection is changed in a listbox, that scenario
seemed liked a good way to illustrate answers to both of the above
questions. If the markup I created as part of that illustration is
bogus, please feel free to correct it.

Thanks!
--joanie

On 03/13/2017 05:24 PM, Bryan Garaventa wrote:
> Actually I was just referring to the intro, so this is actually above where the aria-activedescendant section is. It seemed odd so I wanted to mention it.
> 
> 
> Bryan Garaventa
> Accessibility Fellow
> SSB BART Group, Inc.
> bryan.garaventa@ssbbartgroup.com
> 415.624.2709 (o)
> www.SSBBartGroup.com
> 
> 
> -----Original Message-----
> From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] 
> Sent: Monday, March 13, 2017 10:10 AM
> To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
> Cc: ARIA Working Group <public-aria@w3.org>; Joanmarie Diggs <jdiggs@igalia.com>
> Subject: Re: Testable statements assignments
> 
> Hi Bryan, 
> 
> I am not sure where you are looking in the wiki table. I was trying to avoid your having to do aria-activedescendant. I think it depends on what you are wanted to test. If you want to test the state change events then yeah, you will want to apply an aria-activedescendan on the listbox and also you would need to make the descendants focusable (tabindex=“-1”). You will need code to change the selected states too. Then the expected results should have the selected state exposed appropriately, and also an event to be generated for that state change. 
> 
> Best,
> Rich
> 
> 
>> On Mar 13, 2017, at 12:48 PM, Bryan Garaventa <bryan.garaventa@ssbbartgroup.com> wrote:
>>
>> Hi Rich,
>> I'm just going through the wiki page to understand this better, and noticed the following where it states:
>>
>> To test this, we could use the following markup and table: 
>>
>>  <div id="test" role="listbox" tabindex="0">
>>    <div id="item1" role="option" aria-selected="true">First</div>
>>    <div id="item2" role="option" aria-selected="false">Second</div>
>>  </div>
>>
>> This is a bit confusing to me because this results in an inaccessible listbox when aria-activedescendant is not also included on the focusable role=listbox container element to reference the aria-selected="true" role=option node.
>>
>> So is the goal here to only include markup that demonstrates the desired events or to include compliant markup too?
>>
>> Thanks,
>> Bryan
>>
>>
>> Bryan Garaventa
>> Accessibility Fellow
>> SSB BART Group, Inc.
>> bryan.garaventa@ssbbartgroup.com
>> 415.624.2709 (o)
>> www.SSBBartGroup.com
>>
>>
>> -----Original Message-----
>> From: Rich Schwerdtfeger [mailto:richschwer@gmail.com] 
>> Sent: Thursday, March 09, 2017 11:21 AM
>> To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
>> Cc: ARIA Working Group <public-aria@w3.org>; Joanmarie Diggs <jdiggs@igalia.com>
>> Subject: Testable statements assignments
>>
>> Bryan,
>>
>> Please see your 10 item we need testable statements for with the expected results for each platform. Just look for Bryan G:
>>
>> https://www.w3.org/wiki/ARIA_1.1_Testable_Statements 
>

Received on Tuesday, 14 March 2017 07:54:46 UTC