From 73e40f5ed0a93015327786621c49a0852d99e91a Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:40:25 +0100 Subject: [PATCH 01/17] Update agile.md http to https --- pages/agile.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/agile.md b/pages/agile.md index d366d607..3525f354 100644 --- a/pages/agile.md +++ b/pages/agile.md @@ -6,7 +6,7 @@ permalink: /agile --- ## We are Agile -CivicActions Accessibility is an [agile project](http://agilemanifesto.org/). We use a [project board](https://github.com/CivicActions/accessibility/projects) to iteratively make progress on our goals, collaborate on issues, have open discussions, deliver a [working site](https://accessibility.civicactions.com/) and respond to the changes that happen constantly in the world of accessibility. +CivicActions Accessibility is an [agile project](https://agilemanifesto.org/). We use a [project board](https://github.com/CivicActions/accessibility/projects) to iteratively make progress on our goals, collaborate on issues, have open discussions, deliver a [working site](https://accessibility.civicactions.com/) and respond to the changes that happen constantly in the world of accessibility. ## Accessibility and Agile We encourage accessibility in every part of agile processes. Examples, adding inclusive user archetypes to design sprints, adding accessibility tests to the definition of done, demonstrating how a product is accessible in sprint reviews, prioritizing accessibility goals in retrospectives, delivering accessible product increments, and much more. From 6c59e8ceb0e05ee6d7c1c686d83f0332ac38f2fb Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:42:07 +0100 Subject: [PATCH 02/17] Update plain-language.md http to https --- _guide/plain-language.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_guide/plain-language.md b/_guide/plain-language.md index 60900370..52145c02 100644 --- a/_guide/plain-language.md +++ b/_guide/plain-language.md @@ -68,7 +68,7 @@ Use bulleted lists to make content easy to scan. Remember: website users don't r ### Test your content with a readability tool -Always run your content through a readability tool. You can use [Hemingway App](http://www.hemingwayapp.com/), [Readable.io](https://readable.io/), or [turn on Flesch-Kincaid](https://support.microsoft.com/en-us/topic/get-your-document-s-readability-and-level-statistics-85b4969e-e80a-4777-8dd3-f7fc3c8b3fd2) if editing in Microsoft Word. Try to get the reading grade level lower than 8th grade. Before using the tool, remember to remove: +Always run your content through a readability tool. You can use [Hemingway App](https://www.hemingwayapp.com/), [Readable.io](https://readable.io/), or [turn on Flesch-Kincaid](https://support.microsoft.com/en-us/topic/get-your-document-s-readability-and-level-statistics-85b4969e-e80a-4777-8dd3-f7fc3c8b3fd2) if editing in Microsoft Word. Try to get the reading grade level lower than 8th grade. Before using the tool, remember to remove: * proper nouns * titles From 045425c3b79b34ef50f5b43bbc6efce93fab11fd Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:42:55 +0100 Subject: [PATCH 03/17] Update checklists.md http 2 https --- _playbook/checklists.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_playbook/checklists.md b/_playbook/checklists.md index 54762ec2..c715db7c 100644 --- a/_playbook/checklists.md +++ b/_playbook/checklists.md @@ -31,7 +31,7 @@ One could also look to use a tool like WebAim's WAVE, ANDI, or Tota11y to scan a * See if the alt text effectively describes the images on the page. * Ensure that there is sufficient color contrast. * Do keyboard only testing (using just tab, shift-tab, arrow keys & escape) to navigate the page. -* Evaluate page for plain language using free tools like the [HemingwayApp](http://www.hemingwayapp.com/). +* Evaluate page for plain language using free tools like the [HemingwayApp](https://www.hemingwayapp.com/). * Magnify the page up to 200% and look for usability and readability issues. There are lots of checklists, rotating through a few of them will help give different people different things to think about accessibility: From 901ac41ad4001e7687b1450ec26fb5a096e1b035 Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:43:27 +0100 Subject: [PATCH 04/17] Update roles.md http 2 https --- _playbook/roles.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_playbook/roles.md b/_playbook/roles.md index 6342fbad..4a4a4eff 100644 --- a/_playbook/roles.md +++ b/_playbook/roles.md @@ -56,7 +56,7 @@ We've taken these lists, added other roles that we didn't see included and inclu ## Content Author / Writer * See: [USA: Accessibility for content designers](https://accessibility.digital.gov/content-design/getting-started/) * W3C WAI - [ARRM Project: Accessibility Roles and Responsibilities Mapping](https://www.w3.org/WAI/EO/wiki/Content_Author_Responsibilities_Mapping). -* **Tools:** [Sa11y](https://ryersondmp.github.io/sa11y/), [Editoria11y](https://itmaybejj.github.io/editoria11y/), [retextjs](https://github.com/retextjs) and [HemingwayApp](http://www.hemingwayapp.com/) +* **Tools:** [Sa11y](https://ryersondmp.github.io/sa11y/), [Editoria11y](https://itmaybejj.github.io/editoria11y/), [retextjs](https://github.com/retextjs) and [HemingwayApp](https://www.hemingwayapp.com/) * Checklist: * Does the content meet your readability target? * Are there any [unusual words](https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#unusual-words) to watch for? From 5c2b68f04b97a6069da502d7b5074058d9639390 Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:45:10 +0100 Subject: [PATCH 05/17] Update resources.md http 2 https --- _guide/resources.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_guide/resources.md b/_guide/resources.md index 0ffc8856..a1ba1e0e 100644 --- a/_guide/resources.md +++ b/_guide/resources.md @@ -20,7 +20,7 @@ General and digital-specific accessibility books we recommend. * [Agile Accessibility Explained](https://www.amazon.com/Agile-Accessibility-Explained-sustainable-development/dp/1689182733/ref=sr_1_2?dchild=1&keywords=Agile+Accessibility+Explained&qid=1615337578&sr=8-2) Dylan Anthony Barrell * [Design for Real Life](https://abookapart.com/products/design-for-real-life) - Sara Wachter-Boettcher and Eric Meyer * [Designing Connected Content: Plan and Model Digital Products for Today and Tomorrow](https://www.amazon.com/Designing-Connected-Content-Products-Tomorrow/dp/0134763386) - Mike Atherton -* [End of Average](http://www.toddrose.com/endofaverage) - Todd Rose +* [End of Average](https://www.toddrose.com/endofaverage) - Todd Rose * [Inclusive Design for a Digital World: Designing with Accessibility in Mind](https://www.amazon.com/Inclusive-Design-Digital-World-Accessibility/dp/148425015X) - Regine M. Gilbert * [Inclusive Design Patterns](https://www.amazon.com/Inclusive-Design-Patterns-Heydon-Pickering-ebook/dp/B01MAXK8XR) - Heydon Pickering * [Mismatch: How Inclusion Shapes Design](https://mitpress.mit.edu/books/mismatch) - Kat Holmes @@ -42,7 +42,7 @@ General and digital-specific accessibility books we recommend. * [A11yweekly.com](https://a11yweekly.com/) by David A. Kennedy * [Accessibility Matters Newsletter](https://www.accessibilityassociation.org/content.asp?contentid=167) - by the IAAP * [Microassist's Accessibility in the News](https://www.microassist.com/digital-access/news/) - by Jack McElaney -* More available from [WebAxe who maintains a terrific list](http://www.webaxe.org/digital-accessibility-newsletters/) +* More available from [WebAxe who maintains a terrific list](https://www.webaxe.org/digital-accessibility-newsletters/) ## Podcasts {#podcasts} From 23d3ad0890ecfbcaa6f0f2b57cc41635fe6d1c3e Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:49:03 +0100 Subject: [PATCH 06/17] Update tools.md http 2 https removing out of date application --- _guide/tools.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/_guide/tools.md b/_guide/tools.md index 490abebd..144ec036 100644 --- a/_guide/tools.md +++ b/_guide/tools.md @@ -13,7 +13,7 @@ Digital accessibility tools. ## Authoring {#authoring} -* [A11yFirst for CKEditor](http://a11yfirst.web.illinois.edu/) - [Accessibility First on GitHub](https://github.com/a11yfirst/distribution) \ +* [A11yFirst for CKEditor](https://a11yfirst.web.illinois.edu/) - [Accessibility First on GitHub](https://github.com/a11yfirst/distribution) \ Series of plugins for supporting a11y best practices within the WYSIWYG editor, CKEditor. * [Sa11y, the accessibility quality assurance assistant](https://sa11y.netlify.app/) \ @@ -26,7 +26,7 @@ A plugin for [retext](https://github.com/retext-project/retext) that scans text Another plugin for [retext](https://github.com/retext-project/retext) that checks text content for possible insensitive, inconsiderate language. * [Zettlr: Markdown Editor](https://www.zettlr.com/) - [Zettlr on GitHub](https://github.com/Zettlr/Zettlr) \ Open source Markdown editor that simplifies the content creation experience by avoiding the clutter seen in many common word processing solutions. -* [Drupal](http://drupal.org/) is a very accessible CMS and [these modules can enhance its accessibility](https://accessibility.civicactions.com/guide/resources#drupal-accessibility-modules) +* [Drupal](https://drupal.org/) is a very accessible CMS and [these modules can enhance its accessibility](https://accessibility.civicactions.com/guide/resources#drupal-accessibility-modules) * [ATOM Plugin - web-accessibility-checker package](https://atom.io/packages/web-accessibility-checker) An accessibility \ Plugin for the popular open source ATOM Editor from GitHub. @@ -77,11 +77,11 @@ This tool runs a set of tests against a set of URLs to verify whether each one m Extremely flexible and popular testing suite from Google that can be run directly on pages, from the command line, or as a Node module. * [IBM Equal Access Toolkit](https://www.ibm.com/able/toolkit/) - [equal-access on GitHub](https://github.com/IBMa/equal-access) \ Tools from IBM that can automate accessibility testing from a browser, or when added to a continuous integration environment. -* [Explore ARIA Landmarks Browser Extension](http://matatk.agrip.org.uk/landmarks/) - [Landmarks on GitHub](https://github.com/matatk/landmarks) \ +* [Explore ARIA Landmarks Browser Extension](https://matatk.agrip.org.uk/landmarks/) - [Landmarks on GitHub](https://github.com/matatk/landmarks) \ Browser extension that allows you to navigate a web page via WAI-ARIA landmarks, using the keyboard or a pop-up menu. * [Firefox AInspector WCAG](https://addons.mozilla.org/en-US/firefox/addon/ainspector-wcag/) - A Firefox Add-on that addresses accessibility compliance \ using OpenAjax Alliance rulesets. -* [Qualweb](http://qualweb.di.fc.ul.pt/evaluator/) - [Qualweb on GitHub](https://github.com/qualweb) - A set of tools that are being built to align with the W3C's ACT ruleset. +* [Qualweb](https://qualweb.di.fc.ul.pt/evaluator/) - [Qualweb on GitHub](https://github.com/qualweb) - A set of tools that are being built to align with the W3C's ACT ruleset. ## Bookmarklets {#bookmarklets} @@ -110,7 +110,7 @@ Evaluate WAI-ARIA according to the [ARIA in HTML](https://www.w3.org/TR/html-ari Allows for testing of contrast of text on top of a semi transparent background. * [Contrast Checker](https://contrast-checker.glitch.me/) - [Contrast Checker on Glitch](https://glitch.com/edit/#!/contrast-checker?path=server.js%3A1%3A0) * [ButtonBuddy](https://buttonbuddy.dev/) - [ButtonBuddy on GitHub](https://github.com/5t3ph/buttonbuddy) -* [ACD (Previously ColorCube)](http://accessiblecolor.design) - [ColorCube on GitHub](https://github.com/oomphinc/colorcube) +* [ACD (Previously ColorCube)](https://accessiblecolor.design) - [ColorCube on GitHub](https://github.com/oomphinc/colorcube) * [LeonardoColor.io](https://leonardocolor.io/#) - [Leonardo on GitHub](https://github.com/adobe/leonardo) * [Colour Contrast Checker](https://colourcontrast.cc) - [Colour Contrast Checker on GitHub](https://github.com/Pushedskydiver/Colour-Contrast-Checker) * [Who Can Use](https://whocanuse.com/) - [Who Can Use on GitHub](https://github.com/CoreyGinnivan/whocanuse) @@ -169,13 +169,11 @@ Testing with [Nightwatch](https://nightwatchjs.org/) on GitHub Simulates color blindness, low vision, dyslexia and more. * [Funkify Chrome Extension](https://www.funkify.org/) \ Not open source, but a free version is available which simulates dyslexia and cognitive/motor/vision conditions. -* [ChromeLens Extension](http://chromelens.xyz/) - [ChromeLens on GitHub](https://github.com/chromelens/chromelens) \ -Chrome extension that offers vision simulators, testing, and a tab focus order visualizer. * [Sim Daltonism](https://michelf.ca/projects/sim-daltonism/) - [sim-daltonism on GitHub](https://github.com/michelf/sim-daltonism/) \ iOS/Mac app that lets you visualize colors as they are perceived with various types of color blindness. * [A11Y: Color blindness empathy test](https://vinceumo.github.io/A11Y-Color-Blindness-Empathy-Test/) [on GitHub](https://github.com/vinceumo/A11Y-Color-Blindness-Empathy-Test-browser-extensions) Chrome/Firefox extension and a web-based tool created to help designers and developers better understand color blindness and visual imparity. -* [Color Oracle](http://colororacle.org/) - [Oracle-Mac on GitHub](https://github.com/nvkelso/color-oracle) & [Oracle-Windows on GitHub](https://github.com/nvkelso/color-oracle-java) \ +* [Color Oracle](https://colororacle.org/) - [Oracle-Mac on GitHub](https://github.com/nvkelso/color-oracle) & [Oracle-Windows on GitHub](https://github.com/nvkelso/color-oracle-java) \ Color blindness simulator for Windows, Mac, and Linux. ## EPUB3 {#epub} From b760c9865956dc25e92bc4aa7af7d6181cbe6662 Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:50:08 +0100 Subject: [PATCH 07/17] Update automated-testing.md http to https --- _playbook/automated-testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_playbook/automated-testing.md b/_playbook/automated-testing.md index 5e1b631f..d05c90d8 100644 --- a/_playbook/automated-testing.md +++ b/_playbook/automated-testing.md @@ -31,7 +31,7 @@ Government Digital Services in both the [United Kingdom](https://github.com/alph However, it is important to note that, no matter the tool, [automated testing only catches about one third of accessibility issues](https://alphagov.github.io/accessibility-tool-audit/), so it cannot be relied upon to determine if a site complies. To better ensure that their digital tools are accessible to keyboard-only and assistive technology users, automated tests need to be done along with a robust manual testing plan. List of popular automated testing tools -* [Wave](http://wave.webaim.org/extension/) +* [Wave](https://wave.webaim.org/extension/) * [Tenon](https://tenon.io/) * [SiteImprove](https://chrome.google.com/webstore/detail/siteimprove-browser-exten/amoojkmllfodlpgmdnclkgdnejgpeada) * [See more tools in our guide](/guide/tools) From dbfd34742f28c4b51036fcfa01285542ab6e9682 Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:51:10 +0100 Subject: [PATCH 08/17] Update checklists.md http 2 https --- _playbook/checklists.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_playbook/checklists.md b/_playbook/checklists.md index c715db7c..6db3f576 100644 --- a/_playbook/checklists.md +++ b/_playbook/checklists.md @@ -43,7 +43,7 @@ There are lots of checklists, rotating through a few of them will help give diff * [Elsevier's WCAG 2.1 Checklist](https://romeo.elsevier.com/accessibility_checklist/) * [A11yProject](https://www.a11yproject.com/checklist/) * [Heydon Works](https://github.com/Heydon/inclusive-design-checklist) -* [VoxMedia](http://accessibility.voxmedia.com/) +* [VoxMedia](https://accessibility.voxmedia.com/) * [PSU](https://accessibility.psu.edu/checklist/) * [Yale](https://usability.yale.edu/web-accessibility/articles/wcag2-checklist) * [University of Washington](https://www.washington.edu/accessibility/checklist/) From 6363516f5af216d415e14b14ce7844bae4c7ff1c Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:54:23 +0100 Subject: [PATCH 09/17] Update design.md clean up improving urls --- _guide/design.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_guide/design.md b/_guide/design.md index da31481a..09b55923 100644 --- a/_guide/design.md +++ b/_guide/design.md @@ -47,14 +47,14 @@ Worldwide, government website design is being led by open source initiatives. * [Okta's Odyssey Design System](https://github.com/okta/odyssey) * [IBM's Carbon open source design system](https://www.carbondesignsystem.com/) - [Carbon on GitHub](https://github.com/carbon-design-system/carbon) [Carbon's Accessibility](https://www.carbondesignsystem.com/guidelines/accessibility/overview/) - Uses Web Components * [Impact Design System](https://demos.creative-tim.com/impact-design-system/index.html) - [Impact Desigh System on GitHub](https://github.com/creativetimofficial/impact-design-system) -* [VMWare's Clarity Design System](https://clarity.design/) - [Clarity on GitHub](https://github.com/vmware/clarity) [Clarity's Accessibility](https://clarity.design/get-started/support/#accessibility-support) - Uses Web Components +* [VMWare's Clarity Design System](https://clarity.design/) - [Clarity on GitHub](https://github.com/vmware/clarity) [Clarity's Accessibility](https://clarity.design/get-started/support/) - Uses Web Components * [Emulsify](https://www.emulsify.info/) - [Emulsify on GitHub](https://github.com/emulsify-ds) [Emulsify's Accessibility](https://docs.emulsify.info/usage/accessibility-testing) * [ING's Lion Design System](https://lion-web-components.netlify.app/?path=/story/*) - [Lion on GitHub](https://github.com/ing-bank/lion) [Lion's Accessibility](https://lion-web.netlify.app/blog/ing-open-sources-lion/#accessibility) - Uses Web Components * [Talend's Coral Design System](https://design.talend.com/) - [Coral on GitHub](https://github.com/Talend/ui/) - Uses React Components * [Orange Digital Accessibility](https://a11y-guidelines.orange.com/en/) - [Orange a11y-guidelines on GitHub](https://github.com/Orange-OpenSource/a11y-guidelines) -* [Google's Material Design](https://material.io/) - [Material on GitHub](https://github.com/material-components) [Material's Accessibility](https://material.io/design/usability/accessibility.html#understanding-accessibility) - Uses Web Components +* [Google's Material Design](https://material.io/) - [Material on GitHub](https://github.com/material-components) [Material's Accessibility](https://material.io/design/usability/accessibility.html) - Uses Web Components * [Adobe's Spectrum](https://spectrum.adobe.com/) - [Spectrum's Inclusive Design](https://spectrum.adobe.com/page/inclusive-design/) - Uses Web Components -* [Microsoft's Fluent](https://www.microsoft.com/design/fluent/#/) [Fluent UI on GitHub](https://github.com/microsoft/fluentui) +* [Microsoft's Fluent](https://www.microsoft.com/design/fluent/) [Fluent UI on GitHub](https://github.com/microsoft/fluentui) * [Bridge Lab's Bold](https://bold.bridge.ufsc.br/en/) - [Bold on GitHub](https://github.com/laboratoriobridge/bold) [Bold's Accessibility](https://bold.bridge.ufsc.br/en/design-guidelines/accessibility/) * [Shopify's Polaris](https://polaris.shopify.com/) - [Polaris on GitHub](https://github.com/topics/shopify-polaris) [Polaris' Accessibility](https://polaris.shopify.com/foundations/accessibility) * [Intuit's Design-systems-cli](https://intuit.github.io/design-systems-cli/) - [Intuit on GitHub](https://github.com/intuit/design-systems-cli) [Quickbooks' Accessibility](https://designsystem.quickbooks.com/bolt/accessibility/) From b8da4c480dadd6c7a8ce9aecbd343b5ed0802177 Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:56:46 +0100 Subject: [PATCH 10/17] Update tools.md cleaning links --- _guide/tools.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_guide/tools.md b/_guide/tools.md index 144ec036..f56841cf 100644 --- a/_guide/tools.md +++ b/_guide/tools.md @@ -108,7 +108,7 @@ Evaluate WAI-ARIA according to the [ARIA in HTML](https://www.w3.org/TR/html-ari * [Contrast Finder by Tanaguru](https://contrast-finder.tanaguru.com/) - [Contrast Finder GitHub Page](https://github.com/Tanaguru/Contrast-Finder) * [Contrast-Ratio.com](https://contrast-Ratio.com) - [Contrast-Ratio GitHub Page](https://github.com/siege-media/contrast-ratio) \ Allows for testing of contrast of text on top of a semi transparent background. -* [Contrast Checker](https://contrast-checker.glitch.me/) - [Contrast Checker on Glitch](https://glitch.com/edit/#!/contrast-checker?path=server.js%3A1%3A0) +* [Contrast Checker](https://contrast-checker.glitch.me/) - [Contrast Checker on Glitch](https://glitch.com/edit/#!/contrast-checker) * [ButtonBuddy](https://buttonbuddy.dev/) - [ButtonBuddy on GitHub](https://github.com/5t3ph/buttonbuddy) * [ACD (Previously ColorCube)](https://accessiblecolor.design) - [ColorCube on GitHub](https://github.com/oomphinc/colorcube) * [LeonardoColor.io](https://leonardocolor.io/#) - [Leonardo on GitHub](https://github.com/adobe/leonardo) From ef25c4f3a9279162de859fa0605703849c4dc757 Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:57:56 +0100 Subject: [PATCH 11/17] Update 2023-02-05-FOSDEM-ccessibility-OpenSource.md cleaning links --- _posts/2023-02-05-FOSDEM-ccessibility-OpenSource.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2023-02-05-FOSDEM-ccessibility-OpenSource.md b/_posts/2023-02-05-FOSDEM-ccessibility-OpenSource.md index 38c64aa7..a1b8ad1e 100644 --- a/_posts/2023-02-05-FOSDEM-ccessibility-OpenSource.md +++ b/_posts/2023-02-05-FOSDEM-ccessibility-OpenSource.md @@ -10,7 +10,7 @@ roles: - Developer --- -I presented on February 5th in the Design track of the conference. The [slides](https://docs.google.com/presentation/d/1lkUM9mkBSgH0-8pf-kDtPp-FxTCxKEaWd7ze8wA3NA0/edit#slide=id.gde6e9fa718_0_3) and [presentation](https://fosdem.org/2023/schedule/event/accessibility_and_open_source/) are available to those who missed it. +I presented on February 5th in the Design track of the conference. The [slides](https://docs.google.com/presentation/d/1lkUM9mkBSgH0-8pf-kDtPp-FxTCxKEaWd7ze8wA3NA0/) and [presentation](https://fosdem.org/2023/schedule/event/accessibility_and_open_source/) are available to those who missed it. My presentation focused on my experience in Drupal. Drupal has been a leader in digital accessibility for over an decade. Working with an open community has allowed us to pioneer some new solutions to common design challenges. Working in the open has allowed us to tap expertise outside of our community and given space for people with disabilities to become involved in a variety of roles. Accessibility best practices make it clear that accessibility needs to be considered at all levels of a project. From 1b5660781f154485bf4cf5825c9e0fe69a42e6ca Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 21:59:47 +0100 Subject: [PATCH 12/17] Update 2021-3-12-government-accessibility-and-the-cms-problem.md cleaning url --- .../2021-3-12-government-accessibility-and-the-cms-problem.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2021-3-12-government-accessibility-and-the-cms-problem.md b/_posts/2021-3-12-government-accessibility-and-the-cms-problem.md index 5f9efc96..796bd59b 100644 --- a/_posts/2021-3-12-government-accessibility-and-the-cms-problem.md +++ b/_posts/2021-3-12-government-accessibility-and-the-cms-problem.md @@ -60,7 +60,7 @@ widespread. **Resources** - * [Presentation Slide Deck](https://docs.google.com/presentation/d/1S_K8VcxJ6_IQJ1dT4YJmq3GsMkWAkCU7kavImugu3KI/edit#slide=id.ga784c5ac4b_0_358) + * [Presentation Slide Deck](https://docs.google.com/presentation/d/1S_K8VcxJ6_IQJ1dT4YJmq3GsMkWAkCU7kavImugu3KI) * [Presentation Overview](https://events.drupal.org/europe2020/sessions/top-cms-tools-are-working-together-build-more-inclusive-world) * [We4Authors](https://accessibilitycluster.com/) * [About Funka](https://www.funka.com/en/about-funka2/) From c3e82b1f4ac1fbf433afcea83ed9486898edd745 Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 22:02:08 +0100 Subject: [PATCH 13/17] Update 2023-02-01-governments-accessibility-opensource.md cleaning up urls --- _posts/2023-02-01-governments-accessibility-opensource.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2023-02-01-governments-accessibility-opensource.md b/_posts/2023-02-01-governments-accessibility-opensource.md index f6986a4d..19d5d714 100644 --- a/_posts/2023-02-01-governments-accessibility-opensource.md +++ b/_posts/2023-02-01-governments-accessibility-opensource.md @@ -11,6 +11,6 @@ roles: - Operations --- -I presented [Governments, accessibility and open source](https://www.meetup.com/inclusive-design-accessibility/events/291069715/) in Utrecht. My [slides are available](https://docs.google.com/presentation/d/1Pm0bVAZwk_NBxeOMvjiTtTXTQBumZjwNgb6MDLDXwSE/edit#slide=id.gde6e9fa718_0_3), and we hope to make the audio available soon. +I presented [Governments, accessibility and open source](https://www.meetup.com/inclusive-design-accessibility/events/291069715/) in Utrecht. My [slides are available](https://docs.google.com/presentation/d/1Pm0bVAZwk_NBxeOMvjiTtTXTQBumZjwNgb6MDLDXwSE), and we hope to make the audio available soon. My talk focused on some of the challenges that governments are facing as they work to modernize and adopt modern digital first practices. In my talk I address Open Government, open source software and Civic Tech. I highlight how digital accessibility is a huge challenge for governments. Often innovation clashes with inclusive design. There is new legislative pressure on governments, and governments are always struggling to do more with less. From a93ed0a05e8023c8f87331ae8ba3c8465962654c Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 22:03:50 +0100 Subject: [PATCH 14/17] Update 2021-05-25-how-we-scale-inclusive-website-content-with-automated-testing-and-open-source-tools.md fixing links --- ...site-content-with-automated-testing-and-open-source-tools.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2021-05-25-how-we-scale-inclusive-website-content-with-automated-testing-and-open-source-tools.md b/_posts/2021-05-25-how-we-scale-inclusive-website-content-with-automated-testing-and-open-source-tools.md index 0faa6152..b8757669 100644 --- a/_posts/2021-05-25-how-we-scale-inclusive-website-content-with-automated-testing-and-open-source-tools.md +++ b/_posts/2021-05-25-how-we-scale-inclusive-website-content-with-automated-testing-and-open-source-tools.md @@ -169,4 +169,4 @@ You should keep tweaking the tools and double-check your content to make sure it * [Readability Check](https://marketplace.visualstudio.com/items?itemName=jemcclin.readabilitycheck). * [status-stats-jbrains package](https://atom.io/packages/status-stats-jbrains). -Thank you to [Michelle Kang](/about/people/michelle-kang), [Marlena Medford](https://civicactions.com/team/marlena-medford), [Luke Fretwell](/about/people/luke-fretwell), and [Mike Gifford](/about/people/mike-gifford) for your support, thoughts, and feedback. +Thank you to Michelle Kang, Marlena Medford, Luke Fretwell, and Mike Gifford for your support, thoughts, and feedback. From ed9848afaf8648d3ef2f4e38774674b1fd4f6509 Mon Sep 17 00:00:00 2001 From: Mike Gifford Date: Thu, 14 Mar 2024 22:04:44 +0100 Subject: [PATCH 15/17] Update 2021-2-5-whitehouse.gov-beginning-an-accessibility-journey.md cleaning urls --- ...021-2-5-whitehouse.gov-beginning-an-accessibility-journey.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2021-2-5-whitehouse.gov-beginning-an-accessibility-journey.md b/_posts/2021-2-5-whitehouse.gov-beginning-an-accessibility-journey.md index c446c658..83d88e01 100644 --- a/_posts/2021-2-5-whitehouse.gov-beginning-an-accessibility-journey.md +++ b/_posts/2021-2-5-whitehouse.gov-beginning-an-accessibility-journey.md @@ -159,7 +159,7 @@ started](https://www.microassist.com/digital-accessibility/the-value-of- digital-accessibility-statements-a-checklist-for-getting-started/). The W3C has an [accessibility statement -generator](https://www.w3.org/WAI/planning/statements/generator/#create) which +generator](https://www.w3.org/WAI/planning/statements/generator) which adds in section for technical information that might help a user better navigate the site. [Disability:IN](https://disabilityin.org/resource/digital- accessibility-statement-best-practices/) and the UK's [Government Digital From 9bfd0b8fb168fa69a07dd1113cab949d0fd9e372 Mon Sep 17 00:00:00 2001 From: Daniel Mundra Date: Fri, 22 Mar 2024 13:26:43 -0700 Subject: [PATCH 16/17] Removing double spaces --- _guide/plain-language.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/_guide/plain-language.md b/_guide/plain-language.md index 52145c02..b7cec524 100644 --- a/_guide/plain-language.md +++ b/_guide/plain-language.md @@ -19,7 +19,7 @@ roles: ## Overview -You worked hard getting your content online. How do you make sure your readers can find, understand and use it? Apply plain language. Clear and direct writing makes your content [accessible](https://www.w3.org/WAI/WCAG21/Understanding/reading-level.html) (it's also the [law](https://www.plainlanguage.gov/law/)!). Plain language also helps people with different cognitive abilities. Or speakers of a non-English language. Or those who rely on audio to listen to text. +You worked hard getting your content online. How do you make sure your readers can find, understand and use it? Apply plain language. Clear and direct writing makes your content [accessible](https://www.w3.org/WAI/WCAG21/Understanding/reading-level.html) (it's also the [law](https://www.plainlanguage.gov/law/)!). Plain language also helps people with different cognitive abilities. Or speakers of a non-English language. Or those who rely on audio to listen to text. You might also be writing for the public. Or a group of experts. Either way, your audience's reading level is likely [lower than you think](https://literacyproj.org/). ## Who this is for @@ -35,7 +35,7 @@ You might also be writing for the public. Or a group of experts. Either way, you Avoid: -* Jargon and government legalese. If you have to use an acronym, spell it out first. +* Jargon and government legalese. If you have to use an acronym, spell it out first. * Filler words. For example, use the word 'analyze' not 'conduct an analysis'. * Repetitive words * Irony or idioms @@ -54,7 +54,7 @@ Before writing, ask yourself: What are your reader's needs? What do they need to ### Make it actionable -People visit your website to do something: answer a question or complete a specific task. Ask yourself: what are the top questions my target reader wants to know? How can I answer it quickly? +People visit your website to do something: answer a question or complete a specific task. Ask yourself: what are the top questions my target reader wants to know? How can I answer it quickly? ### Choose words your reader uses @@ -68,7 +68,7 @@ Use bulleted lists to make content easy to scan. Remember: website users don't r ### Test your content with a readability tool -Always run your content through a readability tool. You can use [Hemingway App](https://www.hemingwayapp.com/), [Readable.io](https://readable.io/), or [turn on Flesch-Kincaid](https://support.microsoft.com/en-us/topic/get-your-document-s-readability-and-level-statistics-85b4969e-e80a-4777-8dd3-f7fc3c8b3fd2) if editing in Microsoft Word. Try to get the reading grade level lower than 8th grade. Before using the tool, remember to remove: +Always run your content through a readability tool. You can use [Hemingway App](https://www.hemingwayapp.com/), [Readable.io](https://readable.io/), or [turn on Flesch-Kincaid](https://support.microsoft.com/en-us/topic/get-your-document-s-readability-and-level-statistics-85b4969e-e80a-4777-8dd3-f7fc3c8b3fd2) if editing in Microsoft Word. Try to get the reading grade level lower than 8th grade. Before using the tool, remember to remove: * proper nouns * titles @@ -88,11 +88,11 @@ Automated readability tools won't catch everything. You'll need to test your con * [Menu labels](https://www.nngroup.com/articles/tree-testing/) and micro-content. Keep your [user goals](https://www.nngroup.com/articles/task-scenarios-usability-testing/) in mind. * Language. Ask your users to read your content out loud. What words do they stumble over? How do they rate the clarity of the language (on a scale from 1 to 5)? -* Understanding. Ask your users to paraphrase what they read. What did they summarize correctly? What did they miss? What did they get wrong? +* Understanding. Ask your users to paraphrase what they read. What did they summarize correctly? What did they miss? What did they get wrong? ## Join a plain language community -* [Digital.gov Plain Language Action and Information Network](https://digital.gov/communities/plain-language/). They promote plain language in all government communications. +* [Digital.gov Plain Language Action and Information Network](https://digital.gov/communities/plain-language/). They promote plain language in all government communications. * [Plain Language Association International LinkedIn](https://www.linkedin.com/groups/158634/). This group advocates for plain language in business, government, and law. ## Find a plain language tool @@ -104,7 +104,7 @@ Automated readability tools won't catch everything. You'll need to test your con ## Get trained in plain language -The Center for Plain Language offers training for federal employees. You can take: +The Center for Plain Language offers training for federal employees. You can take: * An [introductory class](https://www.plainlanguage.gov/training/introductory-classes/) to plain language * A [bootcamp class](https://www.plainlanguage.gov/training/train-the-trainer-bootcamp/) to become a plain language trainer at your organization From 6a6be95399e33e9c74a9eccc2c8c66ff79c0dd06 Mon Sep 17 00:00:00 2001 From: Daniel Mundra Date: Fri, 22 Mar 2024 13:27:57 -0700 Subject: [PATCH 17/17] Replacing contrast checker link --- _guide/tools.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_guide/tools.md b/_guide/tools.md index f56841cf..7bb3cf8c 100644 --- a/_guide/tools.md +++ b/_guide/tools.md @@ -108,7 +108,7 @@ Evaluate WAI-ARIA according to the [ARIA in HTML](https://www.w3.org/TR/html-ari * [Contrast Finder by Tanaguru](https://contrast-finder.tanaguru.com/) - [Contrast Finder GitHub Page](https://github.com/Tanaguru/Contrast-Finder) * [Contrast-Ratio.com](https://contrast-Ratio.com) - [Contrast-Ratio GitHub Page](https://github.com/siege-media/contrast-ratio) \ Allows for testing of contrast of text on top of a semi transparent background. -* [Contrast Checker](https://contrast-checker.glitch.me/) - [Contrast Checker on Glitch](https://glitch.com/edit/#!/contrast-checker) +* [Contrast Checker](https://contrast-checker.netlify.app/) * [ButtonBuddy](https://buttonbuddy.dev/) - [ButtonBuddy on GitHub](https://github.com/5t3ph/buttonbuddy) * [ACD (Previously ColorCube)](https://accessiblecolor.design) - [ColorCube on GitHub](https://github.com/oomphinc/colorcube) * [LeonardoColor.io](https://leonardocolor.io/#) - [Leonardo on GitHub](https://github.com/adobe/leonardo)