DEV Community: Auger Móra

How to Create Accessible Websites for People with Disabilities

Auger Móra — Tue, 04 Mar 2025 19:24:04 +0000

Hey everyone! 👋

Let’s be real—most of us don’t think about web accessibility until we have to. I was the same. When I started building websites, my focus was on design, performance, and making things look cool. But then I worked on a project where accessibility was a must, and I realized...

🚨 I had been unknowingly building websites that some people couldn’t even use. 🚨

That hit me hard. Imagine needing the internet for work, school, or even ordering food—but struggling because a website isn’t designed for you. So, I did a deep dive into accessibility, and now I want to share what I’ve learned.

Here’s how to make your websites usable for everyone—not just those with perfect vision, hearing, or motor skills.

1. Use Semantic HTML (Your Future Self Will Thank You) 🏗️

I used to throw <div>s everywhere like confetti. Turns out, that’s terrible for accessibility (and SEO).

Why it matters:

✅ Screen readers rely on proper tags to understand content.

✅ Less work for you later—semantic HTML improves structure and makes styles easier to apply.

Easy Fixes:

❌ Bad: <div class="button">Click me</div>

✅ Good: <button>Click me</button>

❌ Bad: <div class="nav"> (just use <nav>)

✅ Good: <nav> ... </nav>

Using the right HTML tags means assistive technologies can interpret your site properly—without weird workarounds.

2. Color Contrast: Not Everyone Sees Like You Do 🎨

I love a good aesthetic website, but let’s be honest—some designs prioritize beauty over usability. Ever seen light gray text on a white background? Yeah, don’t do that.

Test Your Colors:

✅ Use tools like WebAIM Contrast Checker.

✅ Aim for a 4.5:1 contrast ratio for text (big text can be 3:1).

✅ Don’t rely only on color for meaning (e.g., “Red = Error” isn’t helpful for colorblind users).

Small fix, huge impact.

3. Make Your Website Keyboard-Friendly ⌨️

Some people can’t use a mouse due to motor disabilities. Your site should work with just a keyboard (or other assistive devices).

Try this challenge:

👉 Go to your website and navigate using only Tab, Enter, and Arrow keys.

Can you access everything?
Does it skip important links?
Are you stuck somewhere?

If your site breaks without a mouse, it’s time for fixes:

Best Practices:

✅ Use button instead of clickable <div>s (buttons are naturally keyboard-friendly).

✅ Ensure forms and links can be accessed via Tab key.

✅ Add :focus styles so users know where they are when tabbing.

If you’ve never done this before, trust me—it’s an eye-opener.

4. Add Alternative Text for Images (Alt Text = Super Important) 🖼️

I used to completely ignore alt text. I figured, “Eh, the image is just decorative.” But for blind users who rely on screen readers, missing alt text = missing information.

Quick Guide:

✅ For meaningful images:

<img src="profile.jpg" alt="John Doe, smiling with a coffee cup">

✅ For decorative images:

<img src="stars.png" alt=""> (Empty alt hides it from screen readers, which is fine for purely decorative elements).

Rule of thumb: If removing the image removes meaning, it needs alt text.

5. Caption Videos & Provide Transcripts 📽️

Imagine watching a tutorial without sound—would you still understand it? That’s the experience for deaf or hard-of-hearing users when videos have no captions.

What to do:

✅ Use closed captions for videos (YouTube auto-captions are a start, but they’re not perfect).

✅ Provide text transcripts for audio content.

✅ Don’t rely solely on audio for instructions—offer visual alternatives.

Your content should be accessible to those who can’t hear or process audio easily.

6. Forms: Don’t Make Users Guess What to Type 📝

Forms can be a nightmare if they’re not accessible. Imagine filling out a form with no labels, vague errors, or no guidance.

Make Forms Better:

✅ Use <label> for inputs (not just placeholder text).

✅ Make error messages clear (instead of just “Invalid input”).

✅ Ensure form fields have a logical order (so screen readers don’t jump randomly).

❌ Bad Example:

<input type="text" placeholder="Enter your name">

✅ Good Example:

<label for="name">Full Name:</label>  
<input type="text" id="name" name="name">

This tiny fix improves both accessibility and user experience.

7. ARIA: When HTML Needs a Little Help 🏗️

Sometimes, default HTML doesn’t cover everything. That’s where ARIA (Accessible Rich Internet Applications) helps.

👉 Use ARIA when there’s no built-in semantic HTML option.
✅ Example: Making a custom dropdown accessible

<div role="combobox" aria-expanded="false">
  <div role="option">Option 1</div>
  <div role="option">Option 2</div>
</div>

🚨 BUT! Don’t overuse ARIA—if regular HTML works, use that instead.

Final Thoughts: Accessibility Benefits EVERYONE 🚀

Here’s the thing—accessibility isn’t just for people with disabilities. It helps:

✅ Users with slow internet (text loads faster than images).
✅ People in noisy environments (captions help in loud places).
✅ Elderly users (better readability, easier navigation).
✅ EVERYONE.

I used to think accessibility was extra work. But once I started, I realized it’s just about good design—and it makes the web better for everyone.

Want a challenge?

Take your own website and try using it with only a keyboard or a screen reader. You’ll be surprised what you learn!

What are your thoughts on web accessibility? Have you made any changes to your sites? Let’s chat in the comments! 🚀

Best Practices for Freelance Web Developers (From a Student & Freelancer)

Auger Móra — Tue, 04 Mar 2025 19:10:43 +0000

Hey, everyone! 👋

I’m a freelance web developer juggling projects while finishing my Computer Engineering degree. If you’re like me—balancing studies, coding, and trying to make a name for yourself in freelancing—then you know it’s not always easy.

Freelancing is an amazing way to gain real-world experience, build a portfolio, and earn money, but it also comes with time management struggles, client challenges, and learning curves. Over time, I’ve picked up some best practices that have helped me stay sane and grow as a freelancer, and I want to share them with you.

1. Set Clear Expectations with Clients (or Risk the Chaos) 💀

When I started freelancing, I made the classic newbie mistake—I took on projects without clear contracts or defined scopes. Some clients kept adding "just one more thing" (a.k.a. scope creep), and I ended up working way more than expected. Lesson learned!

Here’s what I do now:

✅ Always discuss project scope upfront – List out exactly what you're delivering.

✅ Have a contract – Even a simple one outlining payment, deadlines, and revisions.

✅ Be upfront about your availability – As a student, I make it clear I have class schedules, so clients know when I’ll be online.

This saves you from unnecessary headaches and keeps everything professional.

2. Your Portfolio = Your Digital Resume 🎨

When I landed my first real freelance gig, it wasn’t because of my resume—it was because of my portfolio. Clients want to see what you can do, not just hear about it.

What worked for me:

🚀 Keep it simple, but showcase real projects – Even if it's small apps, redesigns, or class projects, put them online!

📢 Add testimonials if possible – Happy clients = more credibility.

🔗 LinkedIn & GitHub matter – Keep them updated. I’ve had recruiters and clients reach out just from seeing my GitHub.

Your portfolio doesn’t need to be fancy, but it should be accessible and professional.

3. Time Management: Balancing Freelance, Studies & Life ⏳

Balancing a Computer Engineering degree and freelancing is no joke. At first, I found myself procrastinating on schoolwork while drowning in projects.

Here’s what saved me:

📆 Google Calendar + Notion – I plan out deadlines for classes & projects to avoid last-minute panic.
🎯 Set office hours – Even as a freelancer, I try to keep "work hours" to avoid burnout.

Trust me, the key to surviving as a freelancing student is learning how to manage your time effectively.

4. Know Your Worth – Charge What You Deserve 💰

At first, I was scared to charge higher rates—I thought clients would ghost me. But when I undercharged, I got low-quality clients who expected everything for free.

What I do now:

💵 Charge based on value, not just time – If your work improves their business, price it accordingly.

📜 Break payments into milestones – I do 50% upfront, 50% after completion (to avoid disappearing clients).

🙅 Say no to exposure gigs – "It’ll be great for your portfolio!" Nope. That doesn’t pay the bills.

Once I raised my rates, I attracted better clients who respected my time. It’s scary, but worth it.

5. Stay Updated (Tech Moves FAST) 🚀

Freelancing has pushed me to learn way more than my degree alone ever could. But staying up-to-date is a challenge when new frameworks drop every other week.

How I keep learning:

📖 I follow blogs like CSS-Tricks, Smashing Magazine, and DEV.to – Quick insights into new trends.

🎥 YouTube & Udemy – Free or affordable, practical courses.

🛠 Build small projects with new tech – Even if it’s just a weekend side project, hands-on experience is key.

If you're a student wanting to stand out, always keep learning outside of class!

6. Client Communication is Everything 💬

One thing I learned fast: Most clients are NOT technical. If you bombard them with "API integrations" and "state management", they'll zone out.

What works for me:

🔹 Keep explanations simple – "This will make your website load faster" instead of "I optimized the Lighthouse score."

🔹 Set response expectations – Let them know when you’ll reply (I don’t answer messages at 2 AM).

🔹 Use project management tools – Trello, ClickUp, or even a shared Google Doc helps avoid endless email chains.

Clear communication = fewer misunderstandings & happier clients.

7. Network & Get Clients Organically 🤝

I used to think finding clients meant spamming job boards—but referrals & networking have been my best sources of work.

How I find clients:

💡 Let people know what you do – Post on LinkedIn, X (formerly Twitter), or even tell friends & family.

🌐 Join freelancing communities – Discord, Reddit, and IndieHackers have hidden gems.

🗣 Ask past clients for referrals – If they loved your work, they’ll happily recommend you.

Your next big project might come from a casual X convo—don’t underestimate networking!

8. Freelancing = Business, Treat It Like One 🏢

When I started, I thought freelancing was just "coding for money." But I soon realized, it’s a business—and treating it like one changed everything.

Business tips I’ve learned:

📑 Track your income & expenses – Even simple Excel sheets help.

📝 Have contracts & invoices – Use tools like Bonsai or Wave for easy invoicing.

📊 Plan for taxes – Freelance income isn’t tax-free (I learned this the hard way... but hey, you know, it is what it is living in Spain 🇪🇸💸).

The sooner you run your freelance work like a business, the more professional (and profitable) it becomes.

Final Thoughts: Freelancing is a Marathon, Not a Sprint

Freelancing as a web developer while studying has been challenging but rewarding. I’ve made mistakes, worked with amazing (and not-so-amazing) clients, and learned so much beyond what my degree teaches me.

Here’s my final advice:

✔ Be professional, even if you're a student – Your work reflects you.

✔ Keep learning – The tech world moves fast; stay ahead.

✔ Know your worth – Charge fairly and don’t let clients undervalue you.

✔ Find a balance – Don’t let freelancing burn you out while in school.

Freelancing has opened doors for me I never imagined. If you're thinking about it—go for it! 💪

Are you freelancing while studying? How’s your experience been? Let’s chat in the comments! 🚀

The Essential Skills Every Computer Engineer Should Master Before Graduating

Auger Móra — Tue, 04 Mar 2025 17:56:53 +0000

Hey there, future engineer! 👋🎓

If you're close to finishing your computer engineering degree, you're probably wondering: “Do I have what it takes to thrive in the real world?”

I’ve been there. University gives you a strong foundation, but there’s a big gap between theory and industry expectations. So, let’s talk about the essential skills that will not only help you land your first job but also make you a standout engineer!

1. Programming Proficiency

🌟 Why It Matters:

If there's one thing you’ll do a lot as an engineer, it’s coding. Whether you’re building applications, working on embedded systems, or debugging complex problems, coding is at the heart of it all.

💡 My Recommended Languages:

C/C++ → Great for system-level programming, embedded development, and performance optimization.
Python → Your go-to for scripting, automation, AI, and web backend development.
Java → Still a powerhouse for enterprise applications and Android development.
Assembly → Not always necessary, but understanding it gives you serious street cred.

👉 Pro Tip: Challenge yourself with LeetCode or Codeforces problems—it's a great way to level up fast.

2. Understanding Data Structures & Algorithms

🌟 Why It Matters:

Every technical interview ever: “Solve this problem using an optimal algorithm.” Mastering DSA isn’t just about passing interviews—it teaches you how to write efficient code.

🔑 Key Topics:

Arrays, Linked Lists, Stacks, and Queues
Hash Maps and Binary Trees
Graph Algorithms (BFS, DFS, Dijkstra’s Algorithm)
Sorting and Searching Techniques
Dynamic Programming (Yes, it's painful, but so worth it!)

👉 Pro Tip: Implement these concepts in different languages to see how they work under the hood.

3. Version Control (Git & GitHub/GitLab)

🌟 Why It Matters:

Imagine working on a group project where your teammate accidentally deletes the whole project. 😱 Version control is the safety net that prevents disasters.

⚡ Must-Know Git Commands:

# Clone a repository
git clone <repo_url>

# Create a new branch
git checkout -b feature-branch

# Add and commit changes
git add .
git commit -m "Added new feature"

# Push changes
git push origin feature-branch

👉 Pro Tip: Start contributing to open-source projects on GitHub—it’s a game-changer for your resume.

4. Operating System Fundamentals

🌟 Why It Matters:

You don’t have to write your own OS (unless that’s your thing), but understanding how an OS works will make you a better engineer.

🔑 Must-Know Concepts:

Process Management (Threads, Scheduling, Deadlocks)
Memory Management (Heap, Stack, Virtual Memory)
File Systems & Permissions
Networking Basics (Sockets, TCP/IP, HTTP)

👉 Pro Tip: If you’re not comfortable with Linux yet, start using it NOW. Learn command-line basics, write some shell scripts, and explore system internals.

5. Computer Networks & Security Awareness

🌟 Why It Matters:

Whether you’re working with web apps, cloud systems, or embedded devices, networking is everywhere. And let’s be honest—nobody wants to be the engineer who introduces a security vulnerability.

🔑 Key Topics:

TCP/IP, DNS, HTTP/HTTPS, and REST APIs
Firewalls, Encryption, and Secure Coding Practices
Basic Penetration Testing and Ethical Hacking (Because it’s fun!)

👉 Pro Tip: Use Wireshark to analyze network packets—it’s an eye-opener.

6. Database Management & SQL

🌟 Why It Matters:

Most real-world applications store and retrieve data, so you need to understand how databases work.

🔑 Key Topics:

SQL Queries (SELECT, JOIN, GROUP BY, etc.)
Database Normalization & Indexing
NoSQL vs. SQL Databases (MongoDB, PostgreSQL, MySQL)

👉 Pro Tip: Build a simple CRUD app with a database to get hands-on experience.

7. Embedded Systems & Hardware Knowledge

🌟 Why It Matters:

If you're interested in IoT, robotics, or low-level programming, this is where things get REALLY exciting.

🔑 Key Topics:

Microcontrollers (Arduino, ESP32, STM32)
IoT Development
Memory Hierarchy & CPU Architecture

👉 Pro Tip: Build a smart home project (like an automated door lock) to apply what you learn.

8. Soft Skills & Problem-Solving Abilities

🌟 Why It Matters:

Technical skills will get you hired. Soft skills will get you promoted.

🔑 Must-Have Soft Skills:

Communication – Explain complex things in a simple way.
Teamwork – No one likes a lone wolf (at least, not in engineering).
Critical Thinking – Break problems into smaller, solvable chunks.

👉 Pro Tip: Join hackathons, contribute to open-source, or do internships to gain real-world experience.

🎯 Final Thoughts

Being a great computer engineer isn’t about memorizing textbooks—it’s about solving real problems with creativity and curiosity. Keep building, keep experimenting, and most importantly, keep learning.

🚀 What skill do you think is the most important? Let’s chat in the comments!