Re: Live Code for APG: ARIA Accordion design pattern ready for review

Seems to work OK for me. Can you retry. 

> On Jul 17, 2016, at 19:11, Matt King <a11ythinker@gmail.com> wrote:
> 
> Bryan, 
> 
> Thank you very much for your work on this.
> 
> Unfortunately, I am getting a 404 from the demo url.
> 
> Matt
> 
> -----Original Message-----
> From: Bryan Garaventa [mailto:bryan.garaventa@ssbbartgroup.com] 
> Sent: Sunday, July 17, 2016 6:28 PM
> To: ARIA Working Group <public-aria@w3.org>
> Subject: Live Code for APG: ARIA Accordion design pattern ready for review
> 
> Hi,
> The code for the accordion wireframe is ready, which can be tested at
> http://snoringfoot.dyndns.org/Webserver/ARIA%20Accordions/demo.htm
> 
> At present this is just the coded implementation since my primary objective
> was to simply build out what works first, then document it after we finish
> any tweaks. For this reason, I'm hosting this temporarily on a test server.
> 
> Also, you can download this zip file at
> http://snoringfoot.dyndns.org/
> 
> Included within this is a vanilla JavaScript helpers lib I've cobbled
> together over some years now, which should aid in the process for building
> out these widgets in the future. This is included within the file
> "helpers.js'.
> 
> The design pattern uses the new model for Accordions, which is the use of
> individually focusable toggles in combination with aria-expanded to convey
> the active state of each toggle.
> 
> The setup for this type of implementation is automatically scalable, meaning
> that it can include any type of embedded control type within the dynamically
> expandable sections, including other complex ARIA widget controls, or even
> embedded accordion controls to nest functionality. This is why the named
> regions are important for intuitive grouping.
> 
> This too works on mobile touch screen devices, and within setup.js,
> redundant event handling shows how the same script can be applied to
> non-native triggering elements such as Div or Span elements in place of
> native links or buttons for use as accordion toggles.
> 
> Within this demo, the styling and content are just what I've thrown
> together, but all can be changed however you like. It probably needs some
> positioning work for the accordion section content for instance. The
> triggering elements are presently A tags, but these can be changed to native
> buttons, or even simulated elements like Div or Span with tabindex='0' and
> role='button', and the scripting will still work accessibly.
> 
> Also, please feel free to use the helpers.js file for whatever you wish as
> well, it may make this process go faster.
> 
> All the best,
> Bryan
> 
> 
> 
> 
> Bryan Garaventa
> Accessibility Fellow
> SSB BART Group, Inc.
> bryan.garaventa@ssbbartgroup.com
> 415.624.2709 (o)
> www.SSBBartGroup.com
> 
> 
> 
> 

Received on Monday, 18 July 2016 02:42:49 UTC