ADA Compliancy

Being a Ux Designer and Front-End Developer, I am happy to see this big push for the focus on accessibility. When Ux meets ADA compliance it means more than creating a descriptive <alt> from a coding perspective. It means more than highly contrasted layouts from a design perspective. When it comes to interaction, if a user with working vision can immediately take action based on what they’ve read or have seen, then, someone who is visually impaired should be able to act upon something they want to do as soon as they hear it.

Before I consider the design I look at the copy, I read through it and I ask myself if at any point would I as a reader want to take action on any part of this? If so consideration of where links, forms, buttons should be placed should come into play for those who are visually impaired.

We shouldn’t make them read through the entire paragraph or list item (unless it is necessary for them to read through everything before taking action) to access a link or button.

For someone with working sight, sure a large button with some padding and margin around it looks great and makes me want to click it but it is so far removed from that associated paragraph that anyone visually impaired would find that button to be a hassle.

So what would I do? Place a link to take action right there in the midst of the paragraph and written content AND add that lovely giant flat button after the fact.

Give the visually impaired the ability to be instantly gratified.

Correction and Affirming

I am quite fond of children. Crumb-snatchers and high schoolers alike. I have recently completed my second year as a volunteer teacher for ScriptEd. My sister is a teacher not to mention my baby brother has also ventured into teaching for a short while. I think my grandmother would be proud. How can you not like children? They are so bright!

All of them.

As a Ux Designer I believe that if an interface makes you feel dumb or stuck, then the interface is the issue, not the user. I have witnessed toddlers navigate their way through tablets and phones. Not to suggest that those interfaces are intuitive. Children are sponges, they’ve seen their parents, older siblings, someone navigate their way around on those interfaces.

I said all this to say, the same way in which a child knows they are heading down the right path and doing things right is by affirmation. They can observe you taking certain steps but if they don’t see everything, if they skip over something like the fact that you have to enter a password and so correctly, will cause them to try the first time and fail. So they then know to pay closer attention to the keys you press. Thereby learning your password.

Interfaces should be both corrective and affirming but one more so than the other.

70% corrective and 30% affirmative. Corrective in terms of providing a clear path, being immediately clear about if the user has gone off the path they truly wish to be on. Affirmations can be used to do this. The same messages we use to comfort and encourage our users that they are on the right path are the very same messages we can use alert them that they’ve done something they did not mean to do. Providing them a way to back out and correct their path is great here. At the moments when we affirm we should also allow them correct.

Affirmations should not be without the option to review, to go back and adjust.

Day Three: 30 Day Design Challenge

I’ve got a friend who will be attending the Fullstack Developer Bootcamp in two weeks. So to congratulate him and to practice design dark interfaces, I created a concept for his page. He’s a coffee snob and needs practice coding in Bootstrap so here is my Day three submission. A one-pager design.

It is 1366px wide, built on a 12 column layout, where the images cover up the entire screen. It has a sticky global nav bar and the links change as you scroll down. It was a quick 45min mockup.

day006day006e