From 5e82da63699b9072d6dab88e4ac90a0304509c03 Mon Sep 17 00:00:00 2001 From: Ned Zimmerman Date: Mon, 24 Jun 2024 12:00:38 -0300 Subject: [PATCH 1/2] chore: add WCAG reporter article --- ...ible-framework-for-wcag-audit-reporting.md | 27 +++++++++++++++++++ ...ating-static-content-management-systems.md | 2 +- 2 files changed, 28 insertions(+), 1 deletion(-) create mode 100644 src/collections/news/2024-06-24-developing-an-accessible-framework-for-wcag-audit-reporting.md diff --git a/src/collections/news/2024-06-24-developing-an-accessible-framework-for-wcag-audit-reporting.md b/src/collections/news/2024-06-24-developing-an-accessible-framework-for-wcag-audit-reporting.md new file mode 100644 index 00000000..5f4cacf8 --- /dev/null +++ b/src/collections/news/2024-06-24-developing-an-accessible-framework-for-wcag-audit-reporting.md @@ -0,0 +1,27 @@ +--- +title: Developing an Accessible Framework for WCAG Audit Reporting +date: "2024-06-24" +excerpt: Developing an accessible, web-based framework to support our accessibility auditing workflow. +--- +The IDRC often conducts formal or informal audits of websites for accessibility under the [Web Content Accessibility Guidelines](https://hidde.blog/introducing-an-eleventy-starter-project-for-wcag-reports/), +both internally and as part of our accessibility consulting work. + +We've used a variety of tools to document the results of these audits over the years. Recently, building on our work +with [static websites and content management systems for them](https://floeproject.org/news/mon-jun-24-2024-00-00-00-gmt-0000-coordinated-universal-time-evaluating-static-content-management-systems/), +we've begun developing an [Eleventy](https://11ty.dev/)-based WCAG auditing tool based on work by [Hidde de Vries](https://hidde.blog/introducing-an-eleventy-starter-project-for-wcag-reports/). + +Hidde's [eleventy-wcag-reporter](https://github.com/hidde/eleventy-wcag-reporter) project provides a fantastic +accessible starter kit for Eleventy which lets you add multiple audits to a single Eleventy site, generates an +overview of compliance with WCAG success criteria, and lets you create detailed issues with screenshots, code +samples and reference links. We've worked to adapt his tool to our workflow, adding some new features including: + +- A content management system (CMS) to allow non-developers to easily file issues and complete report details +- Automatic import of WCAG success criteria from the W3C's data repository to maintain an up-to-date list within + the tool itself +- A detailed table indicating support for individual success criteria +- The ability to convert issues in an audit report into issues on GitHub or GitLab with a single click +- The ability to generate an accessible PDF of the audit report as part of the build process + +The [IDRC WCAG Reporter](https://github.com/inclusive-design/idrc-wcag-reporter) is in active development. We're +grateful to Hidde for his initial work on this tool and we're looking forward to sharing our version more widely in the +months to come as we integrate it into our accessibility auditing workflow. diff --git a/src/collections/news/2024-06-24-evaluating-static-content-management-systems.md b/src/collections/news/2024-06-24-evaluating-static-content-management-systems.md index b5de65a0..c2df96bb 100644 --- a/src/collections/news/2024-06-24-evaluating-static-content-management-systems.md +++ b/src/collections/news/2024-06-24-evaluating-static-content-management-systems.md @@ -1,6 +1,6 @@ --- title: Evaluating Static Content Management Systems -date: 2024-06-24 +date: "2024-06-24" excerpt: Adopting an accessible, flexible content management system for our static websites. --- The IDRC has embraced the use of simple, static websites for many of our projects including FLOE over the last four From 61545c93f45d8882c4fd3868bba375a5f6a289d2 Mon Sep 17 00:00:00 2001 From: Ned Zimmerman Date: Mon, 24 Jun 2024 12:01:05 -0300 Subject: [PATCH 2/2] fix: bad link --- ...veloping-an-accessible-framework-for-wcag-audit-reporting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/collections/news/2024-06-24-developing-an-accessible-framework-for-wcag-audit-reporting.md b/src/collections/news/2024-06-24-developing-an-accessible-framework-for-wcag-audit-reporting.md index 5f4cacf8..866c395c 100644 --- a/src/collections/news/2024-06-24-developing-an-accessible-framework-for-wcag-audit-reporting.md +++ b/src/collections/news/2024-06-24-developing-an-accessible-framework-for-wcag-audit-reporting.md @@ -7,7 +7,7 @@ The IDRC often conducts formal or informal audits of websites for accessibility both internally and as part of our accessibility consulting work. We've used a variety of tools to document the results of these audits over the years. Recently, building on our work -with [static websites and content management systems for them](https://floeproject.org/news/mon-jun-24-2024-00-00-00-gmt-0000-coordinated-universal-time-evaluating-static-content-management-systems/), +with [static websites and content management systems for them](https://floeproject.org/news/2024-06-24-evaluating-static-content-management-systems/), we've begun developing an [Eleventy](https://11ty.dev/)-based WCAG auditing tool based on work by [Hidde de Vries](https://hidde.blog/introducing-an-eleventy-starter-project-for-wcag-reports/). Hidde's [eleventy-wcag-reporter](https://github.com/hidde/eleventy-wcag-reporter) project provides a fantastic