The AI Teaching Lab at Penn Carey Law is committed to digital accessibility for the entire Penn Carey Law community and the broader public. This site is built to meet the University of Pennsylvania’s digital accessibility policy and the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.

Conformance target

This site targets WCAG 2.2, Level AA conformance, the standard Penn applies to University websites created or significantly revised after July 1, 2024.

What we do to support accessibility

  • Semantic HTML — every page uses standard landmark elements (<header>, <nav>, <main>, <footer>) so assistive technologies can navigate the structure.
  • Skip-to-content link — keyboard users can bypass the header and jump directly to page content.
  • Visible focus indicators — every interactive element shows a Penn-Red outline on keyboard focus.
  • Contrast — body text and link colors meet or exceed WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text and non-text indicators).
  • Keyboard support — all features, including the search dialog, are operable without a mouse. The dialog traps focus while open and closes with the Escape key.
  • Screen-reader text — external links and icon-only buttons include text for assistive technologies, including a “(opens in new tab)” announcement on links that open externally.
  • Reduced motion — animations and transitions are suppressed for users who set prefers-reduced-motion at the OS level.
  • Plain language — Toolkit and project pages are written for direct, scannable reading.

Known limitations

  • PDF and Word attachments — some legacy documents linked from the site may not be fully accessible. We are migrating these to native web pages as we update them. If you encounter a document you cannot use, contact us using the form below and we will provide an accessible alternative.
  • Embedded video and audio — recordings of past events may not have captions or transcripts. Captions and transcripts are added when we host new recordings; older content is being remediated as resources allow.
  • Third-party tools — some pages embed search functionality (Pagefind) and external content (GitHub repositories, vendor documentation). We choose tools that meet WCAG 2.1 AA where possible, but third-party content may not meet our standard.

How to report a barrier

If you encounter content on this site that is not accessible to you, please contact us. We will work to address the issue and, when possible, provide an accessible alternative within five business days.

When you report a barrier, please include:

  1. The URL of the page where you encountered the problem.
  2. The browser and assistive technology you were using (e.g., “Safari with VoiceOver on macOS 26”).
  3. A short description of what was not working.

Standards and references