![99243ILaGaligo.jpg](https://files.steempeak.com/file/steempeak/gibic/KWC2PTTK-99243I-La-Galigo.jpg)

> “The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.” — Tim Berners-Lee, W3C Director and inventor of the World Wide Web

What makes a good website design? Is it the good looks? The fonts, the colors? Is it the user experience? 

I'm not an expert but I just want to share a story.

A couple weeks ago I saw a junior programmer wrote a few lines on the terminal, and in a second, he already have a boiler plate of Nuxt.js based website. it's a good structured website, with good reactive design standard. Now all he has to do is browsing some JavaScript libraries, and make a rapid prototype using bootstrap.

Relatively easy.

But then come the real problem. He should convince his web designer about the prototype and the structure. The designer barely know anything about coding. He know some CSS but that's it. The designer wants to implement many fancy things, cool fonts, big artsy illustration for background. The coder on the other hand wants the design to be simple, to reduce website loading time. 

Both of them has a point. And me, as a person who just love to see them fight, just stood at the door, drinking my home made mojito. Lol.

I was a website designer myself. I've spent some years designing website built with WordPress and Drupal with Adobe Photoshop. There were no Adobe XD, Sketch, or Figma. jQuery was still dominating the frontend. No React, Angular, or Vue. And no Laravel too. 

Here are some example of what our teams were designing, I love the aesthetics by the way:

![REMOTIVI HOMEPAGE.png](https://files.steempeak.com/file/steempeak/gibic/TPhDT5vO-REMOTIVI20HOMEPAGE.png)
<small><center>Our mock-up for the leading Indonesia media research center: remotivi.or.id</center></small>

![Screenshot_20191120 Spektakel3.png](https://files.steempeak.com/file/steempeak/gibic/bvox804e-Screenshot_2019-11-2020Spektakel3.png)
<small><center>Our mock-up for our own product, a portal for Indonesian art & culture activities: spektakel.id</center></small>

***

Seeing how rapid these web design related technology has developed, It's really fascinating. So about that two boys, I can relate to the web designer, at the same time, I understood what that coder wants too.

I'd say both of them are missing one crucial point. At the end of the day, their work would be presented to me and my two other colleagues. And we will ask them about one thing: accessibility. 


> Accessibility is the practice of making your websites usable by as many people as possible. We traditionally think of this as being about people with disabilities, but the practice of making sites accessible also benefits other groups such as those using mobile devices, or those with slow network connections. ([source](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/What_is_accessibility))

But isn't accessibility in web design should thought later. After we settled in mockup, or even, beta launch?

Frankly, I noded my head to that thinking before. But one of my colleagues--*for now, let's call him as Jack*-- is all about paradigm. Unfortunately he is also acts as the loudest guy in the room. So when he talks we tend to listen. 

He strongly believe that accessibility lies on the design paradigm. To design for accessibility means to design for everyone. Mainly, of course designing for the targeted users, but users outside of the target demographic should be included too. Same goes with users with disabilities, and users from different cultures and countries too. 

That means, we expect that the designer would put that paradigm since the start of design development. Not all of accessibility features should be there. God, no! Actually, what we want to hear is more about the argument.  The arguments about how web design should be responsive, fast load, intuitive, that would be basic. No need to argue on that. The technology stacks we have nowadays help a lot. It's easy to design rough mock-up, even to make prototype with these tools. We need to talk more about how the web would be accessible for everyone. 

So it happened. Those boys showed their work to us. 

"Where is the RTL mock-up?" asked Jack.

"*Ummm*.., we think we'll add that feature later..." answered the web designer.

*Wrong answer.*

"I also think that we need to add text-to-speech feature... later...." said the front-end coder, probably as an act of solidarity.

*Oh, no..*

"I mean... we won't targeted users from middle-east, rite?" asked the web designer.

*Triple strike.*

Jack couldn't stand it. Then he start to ranting about his favorite stuff: the design paradigm. An old boring speech. Classic Jack. I yawned.

Jack stopped the rants and asked my opinion for these boys' work.

So I started to talk:

"Good design is good design. It has to be creative, obviously. It has to be intuitive. But it will be much better if that good design works for as many as possible users. Well, of course, planning design for accessibility could add some limit to design itself, but  the key objective is one functional product that work..."

I was in the middle of my speech when Jack interrupted me.

"Please, don't call our user as 'users'. They are people, person with real characters. Calling them user is unethical..." said Jack.

Damn you, Jack. 

I've lost my train of thought. So I went silence. Uncomfortable silence. Awkward.

Anyway, that's the end of the story. I called that meeting off. The boys were not ready. *Heck*, I was not ready. Jack is being too conceptual most of the time. He is typical urban Jakarta guy. 

***

Here are some articles If you want to read more about web accessibility:

* [What is accessibility?](https://developer.mozilla.org/en-US/docs/Learn/Accessibility/What_is_accessibility) 

* [Stop Designing For Only 85% Of Users: Nailing Accessibility In Design](https://www.smashingmagazine.com/2017/10/nailing-accessibility-design/) 

* [Writing CSS with Accessibility in Mind](https://medium.com/@matuzo/writing-css-with-accessibility-in-mind-8514a0007939)


* [Writing HTML with accessibility in mind](https://medium.com/alistapart/writing-html-with-accessibility-in-mind-a62026493412)


* [Web Accessibility In Context](https://www.smashingmagazine.com/2019/06/web-accessibility-context/)

***
Photo by [Paul Green](https://unsplash.com/@pgreen1983) on [Unsplash](https://unsplash.com/)