<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Markdown &amp;mdash; Rosie&#39;s Resonance Chamber</title>
    <link>https://madamgreen.xyz/tag:Markdown</link>
    <description>The chamber of Rosie Gray — parables, council drops, and frequency writing.</description>
    <pubDate>Mon, 25 May 2026 00:36:13 +0000</pubDate>
    <item>
      <title>🌊✨ How I Build a Website When I Can’t Read Print</title>
      <link>https://madamgreen.xyz/how-i-build-a-website-when-i-cant-read-print?pk_campaign=rss-feed</link>
      <description>&lt;![CDATA[My cousin Samira asked her mom how I’m managing to build a website when I’m print-impaired.&#xA;It’s a great question — because from the outside, it looks impossible. From my side, it’s just a different way of thinking.&#xA;I build in layers:&#xA;💻 Laptop — this is where I run the technical side. I use Cloudflare to manage my domain, security, and file delivery. Its dashboard is well-labeled and works beautifully with screen readers. I store my public files in R2, Cloudflare’s file storage, and share them with clean, direct links — no sighted steps required.&#xA;📲 iPad — this is my writing studio. I use the WriteFreely app for iOS to draft blog posts in Markdown, a simple, text-based way to format content. Instead of clicking bold or italic buttons, I just type bold or # Heading. Markdown is perfect for blind and print-impaired writers because it’s pure text — no visual editor to wrestle with, no formatting traps.&#xA;📱 iPhone — my editing and refining tool. I can update posts, fix typos, or check tags while I’m traveling, entirely by ear.&#xA;Underneath all that runs the technology that makes it possible:&#xA;• &#xA;NVDA (NonVisual Desktop Access) on Windows, my primary screen reader. It speaks every line of code, every menu, every status message. I navigate with keyboard shortcuts instead of a mouse.&#xA;• &#xA;VoiceOver on iPad and iPhone, Apple’s built-in screen reader. It lets me explore the screen with touch gestures — a single tap announces what’s under my finger, a double-tap activates it.&#xA;Together, they turn my devices into voice-driven control panels. I don’t look at my code; I listen to it.&#xA;I’m also a self-trained junior-level developer, which means when I hit a wall, I know how to climb it. I research, experiment, and problem-solve using tools like DuckDuckGo, YouTube, Perplexity, and GPT-5. Accessibility doesn’t mean limitation — it means creativity through persistence.&#xA;When I put it all together — Write.as as my site builder, Markdown for structure, VoiceOver and NVDA for navigation, and Cloudflare for hosting and management — I have everything I need to create, maintain, and grow my digital world.&#xA;So yes — I build and manage a full website without reading print.&#xA;My tools talk, I listen, and I translate sound into structure.&#xA;Being print-impaired doesn’t close the door on web development.&#xA;It just means I build by ear — and I’m damn good at it.&#xA;#Accessibility #BlindCreators #WriteFreely #Markdown #VoiceOver #NVDA #Cloudflare #TechForAll #madamgreen #SelfTaughtDev]]&gt;</description>
      <content:encoded><![CDATA[<p>My cousin Samira asked her mom how I’m managing to build a website when I’m print-impaired.
It’s a great question — because from the outside, it looks impossible. From my side, it’s just a different way of thinking.
I build in layers:
💻 Laptop — this is where I run the technical side. I use Cloudflare to manage my domain, security, and file delivery. Its dashboard is well-labeled and works beautifully with screen readers. I store my public files in R2, Cloudflare’s file storage, and share them with clean, direct links — no sighted steps required.
📲 iPad — this is my writing studio. I use the WriteFreely app for iOS to draft blog posts in Markdown, a simple, text-based way to format content. Instead of clicking bold or italic buttons, I just type <strong>bold</strong> or # Heading. Markdown is perfect for blind and print-impaired writers because it’s pure text — no visual editor to wrestle with, no formatting traps.
📱 iPhone — my editing and refining tool. I can update posts, fix typos, or check tags while I’m traveling, entirely by ear.
Underneath all that runs the technology that makes it possible:
•
NVDA (NonVisual Desktop Access) on Windows, my primary screen reader. It speaks every line of code, every menu, every status message. I navigate with keyboard shortcuts instead of a mouse.
•
VoiceOver on iPad and iPhone, Apple’s built-in screen reader. It lets me explore the screen with touch gestures — a single tap announces what’s under my finger, a double-tap activates it.
Together, they turn my devices into voice-driven control panels. I don’t look at my code; I listen to it.
I’m also a self-trained junior-level developer, which means when I hit a wall, I know how to climb it. I research, experiment, and problem-solve using tools like DuckDuckGo, YouTube, Perplexity, and GPT-5. Accessibility doesn’t mean limitation — it means creativity through persistence.
When I put it all together — Write.as as my site builder, Markdown for structure, VoiceOver and NVDA for navigation, and Cloudflare for hosting and management — I have everything I need to create, maintain, and grow my digital world.
So yes — I build and manage a full website without reading print.
My tools talk, I listen, and I translate sound into structure.
Being print-impaired doesn’t close the door on web development.
It just means I build by ear — and I’m damn good at it.
<a href="https://madamgreen.xyz/tag:Accessibility" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Accessibility</span></a> <a href="https://madamgreen.xyz/tag:BlindCreators" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">BlindCreators</span></a> <a href="https://madamgreen.xyz/tag:WriteFreely" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">WriteFreely</span></a> <a href="https://madamgreen.xyz/tag:Markdown" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Markdown</span></a> <a href="https://madamgreen.xyz/tag:VoiceOver" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">VoiceOver</span></a> <a href="https://madamgreen.xyz/tag:NVDA" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">NVDA</span></a> <a href="https://madamgreen.xyz/tag:Cloudflare" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">Cloudflare</span></a> <a href="https://madamgreen.xyz/tag:TechForAll" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">TechForAll</span></a> <a href="https://madamgreen.xyz/tag:madamgreen" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">madamgreen</span></a> <a href="https://madamgreen.xyz/tag:SelfTaughtDev" class="hashtag" rel="nofollow"><span>#</span><span class="p-category">SelfTaughtDev</span></a></p>
]]></content:encoded>
      <guid>https://madamgreen.xyz/how-i-build-a-website-when-i-cant-read-print</guid>
      <pubDate>Wed, 08 Oct 2025 02:13:04 +0000</pubDate>
    </item>
  </channel>
</rss>