Re: Possible Carousel demo for the APG, please review.

I meant I'm not for or against either. 

—Michiel

> On 17 Nov 2015, at 23:59, Michiel Bijl <michiel@agosto.nl> wrote:
> 
> No problem Bryan. Once you post the code I can have a look at the offset bug.
> 
> A button before the carousel itself would work. Not sure what the guide or WCAG says, but should the carousel autoplay, or should the button perhaps say “play”? I’m for/against either, just a question.
> 
> —Michiel
> 
>> On 17 Nov 2015, at 19:19, Bryan Garaventa <bryan.garaventa@ssbbartgroup.com> wrote:
>> 
>> Thanks, I’ll package up a copy of the regular code in a bit for download. It’s difficult for me to track down strictly visual stuff like the offsets, so if you could help with this that would be awesome. I can show you where this is in the code.
>>  
>> Adding a pause element is no problem, it takes me longer to figure out where to put this in the layout.
>>  
>> All the best,
>> Bryan
>>  
>> From: Michiel Bijl [mailto:michiel@agosto.nl] 
>> Sent: Tuesday, November 17, 2015 4:27 AM
>> To: Bryan Garaventa <bryan.garaventa@ssbbartgroup.com>
>> Cc: Protocols and Formats Working Group <public-pfwg@w3.org>
>> Subject: Re: Possible Carousel demo for the APG, please review.
>>  
>> This looks like a good start!
>>  
>> Found some issues:
>>  
>> No visual way to pause the slider, this is needed to satisfy WCAG 2.2.2;
>> Offset of slides goes out of sync after a while.
>>  
>> Could you provide a un-minified version of the slider code?
>>  
>> Some VoiceOver testing with Safari 9 on OS X 10.10 Yosemite:
>>  
>> Title for content is spoken when focused on slide itself (image portion);
>> Didn’t hear it group next/prev buttons, but not sure what that should sound like;
>> All buttons are spoken correctly.
>> 
>> —Michiel
>>  
>> On 16 Nov 2015, at 21:03, Bryan Garaventa <bryan.garaventa@ssbbartgroup.com> wrote:
>>  
>> Also, this exposes a bug in JAWS16 in IE11 where it won’t recognize the shared button grouping between the Prev and Next buttons, though there is no reason why this should be the case since this is simply a role=”group” with embedded role=”button” elements. Confirmed using JAWS16 + IE11 + Win7. I’m not sure if this occurs in JAWS17 however or in later OS versions.
>>  
>> This also makes use of the new aria-current attribute within the numerical indicators as well, though there is currently no browser or AT support for this as yet. This can be examined within the DOM using a DOM viewer utility.
>>  
>> From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com] 
>> Sent: Monday, November 16, 2015 11:48 AM
>> To: 'PF' <public-pfwg@w3.org>
>> Subject: Possible Carousel demo for the APG, please review.
>>  
>> Hi,
>> I've been working on a carousel demo that uses different concepts than those previously explored such as Tabs and Listboxes, which I find to be more intuitive from a UX perspective. This is meant to be in accordance with the guidance at
>> http://www.w3.org/WAI/tutorials/carousels/
>>  
>> This is live at
>> http://whatsock.com/tsg/Coding%20Arena/Carousels,%20Slideshows,%20and%20Wizards/Carousel%20(Flat%20from%20XML%20with%20Overrides)/demo.htm
>>  
>> This uses standard button roles plus named region and group to identify associated button groupings, plus CSS tooltips for added keyboard-only user accessibility support, plus a one tab stop scrollable slide region for single keypress navigation if desired for keyboard-only users.
>>  
>> The slides just include images at the moment as placeholders, but can be anything from multiple images, combinations of images and links and form fields, etc.
>>  
>> Please let me know if I’ve missed anything or if anything looks off.
>>  
>> Thanks,
>> Bryan
>