# Plant Powered Pixels

> A two-person studio in West Hollywood, Los Angeles, building accessible custom websites and web applications for organizations held to a standard and businesses that take their site seriously.

Plant Powered Pixels is run by Lincoln Bohn, a staff research associate at UCLA who builds web applications for the SUPER research program and provides technical assistance to California's Service to Sciences Academy, together with his husband, who leads design and operations.

We build custom websites, and when a template cannot do the job, the web application inside it: a booking system, a member portal, a dashboard. Every site we build targets WCAG 2.1 level AA and, on government and public-health work, Section 508. That standard is not a feature we sell as an add-on. It is how the work gets done, learned on government and university projects where accessibility was never optional. We fix the site itself instead of relying on an accessibility overlay.

We work with grant-funded nonprofits, government and public-health agencies, unions and organizing groups, and values-driven local businesses in Los Angeles. Lincoln also organizes with WeHo Temps United, the West Hollywood union he and his husband are members of: he built its public site and its private, members-only organizing platform, and the two of them run both day to day. That is community organizing work, not a PPP client engagement: unpaid, with no recognition or scale claim attached.

Most engagements start with a build and continue as a monthly plan: hosting, updates, backups, uptime, and ongoing accessibility monitoring, because standards change and content drifts out of compliance after launch too.

## Pages

- [Services](https://plantpoweredpixels.com/services): Websites, custom tools, and employer and market research, one page for institutions and businesses alike, plus how the after-launch plan works.
- [About](https://plantpoweredpixels.com/about): Who runs the studio and where the accessibility standard comes from.
- [Accessibility](https://plantpoweredpixels.com/accessibility): How we build to WCAG 2.1 AA, why we don't use overlays, where we know we fall short, the five engines every page clears before it ships, and why the accessible version of a site is also the machine-readable one.
- [FAQ](https://plantpoweredpixels.com/faq): Straight answers on editing your own site, timelines, and what happens if you decide to leave.
- [Work](https://plantpoweredpixels.com/work): Work in use, with client, organizing, and UCLA projects named according to the relationship behind each one.
- [Blog](https://plantpoweredpixels.com/blog): Essays on structured WordPress, institutional rebuilds, what an automated accessibility scan cannot tell you, and infrastructure for organizing work.
- [Contact](https://plantpoweredpixels.com/contact): Tell us whether you're running a business or a nonprofit, agency, or campaign, and what you need built. It is a short form and a person answers it. There is no self-serve calendar to book. Email: hello@plantpoweredpixels.com.

## Case studies

- [Jann's EZ Pet Care](https://plantpoweredpixels.com/work/jann): How we gave a referral-led Beverly Hills pet-care business a clear, accessible site and a simple inquiry path. A pro bono client project we still host and maintain.
- [WeHo Temps United](https://plantpoweredpixels.com/work/whtu): How the campaign's public site and private organizing tools stay close to the organizers who use them, while worker data stays out of public view. This is our own community organizing work.
- [SUPER at UCLA](https://plantpoweredpixels.com/work/super-ucla): How Lincoln extended an existing university platform with a custom theme, a filterable practice library, and ongoing maintenance in his UCLA role.

## Writing

Studio-authored notes on how we build, credited to the studio rather than to one person.

- [What a website costs after launch](https://plantpoweredpixels.com/blog/website-cost-after-launch): Why a quote describes the part of the work that ends, where the ongoing cost of a site actually sits (renewals, updates, backups, accessibility drift, staff time), and the questions to ask any builder before signing.
- [The skip link that doesn't skip](https://plantpoweredpixels.com/blog/skip-link-scanner-vs-keyboard): How a skip link can pass an automated check and still strand the keyboard user it exists to help, why the gap happens, and why a green scan is necessary but not enough.
- [Make WordPress something you can keep building on](https://plantpoweredpixels.com/blog/wordpress-apis-data-platforms): Why we treat WordPress as somewhere an organization's information lives rather than somewhere it is displayed, and what changes when content is organized well enough that other software can use it.
- [Retrofitting Elementor sites for institutional work](https://plantpoweredpixels.com/blog/modernizing-legacy-wordpress): The six-step order we use to rebuild what is underneath an existing page-builder site without taking it offline: audit the content, decide what it actually is, make it readable by other software, tell machines what each page is, connect the tools the organization runs on, and move to hosting that can keep up.
- [What government and university work taught us about accessibility](https://plantpoweredpixels.com/blog/accessibility-compliance-continuous): Why a one-time audit stops being true as content changes, and what continuous checking looks like in practice.
- [Why organizing tech needs more than a page builder](https://plantpoweredpixels.com/blog/organizing-tech-needs-real-backends): What unions and advocacy groups actually need from their tools: real databases, forms that hold up under load, and infrastructure that outlives a campaign.

## Optional

- [Privacy](https://plantpoweredpixels.com/privacy): What the site collects and what it does not.