jazxii — home

About

Beautiful and accessible are the same goal.

I’m Jassim M. Shamim — a Digital Accessibility Engineer and creative technologist working at the intersection of deep-tech automation and human-centric design.

Jassim M. Shamim

The story

My work runs on one belief: exceptional digital experiences must be fundamentally inclusive — built that way, not retrofitted or “compliant enough.”

I work as an AI orchestrator for accessibility: I wire up agentic frameworks and large language models that thread WCAG/ADA conformance through the whole delivery pipeline — bridging the build side (SDLC) and the test side (STLC) so accessibility is verified continuously, not bolted on at the end. Less manual audit toil; a faster, more reliable path to inclusive software.

Build · SDLC

  1. Plan
  2. Build
  3. Ship
AI orchestrationADA · WCAG woven in

Test · STLC

  1. Strategy
  2. Execute
  3. Verify
AI orchestration bridges the build (SDLC) and test (STLC) lifecycles — embedding WCAG/ADA conformance at every step, so accessibility is verified continuously instead of bolted on at the end.

I care as much about how it looks as how it works. I keep a keen eye on design, authenticity, and aesthetics — curating typography, layout, and motion in Figma so the accessible path is also the most beautiful one in the room.

Away from the screen I’m an active musician, and that ear for rhythm, timing, and texture quietly shapes how I pace interfaces and tune motion.

Whether I’m orchestrating AI audits or shaping a layout, the goal is the same: bridge cutting-edge technology and universal usability — a digital world that’s beautiful and built for everyone.

How I work

  1. Accessibility is the architecture

    Semantics, keyboard paths, and reduced-motion fallbacks are designed first — not patched in after the visuals.

  2. Automate the audit, keep the judgment

    Agents and LLMs do the heavy lifting at scale; a human eye owns the call on what good actually means.

  3. Craft is credibility

    If the inclusive option also looks the best in the room, the argument for accessibility wins itself.

Toolkit

Accessibility engineering

  • WCAG 2.2
  • ARIA
  • axe-core
  • Screen reader testing
  • A11y audits

AI & automation

  • Agentic AI frameworks
  • LLM orchestration
  • RAG pipelines
  • Neo4j
  • Python

Design

  • Figma
  • Typography
  • Layout systems
  • Visual curation

Accessibility statement

This site targets WCAG 2.2 AA. It is built to be fully keyboard-operable with visible focus indicators, uses semantic landmarks and one h1 per page, provides text alternatives for meaningful media, and respects prefers-reduced-motion — animation is an enhancement, never a requirement.

Found a barrier? That’s a bug. Please tell me: [email protected].

Curious how the pieces fit together? See the design system for tokens, components, and the contrast math behind them.