Digital Dimensions
An independent web practice · Marietta, GA · Remote across the U.S.

Web systems, looked after — with attention to accessibility and the HIPAA-aware web layer.

Digital Dimensions is the independent web practice of Jared Brannen. The day-to-day work is traditional webmastering — building, maintaining, and improving web applications and websites — for healthcare practices, nonprofits, and mission-driven teams. Within that, I bring focused attention to accessibility (WCAG 2.2 AA) and to the technical web layer of HIPAA-aware projects: forms, portals, access control, logging, vendor coordination, and documentation your compliance team can actually review.

Book a consultation See what I do
Practice focus
Web systems · Accessibility · HIPAA-aware web work
Engagement
Project-based or retained
Location
Remote · United States
Availability
Taking new engagements
I work with
Healthcare practices Nonprofits & foundations Mission-driven SMBs Agencies needing specialist support
§ 01
What I do

Four areas, one throughline: web systems that hold up when people actually use them.

  1. Web Systems
    01.

    Web systems — the day-to-day work

    The traditional webmaster work: building and maintaining sites and web applications, CMS care, performance, security updates, content changes, SEO, integrations — the foundation work (Web 1.0) and the reach-and-growth work (Web 2.0) that keep a web presence healthy. New builds, takeovers of existing sites, and monthly retainers.

    Custom builds & rebuilds CMS & site care API integrations Monthly retainers
  2. Accessibility
    02.

    Accessibility

    WCAG 2.2 AA audits, remediation of existing sites, and accessible new builds — tested with the assistive technologies your users actually rely on, not just an automated scanner. Useful for organizations that want real inclusion, and for those facing a demand letter or procurement requirement on a deadline.

    WCAG 2.2 AA Audits & remediation Accessible forms Assistive-tech testing
  3. HIPAA
    03.

    HIPAA-aware web work

    Patient-facing intake, secure forms, portal experiences, and private workflows — built with HIPAA considerations in mind from the first commit. The work focuses on the technical web layer: minimum-necessary data collection, access control, logging, encryption decisions, vendor and BAA review, and documentation for your compliance team. I’m a webmaster, not a HIPAA consultant; I work alongside your Privacy and Security Officers.

    Secure intake forms Patient portals Vendor/BAA review Audit logging
  4. AI
    04.

    AI integration, where it earns its place

    I use AI tools every day in my own work, and I integrate AI features into client projects when they genuinely help — LLM-assisted intake, retrieval over your own content, summarization, classification. Treated as first-class engineering: grounded in your data, evaluated before ship, logged, and held to the same accessibility and privacy standards as the rest of the system.

    LLM-powered features Retrieval over your content Evaluation & logging Privacy-aware
§ 02
Approach

How an engagement tends to go.

Step 1

Discovery

I start with the operational reality of the team using the system, the regulatory context if relevant, and what already exists. Honest scoping is easier when we’ve actually looked.

Step 2

Design

Interface mockups where useful, plus the less visible work: data flows, trust boundaries, and how the system holds up for people on different devices, connections, and abilities.

Step 3

Build

Incremental delivery with checkpoints you can react to. Accessibility and security considerations are part of the work as we go — not a QA pass at the end.

Step 4

Deploy

Real handover. Documentation, monitoring, and a clean environment, so your team inherits something they can understand — not a black box that depends on me.

Step 5

Maintain

Optional ongoing care for what I built — or for the site you already have. Monthly retainers with clear scope, or as-needed work at a fixed rate.

The boring parts — the audits, the edge cases, the Tuesday afternoons when something breaks — are usually where it shows whether a web system actually works. That’s most of what I think about.

Start a conversation
§ 03
Selected work

A few engagements, summarized.

HIPAA-aware · Service management · Multi-jurisdictional

Service-request management platform now used by a county government and a network of provider organizations.

A distributed platform for routing service requests across jurisdictions and provider networks, with HIPAA safeguards considered from the start. Features include automated request routing, provider matching, and audit trails for operational review. The platform is now in use across hundreds of partner organizations.

400+Partner organizations using
HIPAA-aware architecture
AAWCAG 2.2 target
Learning management · Accessibility

Custom LMS for healthcare training and certification tracking.

Replaced a legacy training system with an accessible learning management platform: course authoring, progress tracking, certification management, and reporting for healthcare professionals.

800+Active learners
Grant management · Financial tracking

Applications and tracking system used to administer multi-million-dollar grant programs.

Application intake, review workflows, approval chains, and financial reporting with audit capability — supporting hundreds of applications and well over $2M in distributions across the program’s history.

$2M+Distributed via the platform
§ 04
About

A practice, not a platform.

Portrait of Jared Brannen
Jared Brannen · Lead

Digital Dimensions is the web practice of Jared Brannen — the same person you’ll talk to throughout an engagement.

I’ve been building web systems for healthcare practices, nonprofits, and mission-driven organizations for 15+ years. I work as an independent practice rather than an agency, which means the person you talk to is the person doing the work. Past engagements have included HIPAA-aware applications used to administer multi-million-dollar grant programs, accessibility-first builds, and a service-request platform now used by a county government and a network of partner organizations.

The areas I pay extra attention to — accessibility and the HIPAA-aware web layer — tend to get skipped on smaller engagements. They don’t need to be skipped, and the cost of doing them well at the start is much lower than retrofitting them later. That’s most of what differentiates this practice from a generalist webmaster: the same day-to-day work, with those things treated as part of the job rather than as add-ons.

Every engagement is scoped honestly, delivered with documentation your team can actually use, and built so you can maintain or replace what I deliver. There’s a longer note on technical philosophy and stack choices on the Engineering page if you want it.

Based
Marietta, GA · Serving clients nationwide
Experience
15+ years in web development
Stack
PHP 8, JavaScript, React, MySQL, WordPress, Drupal, REST & GraphQL APIs
Areas of attention
WCAG 2.2 · HIPAA-aware web layer · Maintainable architecture
§ 05
Capabilities

A short map of what I do.

A full catalog of the day-to-day webmaster work — foundation/care (Web 1.0) and reach/growth (Web 2.0) — lives on the Web Systems page. The summary below is just the shape of it.

Build & front-end

  • Accessible interface design (WCAG 2.2)
  • Responsive layouts & mobile-first forms
  • Screen-reader and keyboard-first UX
  • Component patterns & design systems
  • Brand-consistent visual design

Applications & integrations

  • Custom web applications
  • Secure web forms & intake systems
  • Patient and member portals
  • Role-based access & SSO
  • API integrations (CRM, payment, scheduling)

Care & security

  • CMS, plugin, & dependency updates
  • Security headers & CSP
  • Backups, uptime monitoring, & incident response
  • HIPAA-aware web architecture
  • Audit logging & access review

CMS & content

  • WordPress, HubSpot, Drupal, Joomla, Wix
  • Headless & hybrid CMS architecture
  • Content modeling & migration
  • Editorial workflows
  • Documentation for staff and compliance officers

Performance & SEO

  • Core Web Vitals tuning
  • Image & media delivery
  • Caching, CDN, asset pipelines
  • Technical SEO audits
  • GA4 & Search Console setup

Operations & support

  • Monthly webmaster retainers
  • Domain, DNS, & email deliverability
  • SSL renewal tracking
  • Stakeholder reporting
  • Named technical contact for hosting/registrar
§ 06
Questions

Before you get in touch.

Will you sign a Business Associate Agreement (BAA)?

Yes. For engagements where I will create, receive, maintain, transmit, or access Protected Health Information (PHI), I sign a BAA before any PHI is exchanged, and I coordinate with your Privacy Officer, Security Officer, or counsel so the technical implementation fits your broader HIPAA program. See the HIPAA page for how I scope this kind of work.

Can you take on just an accessibility audit — without a full rebuild?

Yes. A standalone WCAG 2.2 AA audit with a prioritized remediation plan is a common engagement. You receive the full report and the plan, and you’re free to have your internal team (or anyone else) implement the fixes. Many clients choose to have me do the remediation as well, but that’s not a condition of the audit.

Will you work with our existing CMS, or do we need to migrate?

I work with what you have whenever that’s the right call. WordPress, Drupal, Joomla, HubSpot, Wix, and custom stacks are all fair game. Migrations happen when the existing platform is actively working against your goals — not because I’d prefer a different one.

What does a typical engagement look like?

Most engagements fall into one of three shapes: a fixed-scope project (a new site or application, a remediation, an integration); a retained monthly arrangement (ongoing maintenance, iterative work, and priority access); or a short discovery engagement to scope a larger project before committing. I’ll suggest the right shape during the first conversation — I won’t try to push retainers on projects, or projects on ongoing work.

How do you price work?

Projects are priced as fixed fees against a defined scope; retainers are priced as monthly blocks of hours. Pricing depends on complexity, compliance requirements, and timeline, and I’ll put a specific number in front of you after a first conversation, not before. If budget is a constraint, tell me upfront and I’ll either shape a scope that fits or tell you honestly that it isn’t the right engagement for me.

Where are you based, and how do you work with remote clients?

I’m based in Marietta, GA and work remotely. Most of the work is asynchronous, with scheduled video calls at project milestones and whenever a real-time conversation is genuinely more useful than a written one. For organizations that need in-person kickoffs or deliverables, I can make that work for engagements of sufficient size.

Begin

Let’s talk about the web system you actually need.

A 30-minute conversation is the cleanest way to tell whether we’re a fit. If we’re not, I’ll usually know someone who is.

No sales process, no prepared decks — just a focused conversation.

Start here

Book a 30-minute consultation

I’ll send a short set of questions beforehand so the call is useful from the first minute.

0 / 5000

I’ll respond personally within one business day to suggest times for a 30‑minute call. If it’s easier, email jared@digitaldimensions.us directly.

Email jared@digitaldimensions.us