Corina Murg smiling. Corina has brown hair and light skin. She is wearing a colorful beanie

About

Hey there, I'm Corina.

If you're looking to build an accessible portfolio site, then this space is for you. As a web developer or designer, you have the power (and the responsibility, of course) to create an accessible web and to make sure that every user feels seen and valued. Learn how to do it right from the start.

I'm a self-taught developer with a background in teaching. Somehow, in every learning dev community I've been part of, I've found myself knowing a touch more about accessibility, and from there, the responsibility and the drive to learn even more. I now hold a DHS Trusted Tester Certification and I'm the Accessibility Specialist for Gridiron Survivor, a team of developers building a SaaS product for fantasy football leagues.

I'm here to share what I've learned about accessibility and to help you place accessibility FRONT and CENTER in your development process.

A dashing Patrick Swayze in a still from Dirty Dancing.
He's captured with a pensive gaze, tousled dark blond hair, and dressed in a casual,
dark blue shirt. The text the reads, Let NOBODY put accessibility in the corner.

How to use Web for Everyone

It depends on where you are in your accessibility journey. If you're just starting out, I recommend the Accessibility 101 section.

Has accessibility been part of your development process, and want to make sure that no bug has slipped through? Check out the Your portfolio site section for a list of 12 common bugs.

And if you still have questions, reach out. It will have to be via LinkedIn or Bluesky to make sure your request is legitimate. Share your site, I'll take a look, and then we can find a time to squash some bugs together, if needed.

Why did I build with React?

Because it was a popular library when I started this project in the fall of 2023. I wanted to practice and understand what it takes to build an accessible site with it. I can't argue with my younger self for wanting to be trendy, but a common sense choice would have involved anything that builds a static site.

I am now exploring options for a static version to make sure everyone can access all content without JavaScript. I am aware of the irony here — if you can't enable JavaScript on your device, you won't be able to access my veiled attempt at an apology or explanations about this choice.

A Work Still in Progress

This concerns two aspects of the site: the content, and the accessibility of the site itself. Since I published the site in February 2024, I received very useful feedback, questions, comments, and request for content. While most of the articles are complete, I will update them as needed to clarify or add more information. I'm working on adding more code examples to the existing posts, and two new posts (on accessible forms, and testing for accessibility) as part of the Accessibility 101 series.

As for the accessibility of the site, I have created a public GitHub repository with accessibility issues to be fixed. Before reaching out to report a bug or request a feature, please check the list of issues to see if it has already been reported. You're welcome to add a comment to an existing issue or open a new one.

Thank you for visiting Web for Everyone. I hope you find the content useful.