Design and dev should be more joined up

I’ve been catching up on some reading and came across this nugget in The “D” in the DOM by Anthony Jeffery for 24A11y:

To fix it we took the h3 and h4 off of the product names that were being displayed, and placed a visually hidden heading containing the product name before the price of the original and recommended products. This duplication of content was far from ideal, but it was necessary to fix the issue. In hindsight, we should have pressed for a design with a more logical reading order, which would have avoided a suboptimal hack

I’m of the opinion that designers should be able to code. Or, at the minimum, designs should be shown to a front-end developer for critique on implementation (and revision) before they’re shown to any stakeholders.

Posted in Design and Development

Follow along

If you enjoyed this post and want to know when the next one is published, head to Twitter and hit ‘Follow’.

@tempertemper

More posts

Here are a couple more posts for you to enjoy. If that's not enough, have a look at the full list.

  1. How to diff branches in Git

    Turns out it’s pretty easy to look at the differences between two branches in Git. This is useful when coming back to a feature branch after a while.

  2. Git rebase versus merge

    There are two ways to get a branch up to date with master before raising a PR: merge and rebase. Here are pros and cons with each.