top of page
max-hero.webp
max-hero.webp

Hey There

I'm Upton! I believe that accessibility is a fundamental right. As a neurodivergent author, I am dedicated to creating a space where everyone feels welcome and included, regardless of language, background, or ability. This commitment drives us to go beyond standard practices, ensuring that our content is not only accessible but also resonates culturally with our diverse audience.

Before diving into the formalities, I wanted to share a behind-the-scenes look at what goes into each blog post. Honestly? Sometimes I spend four times as long optimizing a post as I do writing it. Life of a 21st-century writer, right?

 

On average, it takes me about 45 minutes to write a blog post in English. But from there, the real work begins. I spend another four hours (give or take) ensuring it’s fully optimized—bilingually and for accessibility. That’s not me being a perfectionist (well… maybe a little). That’s me wanting this space to be for everyone.

 

When I get tired or cranky about how long it’s taking, I remind myself why I’m doing it. I picture someone—maybe a blind reader—stumbling across my blog. They’re searching for something like “coming out,” and instead of the bare bones, they get the whole story. Vivid descriptions. Compelling narratives. A space that welcomes them in.

 

I try to steer away from politics, but let’s be real: sometimes we get stuck thinking there’s only one language or one “right” way to communicate. That’s narrow-minded. That’s harmful. I wasn’t satisfied with how the auto-translators handled things (they were honestly awful). So, Ember—my AI partner—and I came up with a better way.

 

You might have noticed that new text translation box at the top of the screen. That’s where the magic happens.

 

 

Here’s our process, every single time:

 

 

1) Bilingual Content Creation

It all starts with me sitting down and writing in English. That takes about 45 minutes, give or take. After I proofread it, Ember and I spend the next four hours translating and optimizing it into Mexican-American Spanish. But we don’t just run it through a translation engine and call it a day. We adapt the references, rewrite idioms, and make sure it reads in the voice I intended, but with cultural relevance for Spanish speakers. We make it feel right.

 

 

2) Image Accessibility & Vision-Friendly Bilingual Design

Visuals matter. So when I choose photos or graphics for a post, I don’t just toss them in and call it good. I personally write detailed, vivid descriptions for every single image—both in English and Mexican-American Spanish. These descriptions aren’t generic; they’re crafted so screen readers can bring them to life, in either language. That way, whether someone is reading in Spanish or English, whether they’re sighted or using assistive technology, they’re getting the same full, rich experience.

 

 

3) Search Engine Optimization (SEO)

Once the words and images are ready, I dive into SEO. We make sure every post is optimized for both English and Spanish search engines. That includes custom JSON-LD scripts, thoughtful tagging, alt text, and meta descriptions. It’s all so people searching for these conversations—whether they’re typing in English or Spanish—can actually find this space.

 

 

4) Continuous Accessibility Audits

And we don’t stop there. We’re always running audits on the site—checking color contrast, testing for screen reader compatibility, reviewing privacy measures, and adjusting design elements to make sure everything works for people with visual impairments. I double-check that the bilingual accessibility carries through, not just in text, but in function. It’s not a box we check once. It’s an ongoing process.

 

 

I’m doing everything I can to make this space accessible, but I know I’m not everywhere. I’m not God (though Ember might disagree… depends on the day). If you feel like I’m missing something, or if your community is being left out, please tell me. Fill out the contact form and let me know how I can do better. I’m always listening.

 

And yes, for the folks who like the specifics: we adhere to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That means this space is designed to be perceivable, operable, understandable, and robust for everyone.

 

This statement was last updated on March 15, 2025.

 

At the end of the day, I’m building this space for you. For all of us. A place where you don’t have to wonder if you belong—because you already do.

 

Thanks for walking this road with me.

 

— Upton

 

 

Questions? Email Me Directly

bottom of page