<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Accessibility on Coach Alan</title><link>https://alanpruitt.com/tags/accessibility/</link><description>Recent content in Accessibility on Coach Alan</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 25 Aug 2026 16:53:00 -0700</lastBuildDate><atom:link href="https://alanpruitt.com/tags/accessibility/index.xml" rel="self" type="application/rss+xml"/><item><title>Curriculum-as-Code, ADA Title II Compliance, and Fleet-Wide Accessibility Refactoring</title><link>https://alanpruitt.com/essays/essay-27/</link><pubDate>Tue, 25 Aug 2026 16:53:00 -0700</pubDate><guid>https://alanpruitt.com/essays/essay-27/</guid><description>&lt;p&gt;When the Department of Justice codified WCAG 2.1 AA standards under ADA Title II for public higher education institutions, it ended the era of reactive, page-by-page accessibility audits. Traditional post-publication fixes inside LMS rich text editors fail to scale across multi-section course fleets.&lt;/p&gt;&#10;&lt;p&gt;Achieving sustainable compliance requires moving accessibility upstream into a version-controlled engineering workflow: &lt;strong&gt;Curriculum-as-Code&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;hr&gt;&#10;&lt;h2 id="the-upstream-accessibility-pipeline"&gt;The Upstream Accessibility Pipeline&lt;/h2&gt;&#10;&lt;p&gt;By authoring instructional materials in standardized Markdown and validating them through automated linting pipelines before deployment, entire categories of accessibility errors are eliminated at the source.&lt;/p&gt;</description></item><item><title>Essay 26</title><link>https://alanpruitt.com/essays/26-curriculum-as-code-pour-audit-framework/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://alanpruitt.com/essays/26-curriculum-as-code-pour-audit-framework/</guid><description>An analysis of the POUR-Audit framework within Curriculum-as-Code paradigms, highlighting automated verification checks for heading hierarchies, image alt-text, and legacy reference deprecation.</description></item><item><title>Essay 17: Engineering Resilience: Resolving False-Positive Contrast Errors and Array Parsing Script Failures via Curriculum-as-Code</title><link>https://alanpruitt.com/essays/17-resolving-array-parsing-script-failures/</link><pubDate>Fri, 14 Aug 2026 00:00:00 +0000</pubDate><guid>https://alanpruitt.com/essays/17-resolving-array-parsing-script-failures/</guid><description>&lt;!-- =========================================================================&#10; LANG: ENGLISH&#10; ========================================================================= --&gt;&#10;&lt;div data-lang="en"&gt;&#10;&lt;h2 id="essay-17-engineering-resilience-resolving-false-positive-contrast-errors-and-array-parsing-script-failures-via-curriculum-as-code"&gt;Essay 17: Engineering Resilience: Resolving False-Positive Contrast Errors and Array Parsing Script Failures via Curriculum-as-Code&lt;/h2&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; Automated accessibility checkers in Learning Management Systems often flag false-positive contrast errors due to array parsing script failures caused by deeply nested, visual-editor HTML bloat. Curriculum-as-Code (C-a-C) resolves this at the source by replacing GUI color adjustments with deterministic Markdown pipelines, native semantic hierarchies starting at &lt;code&gt;&amp;lt;h2&amp;gt;&lt;/code&gt;, and zero inline color overrides.&lt;/p&gt;</description></item></channel></rss>