Projects would be so much easier if clients understood the vision for our concepts and automatically bought in but that almost never happens. The reality of the job is we need to get other people to buy-in to our work. Not only do we need to get buy in from our internal teams of developers and project managers but we also, most importantly, need buy in from our clients.

Below is a three step process to help clients feel more involved in the design process so you can get client approval and get to work faster.

The Myth of Why

"Accessibility is optional."

Legally Required Accessibility Requirements

It all started with Section 508 of the Rehabilitation Act of 1973 from the American government. This act made it illegal to ignore those with disabilities. It focused on the physical world by giving people the ability to enter buildings with wheelchair ramps and handicap buttons. The Americans with Disability Act of 1990 (ADA) expanded these protections into the world of technology.

Icons are used in applications, websites, marketing materials, you name it. They communicate complex topics, create visual interest, punctuate topics, and draw user focus. One of the easiest things to do to ensure that icons are used correctly across applications is to create and share an icon typeface. These icons can then be added to documents on a computer as a font, or used in your stylesheet to display the icons online or in an application.

For the past several years I've been working with SVGs - a lot. Not surprising to myself, I quickly fell in love with them for all the reasons I love vector art. I have come up with several tricks to get lean, highly manageable SVGs that I want to share with you here.

The most difficult part of any design process can be finding the correct, best, or most successful idea out of all possible ideas out there. In User Experience (UX) we start by finding empathy with the user, researching user preferences, successes and failures, and understanding the needs of the clients. However, even armed with research and understanding, discovering or uncovering the correct solution out of all the possible solutions out in the world can still be problematic. Used appropriately, sketching is a fantastic way to generate new ideas without the usual constraints we put on ourselves with technology.

The heart of creating a LSG is the ability to put your documentation right where it belongs: in the source code. Chances are that you are already documenting your code, which is a great opportunity to take it to the next level by using a style guide generator that can turn those comments into an organized site, letting others (and yourself from the future) know why and what has been done in the code.

While the bulk of your LSG documentation will come from special comments that you add to the source code, you can also create standalone pages where you can host other types of content that are not specific to the code (think of design principles, accessibility guidelines, or pull request guidelines). This gives you the advantage of centralizing your documentation in one place: your application living style guide.