We built OriginalSin.com.sg with one idea in mind: recipes for everyone. That means people with fast internet or slower connections. Folks using screens, readers, or just their ears. Fancy desktops, old phones, voice commands, keyboards, whatever works for you, works for us.
This page lays out what we’re doing to make that possible, how we think about it, and where we’re headed next. It’s long. Not because we love long pages. It’s long because this stuff matters.
Design That Moves with You
Some people read recipes line by line. Others jump straight to the part about the sauce. We don’t assume. Instead, we’ve built pages that shift with different needs. Font sizes grow when browser settings change. Layouts flex without cracking. Controls make sense whether tapped or tabbed.
We didn’t guess. We followed tried-and-true guides like WCAG 2.1, focusing mostly on AA compliance but going past that when possible. We keep asking questions. Does this button describe what it does? Can this color combo be read by everyone? If something spins, does it stop when you say so?
Movement on screen can be helpful, or distracting. Our animations respect preferences. If your device says “reduce motion,” our site listens. Transitions stay smooth, but without the extras.
Colors, Text, and Contrast
Some screens glow like lighthouses. Others fade out in sunlight. We get that. So our text isn’t locked into one look. It adapts. Dark on light or light on dark, contrast levels stay strong.
We avoid color-only clues. Red might mean hot, but if red’s all you see, then that’s not enough. That’s why we mix icons, text, and space. More ways to spot what matters.
Our palette sticks to bold, readable tones. Flashy? No. Clear? Always. Font choices follow that same logic. Sans-serif, simple, clean. Custom fonts load fast and fall back smartly if things slow down.
Keyboard Ready
Every recipe, article, and dropdown can be reached with a keyboard. No mouse needed. Arrow keys shift between steps. Tabs move through links. Shortcuts don’t trap you. Nothing vanishes behind a hover that never shows up on a tap.
Focus states are clear. You’ll see where you are. No invisible boxes. No guessing games.
For users who rely on screen readers, we’ve worked to build natural reading flows. Headings make sense. Lists behave like lists. Labels match their fields.
Screen Readers Welcome
We code with screen readers in mind. Every main feature, from step-by-step instructions to ingredient toggles, has structure baked in. ARIA roles stay lean, avoiding clutter while still filling gaps where native HTML falls short.
Forms say what they are. Buttons say what they do. Nothing critical hides behind a mouse-only reveal. Instructions aren’t vague, and we skip over junk.
We test using NVDA and VoiceOver regularly. Bugs show up, so we fix them. Then we test again. Accessibility isn’t a checkbox. It’s a loop.
Images, Icons, and Audio
Food photography makes mouths water. Still, we know not everyone sees it. That’s why every image has a job. If the image gives real info, it gets alt text. If it’s decoration, we leave it out of your way.
Icons come with labels. Not tooltips that disappear the moment your mouse slips, real labels, real names.
If a recipe has sounds, sizzling bacon, bubbling curry, they’ll have transcripts or captions too. Right now, we’re just starting that part. Progress is slow, but steady.
Zoom, Scale, and Flex
Zooming into content shouldn’t break things. Our pages expand gracefully up to 400%. No overlapping boxes. No weird cut-off text. Everything still works, just bigger.
That helps everyone, not just folks with vision loss. Fatigue, injury, small devices, all benefit from smarter scaling.
Our layout avoids fixed-width traps. Text reflows, buttons shift, nothing important hides. We test with pinch-zoom, browser zoom, mobile viewports, and magnification tools.
Captions, Transcripts, and Language
Text means different things to different people. That’s why we keep our writing plain. Recipes don’t talk down, but they don’t throw jargon either.
If we ever say “simmer,” we explain what that looks like. If something needs stirring, we say how often, how fast, and with what.
When we use video or audio, captions follow. Not automated captions full of weird guesses. Hand-written ones. Same for transcripts, they go word by word, sound by sound.
Language is English for now, but we’re working on multilingual support. We’ll make sure those future pages carry over the same clarity.
Slow Internet? No Problem
We slimmed down images. We skipped bloated frameworks. We cache smart. Recipes load quickly, even on weak signals.
You don’t need the newest phone to view this site. We’ve tested on older browsers too. JavaScript stays light. Most pages load even if scripts fail.
Downloads stay lean. No autoplay videos. No forced refreshes. No tracking scripts running wild. Your connection shouldn’t block your kitchen.
Assistive Tech Friendly
Some users rely on tools we don’t see, braille displays, voice command systems, eye trackers. While we don’t own every device, we try to match their expectations.
We read developer blogs, accessibility forums, and open issue reports. When users mention a specific tool, we try it out or simulate it. That’s helped us improve label clarity, landmark roles, and tab orders.
Nothing’s perfect. We stay honest about what needs fixing. We don’t hide that behind fancy words or vague promises.
No Barriers Allowed
Accessibility should never feel like a bonus feature. This isn’t an add-on. It’s the structure. From the first line of code to the last polish on a recipe, we build with this in mind.
We don’t segregate. One version. One site. One experience for all.
Making something usable by more people helps everyone. That’s not a side effect. That’s the point.
What We’ve Learned
Building for accessibility taught us a lot. It’s not just about tools. It’s about thinking differently. Slowing down. Asking what might go wrong before something breaks.
We used to rush layouts, cram content, slap on labels last. Not anymore. Now we write with purpose. Test with purpose. Fix with purpose.
Mistakes still happen. But we make fewer of them. And when we hear feedback, we listen. Sometimes we get praised. Sometimes called out. Both matter.
What We’re Doing Next
We’re working on recipe videos with audio descriptions. We’re also building a “read aloud” option for long articles. That way, folks with reading fatigue can still enjoy our stories.
We want to support local languages. Not just translations, but full support. That means changing layout flow, font handling, and even recipe structure.
We’re also rebuilding our form system. Right now, not every comment box behaves right on all screen readers. That’s high on the fix list.
Finally, we’re starting user testing with real-world assistive tech users. That’s the big one. Lab tests help. Real kitchens help more.
What We Won’t Do
We won’t rely on overlays that pretend to fix everything. They don’t. We code our changes by hand.
We won’t hide content behind mouse-only tricks or gestures that demand five fingers and a steady hand.
We won’t use CAPTCHA unless we absolutely have to. If we ever do, we’ll offer an audio option, or better yet, a logic question that doesn’t block access.
We won’t track people to “optimize experience.” That’s marketing speak. We cook. We don’t stalk.
Language You Can Trust
Accessibility pages usually sound like contracts. Ours won’t. We’re not here to impress lawyers or dodge blame. This is for you. This is us promising we care, and proving it with action.
You don’t need a degree to read this. You shouldn’t need one to use our site.
Plain words. Clear structure. Honest intent. That’s the goal.
Every Dish for Every Hand
Cooking’s physical. Stirring, chopping, tasting, it asks a lot. So we try to give back with instructions that match different needs.
Timers have voice-friendly options. Steps use short, digestible sentences. Videos stay focused, with minimal distractions.
We’re exploring hands-free navigation through voice. Right now it’s in testing, but it’s promising. Want to scroll with your voice? We’re trying to make that happen.
Always Evolving, Never Arrived
Accessibility isn’t a destination. There’s no finish line. Tech changes. Needs shift. So we stay open. Curious. A little obsessed, honestly.
What worked last year might not tomorrow. We’re okay with that. Change keeps us sharp.
We believe progress is built daily. One bug fix, one suggestion, one smart idea at a time.
Thanks for being part of this. Your voice matters. Your clicks, too.