Hello there!
We made this page because we believe everyone deserves tasty food and a comfy place to scroll through recipes without getting tangled up in tricky design. Babe.com.my is built for real people with real needs, eyes that blink slow, fingers that tap fast, screens that zoom, voices that click. Our site’s not just about food. It’s also about being kind, inclusive, and thoughtful.
Why accessibility matters to us
Nobody likes being shut out. Whether it’s dinner plans or a recipe page, being left behind just plain sucks. We believe sharing food means opening doors, not closing them. That’s why we design with different needs in mind. Color contrast isn’t decoration. Bigger text isn’t a luxury. Screen readers? Yes, they matter too. If someone wants to cook nasi lemak or bake pandan cake, we want the only hard part to be not eating everything before it's ready.
What we’re doing right now
We follow global accessibility practices, like the Web Content Accessibility Guidelines (WCAG) 2.1 and do our best to stick to Level AA. Our tech team tweaks structure, spacing, and design so pages feel easy. Labels are in place, buttons behave, links explain themselves. Headings follow an order that makes sense. Fonts stay legible. Bright colors contrast smartly. Pages respond to screen size changes without panic. Keyboard use works across our pages.
Tech bits that help
Our pages work on popular browsers: Chrome, Firefox, Edge, Safari. We’re mobile-friendly. You won’t need to pinch-and-zoom every time you tap through a dish. We also support keyboard navigation. Tab moves forward, Shift+Tab goes back, Enter selects. Most pages have skip links up top so screen reader users can jump to the good stuff. Images come with alt text that says what’s shown. No guessing games.
Testing for real use
We test pages with screen readers like NVDA and VoiceOver. Also tried with high contrast mode and zoom tools. Our color palettes are double-checked for clarity. Our code is audited with accessibility tools that point out what’s not quite right. Then, we fix it. We use automated checks and manual reviews, both. Why both? Because machines miss things, but so do we. So we mix it up.
Stuff we’ve fixed so far
We spotted link text that said “click here.” We changed that. Made alt text more useful. Reduced blinking animations that annoyed folks. Cleaned up duplicate headings. Fixed small buttons. Improved focus indicators so tabbing around feels less like guessing. We reworked form labels, especially for our recipe submit pages. Added roles to elements. We also caught a few hidden keyboard traps, those are gone now.
Things we’re still working on
It’s not perfect. Some old content didn’t meet the mark, so we’re slowly updating older recipe posts. Some videos still need better captions. Not every image has a great alt tag yet. Our PDF downloads aren’t all accessible, but we’re switching many into simple HTML formats. Some keyboard shortcuts conflict with browser functions, so we’re revisiting those. Accessibility isn’t a checkbox, it’s more like tidying up a kitchen. Ongoing work.
Your voice matters
Found a bug? Something feel off? Couldn’t read a recipe because the font danced around? Drop us a message. Tell us how it went, what stopped you, or what worked better than expected. We listen. We tweak. Feedback makes things better. You don’t have to know tech to spot a problem. Real-world input helps us improve in ways no automated checker ever could.
Easy ways to reach us
Use our contact form or email hello@babe.com.my. We’ll get back in a reasonable time, usually within a few days. If you need help faster, put “ACCESSIBILITY” in the subject line. Someone from our team will reply quickly, especially if something blocks your access completely.
What we believe
Access is basic. Not a feature, not a bonus. Good food shouldn’t hide behind bad code. No one should have to fight a website just to boil water or mix dough. Whether you're using one hand or two, screen reader or mouse, magnifier or touchpad, we want our recipes to feel within reach. Nobody needs another hurdle before lunchtime.
Some helpful tools
Here are some things that might help you get around:
- NVDA (Windows) – Free screen reader
- VoiceOver (Mac/iOS) – Built-in screen reader
- ZoomText – For those who prefer magnified text
- Color Contrast Analyzer – Great for checking page clarity
- NoCoffee Vision Simulator – Helps understand different sight levels
- Dragon NaturallySpeaking – Voice command for easier control
We don’t run these tools, but we recommend them based on what helped during testing. If you know others, send suggestions our way.
Little choices, big changes
We chose fonts with clean lines. Text scales without breaking boxes. Icons make sense without needing extra clicks. We don’t rely on color alone to signal action. Touch targets are roomy, no tiny buttons you’ll miss. Video players have controls that respond well. We reduced flicker and flashing animations to avoid distractions or discomfort.
Mobile first, always
Many folks scroll while shopping for ingredients or cooking in the kitchen. So we make sure things fit on small screens without chaos. Buttons stay tappable. Menus don’t hide behind endless swipes. Instructions are clear, concise, and chunked in steps. No long paragraphs that feel like textbooks. Browsing shouldn’t feel like solving a puzzle.
We think about variety
Sight, hearing, motion, touch, all different for everyone. Some users prefer voice. Others rely on subtitles. Some zoom text up to 300%. Some switch colors to ease strain. No single method works for all. That’s why we build with flexibility. One mode won’t suit every taste, but we try to provide more than one route to every goal.
Team mindset
Accessibility is part of how we work, not something we tack on later. Designers, writers, developers all share responsibility. Everyone checks their piece of the puzzle. Before anything goes live, it passes through eyes that ask, “Would this work for someone using one hand? One eye? Voice commands?”
Updates happen often
As we grow, pages change. New features roll in, old ones get tuned. With every update, we check for accessibility impact. New recipes don’t just get photos, they get labels, markup, and clean layout. Design refresh? We don’t only think about color. We think about contrast, movement, focus.
Language options
Right now, we publish mostly in English. We know this might limit access. Malay support is something we want to offer soon. We’re also exploring tools that allow easy toggling between languages, and checking for readability with translation tools. Simpler language makes understanding easier, no jargon, no fluff.
Recipes made easier
Some folks use speech tools while cooking. So we keep steps brief, list-style, and logical. Timers, temperatures, and ingredients get broken out clearly. We avoid ambiguous terms. Instead of “cook till done,” we say, “cook for 12–15 minutes until golden brown.” No guessing games.
Colors and layout
Our site avoids low-contrast combos. No gray-on-white, no red-on-pink. Headings stand out. Paragraphs breathe. Nothing feels jammed together. Images load fast. No autoplay sounds. Nothing that startles you out of your seat. We value calm design that doesn't scream.
Alt text approach
Photos tell stories. Our alt text aims to do the same. Not “image of food.” More like “golden brown curry puffs with flaky crust, sitting on banana leaf.” Context matters. We train our writers to write alt descriptions that help everyone understand what's going on visually.
What you can expect moving forward
We’re not checking off boxes and calling it a day. We treat accessibility as a process. As tools shift, user habits change, and tech evolves, we keep updating our site. If something breaks or doesn’t work well for your setup, speak up. You’ll help make our site better for others too.
You scrolled through this whole page, thank you! That says a lot about your care for inclusive spaces. We’re grateful for your time. Accessibility is part of our flavor here. We cook for everyone. We design for everyone. We learn, fix, rebuild, and try again. It’s the only way forward.