What ADA Title II Actually Requires of Your Lecture Slides

What ADA Title II Actually Requires of Your Lecture Slides — FP×P Blog

- -

:root { --ink: #0d1b2a; --cream: #f6f1e9; --cream2: #ede7d9; --accent: #e8502a; --teal: #1b8a99; --gold: #c9943a; --light-ink: #3a4f63; --rule: #d4cbba; }

, ::before, *::after { box-sizing: border-box; margin: 0; padding: 0; }

body { background: var(--cream); color: var(--ink); font-family: "Source Serif 4", Georgia, serif; font-size: 18px; line-height: 1.72; }

nav { background: var(--ink); padding: 14px 32px; display: flex; align-items: center; gap: 12px; } nav .brand { color: var(--cream); font-family: "DM Mono", monospace; font-size: 13px; letter-spacing: 0.06em; text-decoration: none; opacity: 0.9; } nav .sep { color: var(--accent); margin: 0 6px; } nav .tag { background: var(--teal); color: #fff; font-family: "DM Mono", monospace; font-size: 11px; letter-spacing: 0.08em; text-transform: uppercase; padding: 3px 10px; border-radius: 2px; margin-left: auto; }

.header-graphic { width: 100%; aspect-ratio: 1200 / 400; max-height: 420px; display: block; overflow: hidden; } .header-graphic svg { width: 100%; height: 100%; display: block; }

.article { max-width: 740px; margin: 0 auto; padding: 56px 24px 80px; }

.meta { display: flex; align-items: center; gap: 14px; margin-bottom: 28px; flex-wrap: wrap; } .meta .category { font-family: "DM Mono", monospace; font-size: 11px; letter-spacing: 0.1em; text-transform: uppercase; color: #0d6b77; background: rgba(27, 138, 153, 0.12); padding: 4px 12px; border-radius: 2px; } .meta .read-time { font-family: "DM Mono", monospace; font-size: 12px; color: var(--light-ink); } .meta .date { font-family: "DM Mono", monospace; font-size: 12px; color: var(--light-ink); margin-left: auto; }

h1 { font-family: "Playfair Display", Georgia, serif; font-size: clamp(28px, 4vw, 40px); font-weight: 700; line-height: 1.15; color: var(--ink); margin-bottom: 20px; letter-spacing: -0.01em; } h1 em { font-style: italic; color: var(--teal); }

.deck { font-size: 20px; color: var(--light-ink); line-height: 1.5; margin-bottom: 36px; border-left: 3px solid var(--teal); padding-left: 18px; }

hr.rule { border: none; border-top: 1px solid var(--rule); margin: 40px 0; }

h2 { font-family: "Playfair Display", serif; font-size: 28px; font-weight: 700; margin: 48px 0 16px; color: var(--ink); line-height: 1.2; } h3 { font-family: "Playfair Display", serif; font-size: 20px; font-weight: 700; margin: 36px 0 10px; color: var(--ink); } p { margin-bottom: 22px; } a { color: var(--teal); } strong { color: var(--ink); font-weight: 600; } sup a { font-size: 0.75em; text-decoration: none; vertical-align: super; } sup a:hover { text-decoration: underline; }

ul, ol { margin: 0 0 22px 0; padding-left: 0; list-style: none; } ul li, ol li { padding-left: 24px; position: relative; margin-bottom: 10px; line-height: 1.6; } ul li::before { content: "\2014"; position: absolute; left: 0; color: var(--teal); font-weight: 600; } ol { counter-reset: ol-counter; } ol li { counter-increment: ol-counter; } ol li::before { content: counter(ol-counter) "."; position: absolute; left: 0; color: var(--teal); font-family: "DM Mono", monospace; font-size: 14px; font-weight: 500; top: 3px; }

.share-card { background: var(--ink); color: var(--cream); border-radius: 8px; padding: 36px 40px; margin: 44px 0; position: relative; overflow: hidden; } .share-card::before { content: ""; position: absolute; top: 0; right: 0; width: 200px; height: 200px; background: radial-gradient( circle at top right, rgba(27, 138, 153, 0.2) 0%, transparent 70% ); pointer-events: none; } .share-card .card-label { font-family: "DM Mono", monospace; font-size: 11px; letter-spacing: 0.12em; text-transform: uppercase; color: var(--teal); margin-bottom: 16px; } .share-card h2 { font-family: "Playfair Display", serif; font-size: 26px; font-weight: 700; line-height: 1.2; margin: 0 0 20px; color: #fff; } .share-card .card-list { list-style: none; display: flex; flex-direction: column; gap: 10px; padding: 0; margin: 0; } .share-card .card-list li { font-family: "DM Mono", monospace; font-size: 14px; display: flex; align-items: flex-start; gap: 10px; color: var(--cream); line-height: 1.5; padding-left: 0; margin-bottom: 0; } .share-card .card-list li::before { content: "\2192"; position: static; color: var(--teal); font-size: 16px; font-weight: 400; flex-shrink: 0; margin-top: 1px; }

.share-buttons { display: flex; gap: 8px; flex-wrap: wrap; margin-top: 16px; } .share-btn { display: inline-flex; align-items: center; gap: 7px; font-family: "DM Mono", monospace; font-size: 12px; letter-spacing: 0.04em; padding: 8px 16px; border-radius: 4px; cursor: pointer; transition: all 0.2s ease; text-decoration: none; } .share-btn:hover { opacity: 0.85; transform: translateY(-1px); } .share-btn-x { background: rgba(246, 241, 233, 0.08); color: var(--cream); border: 1px solid rgba(246, 241, 233, 0.15); } .share-btn-linkedin { background: rgba(246, 241, 233, 0.08); color: var(--cream); border: 1px solid rgba(246, 241, 233, 0.15); } .copy-link-btn { display: inline-flex; align-items: center; gap: 7px; font-family: "DM Mono", monospace; font-size: 12px; letter-spacing: 0.05em; padding: 8px 16px; border-radius: 3px; cursor: pointer; border: 1px solid rgba(246, 241, 233, 0.25); background: rgba(246, 241, 233, 0.15); color: var(--cream); transition: opacity 0.2s, transform 0.15s; } .copy-link-btn.copied { background: rgba(27, 138, 153, 0.3); color: #7ecfda; border-color: rgba(27, 138, 153, 0.4); }

.stat-banner { display: grid; grid-template-columns: repeat(3, 1fr); gap: 2px; margin: 40px 0; border-radius: 8px; overflow: hidden; } .stat-cell { background: var(--ink); padding: 28px 20px; text-align: center; } .stat-cell .num { font-family: "Playfair Display", serif; font-size: 42px; font-weight: 900; color: var(--teal); line-height: 1; margin-bottom: 8px; display: block; } .stat-cell .label { font-family: "DM Mono", monospace; font-size: 12px; letter-spacing: 0.04em; color: #ffffff; line-height: 1.4; }

.requirement-block { border-left: 4px solid var(--teal); background: rgba(27, 138, 153, 0.06); border-radius: 0 6px 6px 0; padding: 24px 28px; margin: 36px 0; } .requirement-block .req-label { font-family: "DM Mono", monospace; font-size: 11px; letter-spacing: 0.1em; text-transform: uppercase; color: var(--teal); margin-bottom: 10px; } .requirement-block p { margin: 0; font-size: 16px; } .requirement-block p + p { margin-top: 14px; }

.callout-box { border: 1px solid rgba(201, 148, 58, 0.35); background: rgba(201, 148, 58, 0.07); border-radius: 6px; padding: 24px 28px; margin: 36px 0; } .callout-box .callout-label { font-family: "DM Mono", monospace; font-size: 11px; letter-spacing: 0.1em; text-transform: uppercase; color: var(--gold); margin-bottom: 10px; } .callout-box p { margin: 0; font-size: 16px; }

.footnotes { margin-top: 56px; padding-top: 32px; border-top: 2px solid var(--rule); } .footnotes .label { font-family: "DM Mono", monospace; font-size: 11px; letter-spacing: 0.12em; text-transform: uppercase; color: var(--light-ink); margin-bottom: 20px; } .footnotes ol { counter-reset: fn-counter; } .footnotes ol li { counter-increment: fn-counter; font-size: 15px; color: var(--light-ink); line-height: 1.6; margin-bottom: 12px; padding-left: 28px; } .footnotes ol li::before { content: counter(fn-counter) "."; position: absolute; left: 0; color: var(--teal); font-family: "DM Mono", monospace; font-size: 13px; top: 3px; }

.cta-block { background: var(--ink); border-radius: 8px; padding: 48px 44px; margin-top: 64px; text-align: center; position: relative; overflow: hidden; } .cta-block::after { content: ""; position: absolute; inset: 0; background: radial-gradient( ellipse at 50% 0%, rgba(27, 138, 153, 0.18) 0%, transparent 65% ); pointer-events: none; } .cta-block h2 { font-family: "Playfair Display", serif; font-size: 28px; font-weight: 700; color: #fff; margin-bottom: 16px; line-height: 1.2; } .cta-block p { font-size: 17px; color: rgba(246, 241, 233, 0.8); max-width: 520px; margin: 0 auto 28px; line-height: 1.6; } .btn { display: inline-flex; align-items: center; gap: 8px; background: var(--teal); color: #fff; font-family: "DM Mono", monospace; font-size: 14px; letter-spacing: 0.04em; padding: 14px 28px; border-radius: 4px; text-decoration: none; transition: all 0.2s ease; position: relative; z-index: 1; } .btn:hover { background: #16717e; transform: translateY(-1px); }

@media (max-width: 600px) { .stat-banner { grid-template-columns: 1fr; } .share-card { padding: 28px 24px; } .cta-block { padding: 36px 24px; } }

FP×P / Vellum Review Faculty Conversations, Over Coffee

- - - - - - - - - - - - - - - - - - - - - - -

4.5:1 contrast ratio

ALT

ADA Title II & Your Slides

Professional Development ⏰ 12 min read May 19, 2026

What ADA Title II Actually Requires of Your Lecture Slides

The 2024 DOJ rule updating ADA Title II explicitly covers digital course materials, not just institutional websites. The standard is WCAG 2.1 Level AA. The compliance deadline for most public institutions passed April 2026. Here is what the rule says and what accessible slides actually look like.

6 WCAG 2.1 AA requirements that apply to every slide deck

4.5:1 minimum contrast ratio for normal text under WCAG 2.1 AA

Apr 2026 compliance deadline for most public institutions under the 2024 rule

★ What this post covers

Six Requirements. One Slide Deck. One Deadline That Has Already Passed.

• What the 2024 DOJ rule says and who it covers

• Why course materials, including PowerPoint files, are in scope

• What WCAG 2.1 AA actually requires of a slide deck

• What a compliance tool checks and what it flags

• What to do if your slides fail an audit

Share on X

Share on LinkedIn

Copy Link

What the 2024 DOJ Rule Actually Says

In April 2024, the Department of Justice published a final rule amending its regulations under Title II of the Americans with Disabilities Act. [1] Title II covers state and local government entities, which includes public colleges and universities. The rule went into effect June 24, 2024.

The practical significance of the rule is twofold. First, it establishes a specific technical standard for web and mobile content: WCAG 2.1 Level AA. Second, it sets compliance deadlines that are now behind us for most institutions.

Compliance Timeline

April 24, 2026: compliance deadline for public entities with a population of 50,000 or more (which covers most public universities and community colleges).

April 26, 2027: compliance deadline for smaller public entities with populations under 50,000.

Before this rule, Title II compliance in the digital space was governed by a patchwork of consent decrees and OCR resolution agreements, each negotiated separately. Institutions could argue that no specific technical standard applied. That argument is no longer available. The rule cites WCAG 2.1 Level AA as the binding standard by name. [2]

WCAG stands for Web Content Accessibility Guidelines. It is a set of technical criteria published by the World Wide Web Consortium (W3C) and maintained through an international working group. Level AA is the middle tier of WCAG: stricter than Level A (minimum) and less demanding than Level AAA (full conformance). For most practical purposes in higher education, WCAG 2.1 AA is now the floor, not a stretch goal.

Private Institutions and Section 504

Title II covers public entities only. Private colleges and universities are not subject to Title II directly, but they are covered by Section 504 of the Rehabilitation Act of 1973, which prohibits disability-based discrimination by any program or activity receiving federal financial assistance. [3] Nearly every private college and university receives federal financial assistance in some form, through student financial aid programs if nothing else.

Section 504 does not cite WCAG 2.1 AA explicitly in its regulations, but OCR has consistently applied WCAG 2.1 AA as the operative standard in enforcement actions and resolution agreements involving private institutions. The practical difference between Title II and Section 504 obligations is smaller than the public/private distinction might suggest.

Why Slides Are in Scope

The most common misconception about the 2024 rule is that it only applies to the institution's public website. Faculty have heard "we need to fix the website" and assumed their teaching materials are somebody else's concern. They are not.

The DOJ rule defines "web content" broadly to include "information and experiences available through the internet," which explicitly covers content on course platforms like Canvas, Blackboard, and Moodle, not just publicly accessible pages. [4] A slide deck uploaded to a course management system, shared as a PDF via email, or posted on a course page is web content under this framework. It is digital content delivered through an institution's information technology infrastructure to students who may have disabilities.

The rule includes specific exceptions: archived content from before a certain date, certain third-party content outside institutional control, and content that poses an undue burden. Course materials created and distributed by faculty are not any of those things. They are produced by the institution's employees, in the performance of institutional duties, for delivery to students. They are squarely in scope.

Worth noting

The rule does include an "undue burden" exception, similar to the one in the original ADA: if compliance would impose a fundamental alteration or undue financial and administrative burden, an entity may document that exception and provide an alternative means of access. This is a high bar and requires documentation. It is not a blanket exemption for slides that predate the rule.

What this means in practical terms: if a student who uses a screen reader is enrolled in your course, and your slides are not accessible, that student cannot access the same course content as their peers. That is a discrimination claim waiting to happen, and it is the factual pattern that drives OCR complaints.

Institutions are also not insulated by the fact that they provide accommodations on request. Reactive accommodation (providing an accessible version after a student discloses a disability and makes a formal request) does not satisfy Title II's proactive compliance obligation. The rule requires that content be accessible by design, not accessible on demand after a request triggers the process.

What WCAG 2.1 AA Means for a PowerPoint

WCAG 2.1 is organized around four principles: content must be perceivable, operable, understandable, and robust. For a slide deck, the practical requirements collapse into six categories that come up in virtually every accessibility audit. Each one is checkable without specialized software, though the process goes faster with a tool.

1. Alt Text on All Images and Charts

Every non-decorative image in your slides, including photographs, charts, graphs, diagrams, and embedded clip art, must have alternative text that conveys the content or function of the image to someone who cannot see it. [5] This is WCAG Success Criterion 1.1.1 (Non-text Content), a Level A requirement that carries over into AA compliance.

Alt text requirements are frequently misunderstood in two directions. The first failure is omitting alt text entirely: the image field in PowerPoint is left blank. The second failure is writing alt text that describes appearance without conveying content ("bar chart image"), or writing alt text that restates the slide title without adding information. Effective alt text for a chart describes what the data shows: "Line graph showing enrollment in public four-year institutions declining 8% between 2010 and 2023." That is the information a screen reader user needs.

Decorative images, such as a purely aesthetic background texture or a divider graphic, should be marked as decorative rather than given alt text. PowerPoint allows this explicitly: right-click the image, select "Edit Alt Text," and check "Mark as decorative." This tells assistive technology to skip the image.

1. Sufficient Color Contrast

WCAG 2.1 AA requires a contrast ratio of at least 4.5:1 between normal text and its background, and at least 3:1 between large text and its background. [6] Large text is defined as 18pt (24px) or larger for regular weight, or 14pt (approximately 18.67px) for bold. Contrast ratio is calculated using a specific formula based on relative luminance values of the foreground and background colors.

The most common contrast failures in slide decks involve colored text on colored backgrounds, white text on medium-saturation backgrounds, and light gray text used for secondary information. A slide using dark teal text on a medium blue background may feel cohesive visually and still fail contrast requirements. Contrast checkers built into PowerPoint's Accessibility Checker flag these automatically, as do browser-based tools such as the WebAIM Contrast Checker.

Brand slides are a specific risk area. Institutional color palettes are often developed without accessibility constraints, particularly at older institutions. If your institution's branded slide template uses colors that fail the contrast requirement, compliant slides will look off-brand. That is a design problem for the communications office to resolve with an accessible brand update, not a reason to ship inaccessible slides.

1. Reading Order

Screen readers navigate slide content based on the order objects appear in the slide's tab order, which is set independently of visual position. A slide where the title appears visually at the top but was added to the slide last may be read by a screen reader in a confusing sequence: body text first, then a chart, then the title.

In PowerPoint, reading order is managed through the Selection Pane (accessible under the Arrange menu or the Accessibility Checker). Objects are listed in the Selection Pane in reverse reading order: the item at the bottom of the list is read first. Common failures include templates that place the title object at a lower position in the stack than the body text, and slides assembled by copying content from multiple sources.

Correcting reading order is tedious in a large deck but not technically difficult. Select the slide, open the Selection Pane, and drag objects to the correct stacking order. The slide title should appear at the top of the reading order (bottom of the Selection Pane).

1. No Information Conveyed by Color Alone

This is WCAG Success Criterion 1.4.1 (Use of Color). Information cannot be communicated exclusively through color: that is, a person who cannot perceive color differences must still be able to understand the content. [7]

The most common failure pattern is a chart where data series are distinguished only by color: "the red line represents 2022 and the blue line represents 2023." A student with red-green color vision deficiency cannot distinguish these series. The fix is to add a secondary differentiator: different line patterns (solid vs. dashed vs. dotted), distinct data point markers (circles vs. squares vs. triangles), or direct data labels. A chart that labels series directly does not rely on color to convey which line is which.

The same principle applies to status indicators (red for fail, green for pass), process diagrams that use color to indicate direction or status, and any other visual encoding where color carries semantic weight.

1. Captions for Embedded Video

If your slides include embedded video clips, those clips must have accurate captions. This is WCAG Success Criterion 1.2.2 (Captions, Prerecorded), a Level A requirement. Auto-generated captions from YouTube or other platforms do not satisfy this requirement unless they have been reviewed and corrected: auto-captions for lecture content routinely produce errors on technical terminology, proper nouns, and accented speech.

Faculty who embed short clips frequently assume captioning is the platform's responsibility. When the clip is embedded in your course materials and you are distributing it to your students as part of your instruction, the accessibility obligation follows the distribution, not the original platform.

1. Heading Structure

Slide titles should be formatted as actual headings in the document's accessibility tree, not as plain text boxes styled to look like titles. In PowerPoint, this means using the designated title placeholder on each slide, not adding a text box and making it look like a title. The designated title placeholder is exposed as a heading to assistive technology; a styled text box is not.

Slides without titles, or slides where the same title is reused across multiple slides with different content (for example, multiple slides all titled "Continued"), create navigation problems for screen reader users, who rely on slide titles to move through a presentation and understand where they are. Every slide should have a unique, descriptive title. If a sequence of slides covers a single topic, the titles can be: "Active Learning: Definition," "Active Learning: Research Base," "Active Learning: Application," rather than "Active Learning" repeated three times.

What a Compliance Audit Checks

PowerPoint's built-in Accessibility Checker (Review menu, then Check Accessibility) performs a subset of WCAG checks and is a reasonable first pass. It catches missing alt text, slides without titles, and some reading order issues. It does not check color contrast directly, does not evaluate whether captions are accurate (only whether they exist), and does not assess whether information is being conveyed by color alone.

For a more complete picture, slides can be exported to PDF and evaluated with a PDF accessibility checker, or uploaded to a tool that applies WCAG 2.1 AA criteria systematically.

What the FPxP audit tool flags

The FPxP compliance checker runs a WCAG 2.1 AA scan of uploaded slides and returns a report with specific failure locations. Flags include: missing or empty alt text, detected contrast failures below the 4.5:1 threshold, slides with no title element, and common reading-order anomalies. It does not evaluate caption accuracy (that requires human review) or assess color-only encoding (which requires content interpretation). The scan runs in under 30 seconds. No account required.

A compliance audit is not a one-time event. Slides change every semester. New images are added, data is updated, charts are revised. A department that establishes a regular audit cycle, whether individual faculty running the tool before each course launch or a centralized instructional design review, is in a fundamentally different position than one that relies on individual good intentions.

One pattern that complicates audit efficiency: slide decks assembled from multiple sources accumulate accessibility failures from each source. Faculty who build slides by combining content from colleagues, institutional templates, textbook publishers' slides, and their own additions are inheriting the accessibility decisions (or failures) of each contributor. Auditing before distribution is the only reliable way to catch cross-source failures.

What to Do If Your Slides Fail

The most useful response to an accessibility audit is triage by frequency and severity, not a commitment to fix everything at once. Most slide decks that have not been designed with accessibility in mind will have multiple failure types. The question is where to start.

Priority 1: Missing Alt Text and Slide Titles

These are the highest-impact failures because they affect all screen reader users completely, not partially. A slide with no title cannot be navigated by title. An image with no alt text conveys nothing to a screen reader user. These are also the fastest fixes: alt text is added by right-clicking an image, slide titles by clicking into the title placeholder. A deck of forty slides with missing alt text on twelve images and three untitled slides can often be remediated in under an hour.

Priority 2: Color Contrast

Contrast failures are addressed by changing text or background color values. If your slides use a branded color palette, this requires choosing compliant alternatives that approximate the brand intent. Run any candidate colors through a contrast checker before committing. There are browser extensions and desktop applications that let you sample colors from any open document and calculate contrast ratios in real time.

If a significant portion of your slides fail contrast checks because of an institutional template, bring this to your instructional design or communications office with the specific color values and failure data. That is a more productive conversation than individual faculty redesigning brand slides on their own.

Priority 3: Reading Order and Color-Only Encoding

Reading order corrections are mechanical but time-consuming in a large deck. Consider fixing these systematically on your core lecture slides: the slides you reuse each semester. Single-use slides that are never redistributed or archived are lower priority.

Color-only encoding in charts and diagrams often requires redesigning the visual itself, not just adding descriptive text. If you are using chart templates from a data visualization tool, check whether the tool has an accessible palette option. Many do, and switching the palette is a single setting change.

Building Accessible Slides from the Start

Retroactive remediation is more expensive than accessible design from the beginning. For faculty who are revising or rebuilding a course, the leverage is in the template: start with a slide template that has been verified for contrast compliance, uses the designated title placeholder on every slide, and has an accessible layout structure. Every slide built on that template starts with most of the compliance work already done.

Many instructional design offices have developed or can develop accessible slide templates for faculty use. If yours has not, this is worth requesting. The cost of building one good template is almost always less than the cost of remediating dozens of individual decks.

Microsoft's own accessibility documentation for PowerPoint has improved substantially and is a reliable procedural reference. [8] The steps for checking and setting alt text, adjusting reading order, and adding slide titles are documented with screenshots for current versions of PowerPoint on both Windows and macOS.

A note on the legal environment

OCR complaint volume related to digital accessibility in higher education has increased year over year since 2020. Resolution agreements typically require institutions to audit existing content, develop remediation plans with timelines, train faculty, and implement ongoing accessibility review processes. The compliance burden imposed by a resolution agreement is significantly higher than the burden of proactive compliance. Faculty-level awareness of the requirements is one part of what makes proactive compliance possible.

The 2024 DOJ rule did not create new obligations so much as it clarified and standardized obligations that were already present in Title II and Section 504. What changed is the specificity: WCAG 2.1 AA is now the named standard, the deadlines are fixed, and the definition of web content is broad enough to capture course materials. Slide decks that cannot be used by students with disabilities are not a technical edge case. They are an access problem with a legal framework around it.

The six requirements covered here, alt text, color contrast, reading order, no color-only encoding, captions, and heading structure, are the places to start. Each one is fixable with existing tools and a working knowledge of the specification. The specification exists, it is public, and it is precise.

References

- U.S. Department of Justice. (2024).

Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities.

Federal Register, 89 (80), 31320–31474. 28 CFR Part 35.

- World Wide Web Consortium. (2018).

Web Content Accessibility Guidelines (WCAG) 2.1.

W3C Recommendation. Retrieved May 2026.

- Rehabilitation Act of 1973, Section 504, 29 U.S.C. § 794. See also U.S. Department of Education, Office for Civil Rights,

Frequently Asked Questions about Section 504 and the Education of Children with Disabilities.

- 28 CFR § 35.104 (definition of "web content"); 28 CFR § 35.200 (scope of requirements). The preamble to the 2024 rule discusses the application to learning management systems and course materials. Federal Register, 89 (80), 31338–31341.

- WCAG 2.1 Success Criterion 1.1.1 (Non-text Content). In: World Wide Web Consortium. (2018).

Web Content Accessibility Guidelines (WCAG) 2.1 § 1.1.1.

- WCAG 2.1 Success Criterion 1.4.3 (Contrast, Minimum). In: World Wide Web Consortium. (2018).

Web Content Accessibility Guidelines (WCAG) 2.1 § 1.4.3.

- WCAG 2.1 Success Criterion 1.4.1 (Use of Color). In: World Wide Web Consortium. (2018).

Web Content Accessibility Guidelines (WCAG) 2.1 § 1.4.1.

- Microsoft Support. (2024).

Make your PowerPoint presentations accessible to people with disabilities.

Microsoft Corporation.

Check your slides before your students do.

The FPxP compliance checker runs a WCAG 2.1 AA scan of your slides in 30 seconds. No account required.

Run the Compliance Check →

function shareOnX() { var url = window.location.href; var title = document.title.split(" — ")[0]; window.open( "https://twitter.com/intent/tweet?url=" + encodeURIComponent(url) + "&text=" + encodeURIComponent(title), "_blank", "width=550,height=420" ); } function shareOnLinkedIn() { var url = window.location.href; window.open( "https://www.linkedin.com/sharing/share-offsite/?url=" + encodeURIComponent(url), "_blank", "width=550,height=420" ); } function copyLink() { var url = window.location.href; if (navigator && navigator.clipboard) { navigator.clipboard.writeText(url).then(function () { var btns = document.querySelectorAll(".copy-link-btn"); btns.forEach(function (btn) { btn.classList.add("copied"); var label = btn.querySelector("span"); if (label) label.textContent = "Copied!"; }); setTimeout(function () { btns.forEach(function (btn) { btn.classList.remove("copied"); var label = btn.querySelector("span"); if (label) label.textContent = "Copy Link"; }); }, 2200); }); } }