W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2017

Re: WCAG 2.0 AA and Zurb Foundation

From: Jon Gunderson <jongund@gmail.com>
Date: Wed, 2 Aug 2017 16:09:17 -0500
Message-ID: <CADBaZzP+Ou-X-O0SLMu_fXv=ZoVU1r+eJbpjRfZmtgZFXdPFbA@mail.gmail.com>
To: Phill Jenkins <pjenkins@us.ibm.com>
Cc: Mark Weiler <mweiler@alumni.sfu.ca>, "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Mark,

The oaa-accessibility.org examples are out date and I am planning to
redirect the website to the ARIA 1.1 Authoring Practices website.
The ARIA 1.1 Authoring practices include fully reviewed examples of ARIA
enabled widgets and design information needed for implementation.

https://www.w3.org/TR/wai-aria-practices-1.1/

Most widget section includes one or two example implementations, and the
source code is also provided.

Jon


On Thu, Jul 27, 2017 at 5:38 PM, Phill Jenkins <pjenkins@us.ibm.com> wrote:

> Have you look at similar front-end frameworks that have incorporated
> accessibility, such as Open Ajax - see http://oaa-accessibility.org/
>
> I do not know of any organizations working with Zurb's Foundation.  If
> it's not mainstream and accessible, why work on it (unless it is also being
> specifically designed for a narrow user group, like AAA success criteria
> could be applied to it?
> ___________
> Regards,
> Phill Jenkins
> pjenkins@us.ibm.com
> Senior Engineer & Accessibility Executive
> IBM Research Accessibility
> linkedin.com/in/philljenkins/ <https://www.linkedin.com/in/philljenkins/>
> ibm.com/able <http://www.ibm.com/able>
> facebook.com/IBMAccessibility <http://www.facebook.com/IBMAccessibility>
> <http://ageandability.com/>twitter.com/IBMAccess
> ageandability.com
>
>
>
> From:        Mark Weiler <mweiler@alumni.sfu.ca>
> To:        "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
> Date:        07/27/2017 04:35 PM
> Subject:        WCAG 2.0 AA and Zurb Foundation
> ------------------------------
>
>
>
> Does anyone know of organizations working with Zurb's Foundation to create
> a web application frontend framework of UI components that is intentionally
> designed to be conformant with WCAG 2.0 AA (I'm mindful that some
> responsibilities would still reside with the user of the framework)
>
> Such a group would be mindful of techniques to meet the specific success
> criteria, cognizant of the need for both automated and manual tests, and
> mindful of the need for regression testing before integrating changes into
> the code base.
>
> An example of a strong statement of WCAG conformance might be something
> like the Section 508 statement here:
> *https://assets.cms.gov/resources/framework/3.4.1/Pages/#accessibility*
> <https://assets.cms.gov/resources/framework/3.4.1/Pages/#accessibility>
>
> or
>
> "The Assets.CMS.Gov website is tested on an iterative basis for
> conformance with the Section 508 requirements"
> *https://assets.cms.gov/resources/framework/3.4.1/Pages/#governance*
> <https://assets.cms.gov/resources/framework/3.4.1/Pages/#governance>
>
> Example organizations might be: governmental agencies or non-profits
> organizations in the US, United Kingdom, or Europe.
>
>
>
Received on Wednesday, 2 August 2017 21:09:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 2 August 2017 21:09:43 UTC