The Philosophy: Accessibility as Pedagogical Foundation

“The average learner is a myth; barriers exist in the design of the environment, not the individual.”

In learning experience design (LXD), accessibility is not a compliance checklist or an afterthought added onto a finished interface. It is the core pedagogical foundation. When learning environments assume a single "typical" user, they create artificial friction for diverse learners. When instructional systems are engineered through the framework of Universal Design for Learning (UDL), they provide multiple means of representation, action and expression, and engagement.

This portfolio site functions as a living demonstration of evidence-based instructional design. Eliminating extraneous cognitive load—through accessible color contrast, structured navigational landmarks, scannable hierarchies, and purposeful whitespace—benefits every visitor. In particular, it enables busy hiring managers, talent directors, and search committees to evaluate core competencies and verified evidence quickly and without cognitive fatigue.

Technical Conformance: The POUR Framework (WCAG 2.1 AA)

This website targets full conformance with WCAG 2.1 Level AA standards across the four foundational POUR principles of web accessibility:

Perceivable

Information and user interface components must be presentable to users in ways they can perceive.

  • High-Contrast Color Palette: All body copy meets or exceeds the 4.5:1 contrast threshold (evaluated between 4.82:1 on tinted cards and 15.8:1 on primary page surfaces across the approved Portfolio Palette tokens). Large headings exceed the 3:1 contrast requirement.
  • Dual-Channel Multimedia: Built in accordance with Mayer’s Multimedia Principles. Audio production artifacts and video walkthroughs are paired with synchronized captions, full transcripts, and text descriptions to eliminate sensory bottlenecks.
  • Text Alternatives: All informative visual assets include descriptive alt text. Purely decorative elements are marked with aria-hidden="true" to prevent auditory clutter for screen-reader users.

Operable

Interface components and navigation must be operable by all users across all input methods.

  • 100% Keyboard Operability: Every interactive element—including navigation links, filter buttons, and branching simulation choices—is fully operable using only the keyboard.
  • Visible Focus Indicators: Clear, high-contrast :focus-visible outlines (2px solid with distinct offsets) guarantee visible focus orientation during keyboard navigation.
  • Skip Navigation & Landmarks: A keyboard-accessible skip link (.skip-link) allows users to bypass global navigation directly to the main content. HTML5 landmarks (header, nav, main, footer, section) provide rapid landmark jumps.
  • Roving Tabindex on Tabs: The case study filtering system implements the WAI-ARIA tablist pattern with keyboard arrow wrapping (ArrowLeft / ArrowRight) and Home / End shortcut keys.
  • Touch Target Sizing: All buttons, tabs, and interactive targets meet or exceed minimum 44×44px hit dimensions to accommodate mobile and motor-impaired users.

Understandable

Information and the operation of user interface controls must be intuitive, predictable, and clear.

  • Predictable Layout: Visual layout, heading hierarchies (h1 through h4), and navigation structures remain consistent across the entire domain and across device viewports.
  • Live Status Announcements: Dynamic events (such as filter counts and emitted xAPI statements) communicate concise feedback via screen-reader-only aria-live="polite" status regions without interrupting active reading.
  • Clear Cognitive Chunking: Case studies and capabilities are organized into consistent, structured metadata (Context, Intervention, Metrics & Impact) to maximize clarity and scannability.

Robust

Content must be robust enough that it can be reliably interpreted by a wide variety of user agents, including assistive technologies.

  • Semantic HTML5 Architecture: Built using clean, native semantic HTML5 tags without dependency on heavy frameworks or fragile DOM abstractions.
  • Standardized ARIA Roles: Native HTML elements are prioritized; ARIA attributes (such as role="tablist", role="tab", role="tabpanel", aria-selected, aria-controls, and aria-labelledby) are applied strictly according to W3C specifications.
  • Assistive Tech Compatibility: Engineered for logical reading order, heading navigation, and speech output compatibility with standard assistive technologies (NVDA, JAWS, VoiceOver, and TalkBack) and audited via Google Lighthouse.

Honest Known Limitations & Transparent Alternatives

While all native templates, layouts, and interactive modules built specifically for nicholascates.com are engineered for complete WCAG 2.1 AA conformance, educational technology routinely interfaces with historical platforms and third-party authoring tools.

Third-Party Embedded Learning Containers

Certain legacy authoring packages (e.g., historical SCORM 1.2 / 2004 modules, proprietary LMS demo players, or third-party iframe containers) carry vendor-side keyboard focus traps, fixed pixel dimensions, or screen-reader rendering constraints that cannot be modified directly from this codebase.

The Inclusive Alternative Guarantee: In alignment with Universal Design for Learning, no user is required to interact with a third-party container to access learning evidence. Every embedded artifact or case study is accompanied by complete text alternatives, structural process diagrams, live data schemas, and verifiable impact summaries directly in accessible semantic HTML.