Featured

Most organizations have heard of the Americans with Disabilities Act (ADA), but few are clear on exactly how it affects the way they operate their business — especially online. Every US-based business is required by the law to provide full and equal access, regardless of ability, and this is especially true for those that provide some form of public accommodation.

Passed into law in 1990, the ADA was written when only 15% of US households even owned a computer — never mind the current ubiquity of smartphones. However, Title III of the ADA says, in part, that you can’t discriminate against an individual on the basis of disability “in the full and equal enjoyment of the goods, services, facilities, privileges, advantages, or accommodations of any place of public accommodation by any person who owns, leases, or operates a place of public accommodation” and the 9th Circuit Court of Appeals upheld that this extends to the online world in Domino’s v. Robles:

Domino’s website and app facilitate access to the goods and services of a place of public accommodation—Domino’s physical restaurants. They are two of the primary (and heavily advertised) means of ordering Domino’s products to be picked up at or delivered from Domino’s restaurants. We agree with the district court in this case—and the many other district courts that have confronted this issue in similar contexts—that the ADA applies to Domino’s website and app, which connect customers to the goods and services of Domino’s physical restaurants.

The good news is that the basic principles of the ADA are easy to adhere to, even online, and many run in parallel with SEO best practices that you’re likely already following. Here are some of the easiest updates you can make to bring your website into compliance.

Color Contrast

This is the easiest, but most often overlooked, element of your website’s design to check and correct. When choosing a color scheme for your website, ensuring that the text color contrasts well against any background color. You may need to make small compromises on your branding or design, but it will help those with visual impairments (such as color blindness) to view your website. This will also have the added benefit of helping mobile users view your website if they’re outdoors and in bright sunlight.

From a web development perspective, this is a very easy change to make and there are tools, such as WebAIM’s Color Contrast Checker, that can help you.

Alt Text

Your website’s text is easy for screen readers to understand, but the same can’t be said for images, audio, or videos. Instead, they will rely on descriptive alt text that’s written into your HTML to interpret them. Without it, the screen reader may just read back the filename of your content which may be descriptive, but most likely isn’t descriptive enough to provide the full context or experience. 

The good news is that this is very easy to add. Within the img tag, a simple alt=”description” attribute (where “description” is the written description of the content) is all a screen reader will need to know what to read back to the user. And if you’re not writing your HTML from scratch, any CMS will include this option when you upload and add the file.

For the same reason, it’s recommended that you don’t include text embedded within your images or video unless that same text is also included in the alt text.

Semantic HTML

Much of your website can be made accessible just by ensuring that the correct HTML elements are used for their intended purpose and in the correct hierarchy. It’s one of the best accessibility aids that a screen reader can use to properly translate the structure of your website.

Examples of this can include properly nested heading (H1, H2, H3, etc.), paragraph, and list tags. The screen reader will each header out as you progress through the content, notifying you what a heading is, what a paragraph is, etc., it will stop after each element to let the user advance at a pace that is comfortable for them, the user can jump to the next/previous heading, and you can pull up a list of all of the headings to use as a table of contents.

Good semantic HTML also has the added benefits of rendering better on mobile devices and improving your SEO.

Labeling UI Controls

Labeling UI controls refers to making sure that anything you can do or submit on your website is clearly labeled. Examples of this include forms, submission buttons, and order/purchase buttons.

This is best completed through a process called Accessible Rich Internet Applications (ARIA), which is a set of attributes that define ways to make web content and web applications (especially those developed with JavaScript) more accessible, and is built into many common frameworks. It supplements HTML so that these user interactions that are commonly used can be passed to assistive technologies when there is not otherwise a mechanism.

However, there are only varying degrees of support for ARIA based on the operating system and browser being used, as well as the kind of assistive technology the user may require that may interfere with it. 

Also, it’s important to acknowledge that some people who rely on assistive technology may be reluctant to upgrade their software because of the comfort level they’ve built with it. Because of this, it’s more important to use the semantic HTML elements we discussed above whenever possible as it’s more widely supported.

WAVE Evaluation Tool

At Howard Development & Consulting, we like to use WebAIM’s WAVE Evaluation Tool to quickly check our websites and identify any accessibility issues. WAVE is available as a free Chrome extension and provides visual feedback about the accessibility of your web content by adding icons and indicators to the page. 

While no automated tool can tell you if your page is fully accessible, WAVE excels at simulating human interaction and informs you of any accessibility issues. All of the analysis is done within the Chrome browser, which allows for the secure valuation of intranet, local, password-protected, and other sensitive web pages.

Rob Howard in conversation with Susan Boles on the Break the Ceiling podcast

If you’ve read Rob’s Agency Owner’s Guide to Hiring Web Developers, you know that one of his core values is building long-term relationships with both his clients and his team. He treats them as his friends — people he’s going to be working with for many years.

Rob was a recent guest on Susan Boles’ Break the Ceiling podcast to discuss why he prioritizes these long-term relationships and how he orients his business and its offerings to encourage them.

Listen to the full episode to hear:

• Why we offer a hybrid retainer, called a WordPress Assurance Plan, that helps to build long-term partnerships
• Why we offer an industry-leading unconditional 30-day guarantee on our work
• How we infuse relationship-building into every aspect of the agency
• How to create your own unique offerings that embody your personal and company values
• The benefits of crafting all of your services around a long-term recurring relationship model

Trello is a web-based Kanban-style list-making application that’s commonly used by teams to organize project tasks into lists, especially when those teams are using the Scrum project management framework like we do at Howard Development & Consulting.

Or, in Trello’s own words:

Trello is a collaboration tool that organizes your projects into boards. In one glance, Trello tells you what’s being worked on, who’s working on what, and where something is in a process.

Imagine a white board, filled with lists of sticky notes, with each note as a task for you and your team. Now imagine that each of those sticky notes has photos, attachments from other data sources like BitBucket or Salesforce, documents, and a place to comment and collaborate with your teammates.

Now imagine that you can take that whiteboard anywhere you go on your smartphone, and can access it from any computer through the web. That’s Trello!

If you’ve ever worked within the Scrum framework, then you’ll already be familiar with how most project tasks are organized — project backlog, sprint backlog, in progress, blocked, and done. So, given Trello’s layout of boards and lists, it’s a natural fit for these projects.

Let’s look at the basics of this layout.

First, this is a board:

Next, this is a list on a board:

Then, a card within a list:

And finally, the details of the card:

Relating this back to Scrum, you can make the following equivalencies:

• A board is a single project
• A list can be either a backlog, tasks in progress, blocked tasks, or completed tasks
• A card is a task
• The card details contain the details of the task, such as the user story, acceptance criteria, or any relevant files as attachments

But the benefits of Trello aren’t limited to its layout. 

One of the most useful features is that, like many web-based applications, multiple team members can work on the same board at the same time — with each team member able to see changes in real-time. For example, a project owner could be refining a user story or adding attachments that the developer working on the task can access immediately; or, one developer can start to work on a task without the risk of another developer duplicating their work.

Another feature that we like is that Trello is extremely simple to use. The learning curve is minimal; you can create boards, lists, and cards, each with a single click; and, cards can be moved up and down within a list or from one list to another by dragging and dropping them. I’ve worked with a wide range of teams, from developers to HR writers, and never once has Trello’s UI or UX been a barrier to its use.

Finally, Trello is extremely flexible and adaptive to how your teams work best. While we use Trello as a Kanban-style board at Howard Development & Consulting, you can create lists and cards for any purpose and organize them in any way you like. Trello also offers hundreds of power-ups, which are plugins that expand the features available to you. Some of the power-ups are developed by Trello, but most are from third-parties. Either way, they integrate seamlessly with your boards and allow you to fully customize your experience. 

For example, we use Butler to create automations, Google Drive to integrate our files from the productivity suite, Custom Fields to add new fields to our cards, and Slack to connect Trello to our Slack workgroup for automatic notifications, card creation, and to attach conversations to cards.

As a development team that embraces the Scrum framework, we’ve found Trello to be one of the most useful applications for managing our projects. While the bulk of our work is done in Basecamp (which we’ll discuss in another post), Trello allows us to drill down into some projects at a much more granular level — and some of our clients prefer it because of this and its ease of use.

There’s a paradox you’ll discover as you’re building your team: even though hiring great people benefits everyone, nobody really enjoys the process. Agency owners struggle to write job descriptions, conduct interviews, and make judgment calls about the best candidates. Candidates hate the process of searching for opportunities, crafting resumés, updating portfolios, and feeling like they have to sell themselves to one company after another.

I’ve met thousands of creative and technology professionals in my career – and not a single one chose their career because they love sales. We’re creative! We want to create cool stuff! And the hiring process is really just sales by another name – the company sells itself to candidates, and candidates sell themselves to the company – which means we’d all like to get it over with as quickly as possible.

So, how do you best simplify and shorten the hiring process? By making sure your great new web developer sticks around so you don’t have to go through all this again for no good reason.

Data from the Work Institute’s 2019 Retention Report shows that recruiting and training a new employee can cost a business up to four months of their salary, not to mention any lost productivity during that time. The same study reports that the top two reasons for employee attrition are career development (22 percent) and work-life balance (12 percent).

Web developers are no different.

Sometimes they leave for more prestigious opportunities in Silicon Valley. Sometimes they’re seeking a company with more diversity on its team. Sometimes they’re offered an alternative with more flexible hours, more location independence, better pay, or all of the above. I’ve seen this happen in the best economic times and the worst because talented developers always seem to be in demand.

Unless you’re actively working to forge a long-term relationship with your developer, chances are someone else is working much harder to lure them away.

It’s most painful for the agency owner when a developer parts ways with a company and leaves key projects hanging – which, even in the best circumstances, is hard to avoid for an agency that always has many projects at various stages of completion. (Even if someone gives a month’s notice, they can’t realistically wrap everything up before they leave, and it might not be enough time to hire someone to fill their role.) 

None of that sounds like fun to me, so I take a proactive – and, admittedly, somewhat extreme – approach to retention of my team: I want to build an organization that no one wants to leave.

And I want to continuously deliver the benefits – including top-of-market pay, location independence, schedule flexibility, and a culture of diversity and inclusion – that I know will set Howard Development & Consulting apart when competitive tech companies come calling.

Retaining high-end contractors, and how to not be Uber

Among the long list of tragic Silicon Valley outcomes is the perception that all freelancers and independent contractors are abused by corporations, and that everyone would prefer a traditional job if presented the choice. This is absolutely true of gig-economy companies like Uber and its many copycats – they’re so horrible to their drivers that California passed a new law in an attempt to compel them to treat people with dignity and respect. (The fact that this law was controversial should tell you a lot about the ethics of most technology companies.)

However, it’s not right to paint all independent contractors with the same brush. Beyond the realm of Uber, DoorDash, and starving-artist freelancers, there is a whole world of highly paid, highly skilled professionals who actually want to be independent. I know because I am one, and I have hired many of these all-stars to my own web development team.

This hidden world is full of widely experienced, highly skilled developers who are eager to stay with your company for the long-term. They could go work for Google tomorrow, but when they get those offers, they just smile and turn them away. They don’t crave so-called career advancement because they’ve already found their sweet spot. They’re not just earning an income that competes with the best in Silicon Valley, but they’re doing it in a way that provides flexibility and independence that none of the big-name companies can offer.

“Have you heard about those companies whose benefits include game-console rooms, cereal snack bars, top-chef lunches and dinners, nap rooms, laundry service, and free beer on Fridays? It seems so generous, but there’s also a catch: You can’t leave the office.

These fancy benefits blur the line between work and play to the point where it’s mostly just work. When you look at it like that, it isn’t really generous – it’s insidious.

These mainly exist at companies that work 60-plus hours a week, not 40. Sounds more like bribes than benefits, doesn’t it?”

– Jason Fried and David Heinemeier Hansson in It Doesn’t Have to be Crazy at Work

When you hire an experienced freelancer, you get someone with a wide range of experience (they actually do know all those frameworks and languages you’d find in an over-the-top job description). They’re generally business owners, which means they’re solid communicators, and they don’t need nearly as much training or hand-holding as in-house employees who are early in their careers. And because they’ve already arrived at their major goal – running a flexible, independent business – they’re happy to stick with you for years or decades.

Here are the top three ways to retain your best web development talent.

1. Provide a roadmap for career growth

One of the challenges of running a relatively small business is that your most valuable and ambitious team members often look up the ladder and see only you – which means limited growth potential since they’re not likely to take over your role as owner any time soon.

This is one of the areas where a big tech company can really appeal to a young developer – by showing a clear path to a career that’s bigger and better in many quantifiable ways.

To compete with that, you’ll need to get creative about how your company is structured and how you compensate your team as you grow. If you’ve been working with a developer for years, it’s likely they’re thinking about how they can someday become more than “just a developer” – that could mean managing other developers, shifting to sales or account management, or some combination of the two. I encourage you to nurture those instincts when you see them in your team because it means they’re aiming for growth that will be mutually beneficial – they’ll advance their careers and grow their incomes while helping you build a more valuable business.

For a long time, it was difficult for me to embrace growth. We’d get to a place where we felt like we were “sold out,” and then we’d slow down marketing and sales and focus on delivery. That was fun, but also set us up for stagnation and sometimes put too many of our eggs in too few baskets, exposing us to risk if a large client were to end their contract.

And even though we were making plenty of money with that strategy, it had the nasty side effect of stunting my team’s career growth – and more importantly, constraining their imagination about what the future might hold. If my five-person company is still going to be a five-person company in 10 years, then my team’s only real option for a career leap is to move to another company or start their own. 

But if we grow to a team of 25, every one of those first five hires can see a clear path to a management role if that’s what they want to pursue. And as the company’s revenue grows, it gives us the fuel we need to provide bonuses, profit-sharing, or equity opportunities to managers who want to move to the next level. In other words, an ambitious young developer could map out an entire, successful, prestigious career path without ever working for anyone else.

Don’t grow for growth’s sake. Don’t even grow for your sake. Grow for your team, so you can give them the opportunity they deserve to build an admirable and enviable career.

2. The magic of location-independence and flexible hours

That said, if you’re used to hiring entirely in-house, there are some assumptions and approaches you’ll need to change to hire and retain great independent contractors. First, you’ll want to focus on remote work, because freelancers highly value their location-independence and time-flexibility. They’re also great at working remotely, and significantly more efficient than a typical in-house employee since they’ve been honing their work-from-home skills for years. Nobody in this group accidentally gets distracted by Netflix or Facebook after lunchtime.

And because they can take advantage of their location-independence to live wherever they want, they can earn extraordinary incomes while charging cost-of-living-adjusted rates that seem reasonable compared to the out-of-control costs of tech hubs like the San Francisco Bay Area and Seattle.

One of my team members, who lives in Toronto, recently asked a question that would flabbergast many employers: “So, do you mind if I work from Germany for a few weeks a year?”

No, I don’t mind.

In fact, I absolutely love it.

Not only does extreme location flexibility mean a huge quality-of-life boost for my team, it’s a competitive advantage that almost no other employer is willing to match. It means my team can weigh working for my company against working for a Silicon Valley powerhouse – and they can honestly decide that the lifestyle benefits of their current job are way better than the big guys can offer.

If you’re set on hiring in-house, you’ll need to be ready to compete with big tech companies – that means a high-end office space, a well-manicured reputation and an acceptance that, despite your best efforts, most of your best hires will move on when a more prestigious opportunity knocks. This approach works for some companies, particularly if you (as the owner) want to aspire to build a Silicon Valley-style workplace downtown in a major city.

If you prefer longevity, consistency, and working with a highly-skilled, widely experienced technology artisan – and you’re cool with granting more flexibility and independence in exchange for those benefits – hiring a high-end independent contractor is your secret weapon.

3. Independent contractors love retainers

I reached an inflection point in the process of building my team when I finally started selling a significant number of retainers – in my case, WordPress Assurance plans that allowed us to cover software updates, security, and support for sites after we built them. These retainers gave me the predictable revenue I needed to justify hiring a high-end web developer as an independent contractor while also committing to a significant amount of work per month – something that pretty much every freelancer craves.

For years, I took the opposite approach – calling on contractors only when they were needed for specific projects, then going dark for months at a time. The result was that I never had a chance to really nurture a relationship with someone who delivered great work – and even if I found a great candidate, they’d need to go pick up more projects as soon as we were done, which meant they’d potentially be unavailable the next time I needed them. This is a pattern I see creative agencies repeating all the time – they spend a ton of time and energy onboarding a developer, have one or two successful projects, then throw up their hands when that person suddenly gets booked out by other clients for months at a time.

Your goal is to be the client who books the best developers for months at a time.

That means building a flow of retainers (or a very steady stream of one-off projects) that allows you to provide your developer with at least 10 hours of work per week. I’ve found that 20 hours per week is the sweet spot since you’re likely to be the developer’s biggest contract, but they also have room to continue to serve other clients if they choose to do so. Your contract is also much more valuable to them because of its long-term, high-volume nature, which means you can agree on a rate that’s less than what they might charge to a client who only needs them for a few hours once a year.

The continuous engagement allows you to build a true relationship with your developer – so even if they’re working as an independent contractor and aren’t physically in your office, they truly become a part of your team, and they begin to share your goal of growing your company and delivering successful projects for your clients.