The Brief

The Approach

Gaining the Audience’s Trust with Thoughtful Design Details

We learned that many visitors found the MLH website by searching Google with their questions. Many primary audience members would visit the site on their mobile phones, perhaps even listening to its content with their text-to-speech tool. Knowing that, we had to design an accessible experience on any phone, tablet, or desktop device. This increased the importance of a mobile-first design so the pages loaded quickly, the information was clear, and the experience made sense for mobile browsing.

A Modernized Design

The site’s look was outdated, making some visitors feel that it either lacked credibility or didn’t contain the latest legal rules and laws (even though it’s been actively maintained and added to for the past 15+ years!). For the Oomph team, the final designs had to walk a fine line between being authoritative, trustworthy, and comforting. To achieve this, we retained the blue color palette but created slightly softer tones to help create a calming aesthetic.

Our team also limited the amount of photography on the site but ensured that any photos we used represented the diverse groups MLH serves. Icons became a tool to guide the visitor through different topics; regardless of the visitor’s language, the icon could help them understand what information may be within that particular topic.

MLH has also accumulated a lot of content over the years. To help organize its search and topic organization feature, we incorporated content filters according to the information type: articles, how-tos, e-books, and videos. Each category has its own icon, and each icon is represented by a color. This helps unify the search based on the type of content the visitor is seeking.

Color Contrast and Accessibility

From the start, MLH made it very clear that their new designs should comply with both 508 and WCAG 2.1 guidelines — ideally conforming to the highest level of contrast, level AAA. As Oomph created the color palette, we were careful to use only high-contrast colors and document how to use them in a system to ensure that the palette satisfied accessibility guidelines. 

Supporting the Content With Tools

MLH had several existing tools to assist in digesting content. During our discovery phase, we validated the need for these tools and upgraded them. For example, on the content pages, there are options to print, share, listen to the content, and even switch the language as the visitor lands on the page.

Within the main navigation menu, the design included a “Quick Exit” button. This supports visitors who need to abandon the page when, for example, a domestic violence survivor’s abuser re-entered the room.

We cultivated a passion for this feature through our research and have written an article detailing our best practices for implementing a quick exit button. Additionally, we have created a Drupal Module for this feature so that more people can implement this important tool for sites with sensitive content.

Findability of Content Through the Main Menu Navigation

On a larger scale, the primary and secondary navigation menus needed an upgrade. As it stood, the main categories were wall-to-wall across the desktop, and it was hard to determine where a visitor needed to go. The secondary navigation menu read like a table of contents in a chapter book and didn’t allow the visitor to return to other categories. 

We solved for this by creating a survey to test a proposed navigation structure and revised the information architecture (IA). This included a new top menu that supported every step of our primary audience’s journey. We also created a level of navigation that directed visitors to the information they were looking for, no matter how they entered the site. 

Search

For search, we used a multi-filter approach which allows visitors to search both by topic and by content type. This filtering allowed them to find questions that might belong to multiple categories, and to narrow down content to the types they are willing to review.

Proactive vs. Reactive Enhancements

Analytics and user interview results showed that most visitors start their journey on either the homepage or pages that are three or more levels down the navigation. Many also reach the site via a specific Google search. While it is likely they found what they needed, they may not be aware of other information that can help them. To mitigate the risk of bouncing away from the website, we created a “Viewers also reviewed…” component on answer pages that showcased related content more naturally.

Repeating Help Footer

Above the footer, we created a “safety net” to help visitors who have browsed the site for a long time but have not found what they are looking for. If they reached the end of the page, this footer would direct them to more content that may hold their answers.

Previously Viewed

We added a “Previously Viewed” section at the bottom of content pages to remind visitors of the content they have already reviewed. This reduces the burden on the visitor when they ask themselves, “I think I’ve seen that already, but I can’t remember where I saw it.”

The Results

Oomph has been quiet about our excitement for artificial intelligence (A.I.). While the tech world has exploded with new A.I. products, offerings, and add-ons to existing product suites, we have been formulating an approach to recommend A.I.-related services to our clients. 

One of the biggest reasons why we have been quiet is the complexity and the fast-pace of change in the landscape. Giant companies have been trying A.I. with some loud public failures. The investment and venture capitalist community is hyped on A.I. but has recently become cautious as productivity and profit have not been boosted. It is a familiar boom-then-bust of attention that we have seen before — most recently with AR/VR after the Apple Vision Pro five months ago and previously with the Metaverse, Blockchain/NFTs, and Bitcoin. 

There are many reasons to be optimistic about applications for A.I. in business. And there continue to be many reasons to be cautious as well. Just like any digital tool, A.I. has pros and cons and Oomph has carefully evaluated each. We are sharing our internal thoughts in the hopes that your business can use the same criteria when considering a potential investment in A.I. 

Using A.I.: Not If, but How

Most digital tools now have some kind of A.I. or machine-learning built into them. A.I. has become ubiquitous and embedded in many systems we use every day. Given investor hype for companies that are leveraging A.I., more and more tools are likely to incorporate A.I.

This is not a new phenomenon. Grammarly has been around since 2015 and by many measures, it is an A.I. tool — it is trained on human written language to provide contextual corrections and suggestions for improvements.

Recently, though, embedded A.I. has exploded across markets. Many of the tools Oomph team members use every day have A.I. embedded in them, across sales, design, engineering, and project management — from Google Suite and Zoom to Github and Figma.

The market has already decided that business customers want access to time-saving A.I. tools. Some welcome these options, and others will use them reluctantly.

The Risks that A.I. Pose

Every technological breakthrough comes with risks. Some pundits (both for and against A.I. advancements) have likened its emergence to the Industrial Revolution of the early 20th century. And a high-level of positive significance is possible, while the cultural, societal, and environmental repercussions could also follow a similar trajectory.

A.I. has its downsides. When evaluating A.I. tools as a solution to our client’s problems, we keep this list of drawbacks and negative effects handy, so that we may review it and think about how to mitigate their negative effects:

• A.I. is built upon biased and flawed data
• Bias & flawed data leads to the perpetuation of stereotypes
• Flawed data leads to Hallucinations & harms Brands
• Poor A.I. answers erode Consumer Trust
• A.I.’s appetite for electricity is unsustainable

We have also found that our company values are a lens through which we can evaluate new technology and any proposed solutions. Oomph has three cultural values that form the center of our approach and our mission, and we add our stated 1% For the Planet commitment to that list as well: 

• Smart
• Driven
• Personal
• Environmentally Committed

For each of A.I.’s drawbacks, we use the lens of our cultural values to guide our approach to evaluating and mitigating those potential ill effects. 

A.I. is built upon biased and flawed data

At its core, A.I. is built upon terabytes of data and billions, if not trillions, of individual pieces of content. Training data for Large Language Models (LLMs) like Chat GPT, Llama, and Claude encompass mostly public content as well as special subscriptions through relationships with data providers like the New York Times and Reddit. Image generation tools like Midjourney and Adobe Firefly require billions of images to train them and have skirted similar copyright issues while gobbling up as much free public data as they can find. 

Because LLMs require such a massive amount of data, it is impossible to curate those data sets to only what we may deem as “true” facts or the “perfect” images. Even if we were able to curate these training sets, who makes the determination of what to include or exclude?

The training data would need to be free of bias and free of sarcasm (a very human trait) for it to be reliable and useful. We’ve seen this play out with sometimes hilarious results. Google “A.I. Overviews” have told people to put glue on pizza to prevent the cheese from sliding off or to eat one rock a day for vitamins & minerals. Researchers and journalists traced these suggestions back to the training data from Reddit and The Onion.

Information architects have a saying: “All Data is Dirty.” It means no one creates “perfect” data, where every entry is reviewed, cross-checked for accuracy, and evaluated by a shared set of objective standards. Human bias and accidents always enter the data. Even the simple act of deciding what data to include (and therefore, which data is excluded) is bias. All data is dirty.

Bias & flawed data leads to the perpetuation of stereotypes

Many of the drawbacks of A.I. are interrelated — All data is dirty is related to D.E.I. Gender and racial biases surface in the answers A.I. provides. A.I. will perpetuate the harms that these biases produce as they become easier and easier to use and more and more prevalent. These harms are ones which society is only recently grappling with in a deep and meaningful way, and A.I. could roll back much of our progress.

We’ve seen this start to happen. Early reports from image creation tools discuss a European white male bias inherent in these tools — ask it to generate an image of someone in a specific occupation, and receive many white males in the results, unless that occupation is stereotypically “women’s work.” When AI is used to perform HR tasks, the software often advances those it perceives as males more quickly, and penalizes applications that contain female names and pronouns.

The bias is in the data and very, very difficult to remove. The entirety of digital written language over-indexes privileged white Europeans who can afford the tools to become authors. This comparably small pool of participants is also dominantly male, and the content they have created emphasizes white male perspectives. To curate bias out of the training data and create an equally representative pool is nearly impossible, especially when you consider the exponentially larger and larger sets of data new LLM models require for training.

Further, D.E.I. overflows into environmental impact. Last fall, the Fifth National Climate Assessment outlined the country’s climate status. Not only is the U.S. warming faster than the rest of the world, but they directly linked reductions in greenhouse gas emissions with reducing racial disparities. Climate impacts are felt most heavily in communities of color and low incomes, therefore, climate justice and racial justice are directly related.

Flawed data leads to “Hallucinations” & harms Brands

“Brand Safety” and How A.I. can harm Brands

Brand safety is the practice of protecting a company’s brand and reputation by monitoring online content related to the brand. This includes content the brand is directly responsible for creating about itself as well as the content created by authorized agents (most typically customer service reps, but now AI systems as well).

The data that comes out of A.I. agents will reflect on the brand employing the agent. A real life example is Air Canada. The A.I. chatbot gave a customer an answer that contradicted the information in the URL it provided. The customer chose to believe the A.I. answer, while the company tried to say that it could not be responsible if the customer didn’t follow the URL to the more authoritative information. In court, the customer won and Air Canada lost, resulting in bad publicity for the company.

Brand safety can also be compromised when a 3rd party feeds A.I. tools proprietary client data. Some terms and condition statements for A.I. tools are murky while others are direct. Midjourney’s terms state,

“By using the Services, You grant to Midjourney […] a perpetual, worldwide, non-exclusive, sublicensable no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute text and image prompts You input into the Services” 

Midjourney’s Terms of Service Statement

That makes it pretty clear that by using Midjourney, you implicitly agree that your data will become part of their system.

The implication that our client’s data might become available to everyone is a huge professional risk that Oomph avoids. Even using ChatGPT to provide content summaries on NDA data can open hidden risks.

What are “Hallucinations” and why do they happen?

It’s important to remember how current A.I. chatbots work. Like a smartphone’s predictive text tool, LLMs form statements by stitching together words, characters, and numbers based on the probability of each unit succeeding the previously generated units. The predictions can be very complex, adhering to grammatical structure and situational context as well as the initial prompt. Given this, they do not truly understand language or context. 

At best, A.I. chatbots are a mirror that reflects how humans sound without a deep understanding of what any of the words mean. 

A.I. systems are trying its best to provide an accurate and truthful answer without a complete understanding of the words it is using. A “hallucination” can occur for a variety of reasons and it is not always possible to trace their origins or reverse-engineer them out of a system. 

As many recent news stories state, hallucinations are a huge problem with A.I. Companies like IBM and McDonald’s can’t get hallucinations under control and have pulled A.I. from their stores because of the headaches they cause. If they can’t make their investments in A.I. pay off, it makes us wonder about the usefulness of A.I. for consumer applications in general. And all of these gaffes hurt consumer’s perception of the brands and the services they provide.

Poor A.I. answers erode Consumer Trust

The aforementioned problems with A.I. are well-known in the tech industry. In the consumer sphere, A.I. has only just started to break into the public consciousness. Consumers are outcome-driven. If A.I. is a tool that can reliably save them time and reduce work, they don’t care how it works, but they do care about its accuracy. 

Consumers are also misinformed or have a very surface level understanding of how A.I. works. In one study, only 30% of people correctly identified six different applications of A.I. People don’t have a complete picture of how pervasive A.I.-powered services already are.

The news media loves a good fail story, and A.I. has been providing plenty of those. With most of the media coverage of A.I. being either fear-mongering (“A.I. will take your job!”) or about hilarious hallucinations (“A.I. suggests you eat rocks!”), consumers will be conditioned to mistrust products and tools labeled “A.I.” 

And for those who have had a first-hand experience with an A.I. tool, a poor A.I. experience makes all A.I. seem poor. 

A.I.’s appetite for electricity is unsustainable

The environmental impact of our digital lives is invisible. Cloud services that store our lifetime of photographs sound like featherly, lightweight repositories that are actually giant, electricity-guzzling warehouses full of heat-producing servers. Cooling these data factories and providing the electricity to run them are a major infrastructure issue cities around the country face. And then A.I. came along.

While difficult to quantify, there are some scientists and journalists studying this issue, and they have found some alarming statistics: 

• Training GPT-3 required more than 1,200 MWh which led to 500 metric tons of greenhouse gas emissions — equivalent to the amount of energy used for 1 million homes in one hour and the emissions of driving 1 million miles. GPT-4 has even greater needs.
• Research suggests a single generative A.I. query consumes energy at four or five times the magnitude of a typical search engine request.
• Northern Virginia needs the equivalent of several large nuclear power plants to serve all the new data centers planned and under construction.
• In order to support less consumer demand on fossil fuels (think electric cars, more electric heat and cooking), power plant executives are lobbying to keep coal-powered plants around for longer to meet increased demands. Already, soaring power consumption is delaying coal plant closures in Kansas, Nebraska, Wisconsin, and South Carolina.
• Google emissions grew 48% in the past five years in large part because of its wide deployment of A.I. 

While the consumption needs are troubling, quickly creating more infrastructure to support these needs is not possible. New energy grids take multiple years and millions if not billions of dollars of investment. Parts of the country are already straining under the weight of our current energy needs and will continue to do so — peak summer demand is projected to grow by 38,000 megawatts nationwide in the next five years. 

While a data center can be built in about a year, it can take five years or longer to connect renewable energy projects to the grid. While most new power projects built in 2024 are clean energy (solar, wind, hydro), they are not being built fast enough. And utilities note that data centers need power 24 hours a day, something most clean sources can’t provide. It should be heartbreaking that carbon-producing fuels like coal and gas are being kept online to support our data needs.

Oomph’s commitment to 1% for the Planet means that we want to design specific uses for A.I. instead of very broad ones. The environmental impact of A.I.’s energy demands is a major factor we consider when deciding how and when to use A.I.

Using our Values to Guide the Evaluation of A.I.

As we previously stated, our company values provide a lens through which we can evaluate A.I. and look to mitigate its negative effects. Many of the solutions cross over and mitigate more than one effect and represent a shared commitment to extracting the best results from any tool in our set

Smart

• Limit direct consumer access to the outputs of any A.I. tools, and put a well-trained human in the middle as curator. Despite the pitfalls of human bias, it’s better to be aware of them rather than allow A.I. to run unchecked
• Employ 3rd-party solutions with a proven track-record of hallucination reduction

Driven

• When possible, introduce a second proprietary dataset that can counterbalance training data or provide additional context for generated answers that are specific to the client’s use case and audience
• Restrict A.I. answers when qualifying, quantifying, or categorizing other humans, directly or indirectly

Personal

• Always provide training to authors using A.I. tools and be clear with help text and microcopy instructions about the limitations and biases of such datasets

1% for the Planet

• Limit the amount of A.I. an interface pushes at people without first allowing them to opt in — A.I. should not be the default
• Leverage “green” data centers if possible, or encourage the client using A.I. to purchase carbon offset credits 

In Summary

While this article feels like we are strongly anti-A.I., we still have optimism and excitement about how A.I. systems can be used to augment and support human effort. Tools created with A.I. can make tasks and interactions more efficient, can help non-creatives jumpstart their creativity, and can eventually become agents that assist with complex tasks that are draining and unfulfilling for humans to perform. 

For consumers or our clients to trust A.I., however, we need to provide ethical evaluation criteria. We can not use A.I. as a solve-all tool when it has clearly displayed limitations. We aim to continue to learn from others, experiment ourselves, and evaluate appropriate uses for A.I. with a clear set of criteria that align with our company culture. 

To have a conversation about how your company might want to leverage A.I. responsibly, please contact us anytime.

Additional Reading List

• “The Politics of Classification” (YouTube). Dan Klyn, guest lecture at UM School of Information Architecture. 09 April 2024. A review of IA problems vs. AI problems, how classification is problematic, and how mathematical smoothness is unattainable.
• “Models All the Way Down.” Christo Buschek and Jer Thorp, Knowing Machines. A fascinating visual deep dive into training sets and the problematic ways in which these sets were curated by AI or humans, both with their own pitfalls.
• “AI spam is already starting to ruin the internet.” Katie Notopoulos, Business Insider, 29 January 2024. When garbage results flood Google, it’s bad for users — and Google.
• Racial Discrimination in Face Recognition Technology, Harvard, 24 October 2020. The title of this article explains itself well. 
• Women are more likely to be replaced by AI, according to LinkedIn, Fast Company, 04 April 2024. Many workers are worried that their jobs will be replaced by artificial intelligence, and a growing body of research suggests that women have the most cause for concern. 
• Brand Safety and AI, Writer.com. An overview of what brand safety means and how it is usually governed.
• AI and designers: the ethical and legal implications, UX Design, 25 February 2024. Not only can using training data potentially introduce legal troubles, but submitting your data to be processed by A.I. does as well.
• Can Generative AI’s Hallucination Problem be Overcome? Louis Poirier, C3.ai. 31 August 2023. A company claims to have a solution for A.I. hallucinations but doesn’t completely describe how in their marketing.
• Why AI-generated hands are the stuff of nightmares, explained by a scientist, Science Focus, 04 February 2023. Whether it’s hands with seven fingers or extra long palms, AI just can’t seem to get it right.
• Sycophancy in Generative-AI Chatbots, NNg. 12 January 2024. Human summary: Beyond hallucinations, LLMs have other problems that can erode trust: “Large language models like ChatGPT can lie to elicit approval from users. This phenomenon, called sycophancy, can be detected in state-of-the-art models.”
• Consumer attitudes towards AI and ML’s brand usage U.S. 2023. Valentina Dencheva, Statistica. 09 February 2023
• What the data says about Americans’ views of artificial intelligence. Pew Research Center. 21 November 2023
• Exploring the Spectrum of “Needfulness” in AI Products. Emily Campbull, The Shape of AI. 28 March 2024
• AI’s Impact On The Future Of Consumer Behavior And Expectations. Jean-Baptiste Hironde, Forbes. 31 August 2023.
• Is generative AI bad for the environment? A computer scientist explains the carbon footprint of ChatGPT and its cousins. The Conversation. 23 May 2023

THE BRIEF

THE APPROACH

THE RESULTS

Everyone’s been saying it (and, frankly, we tend to agree):  We are currently in unprecedented times. It may feel like a cliche. But truly, when you stop and look around right now, not since the advent of the first consumer-friendly smartphone in 2008 has the digital web design and development industry seen such vast technological advances.

A few of these innovations have been kicking around for decades, but they’ve only moved into the greater public consciousness in the past year. Versions of artificial intelligence (AI) and chatbots have been around since the 1960s and even virtual reality (VR)/augmented reality (AR) has been attempted with some success since the 1990s (That Starner). But now, these technologies have reached a tipping point as companies join the rush to create new products that leverage AI and VR/AR. 

What should we do with all this change? Let’s think about the immediate future for a moment (not the long-range future, because who knows what that holds). We at Oomph have been thinking about how we can start to use this new technology now — for ourselves and for our clients. Which ideas that seemed far-fetched only a year ago are now possible? 

For this article, we’ll take a closer look at VR/AR, two digital technologies that either layer on top of or fully replace our real world.

VR/AR and the Vision Pro

Apple’s much-anticipated launch into the headset game shipped in early February 2024. With it came much hype, most centered around the price tag and limited ecosystem (for now). But after all the dust has settled, what has this flagship device told us about the future? 

Meta, Oculus, Sony, and others have been in this space since 2017, but the Apple device has debuted a better experience in many respects. For one, Apple nailed the 3D visuals, using many cameras and low latency to reproduce a digital version of the real world around the wearer— in real time. All of this tells us that VR headsets are moving beyond gaming applications and becoming more mainstream for specific types of interactions and experiences, like virtually visiting the Eiffel Tower or watching the upcoming Summer Olympics.

What Is VR/AR Not Good At?

Comfort

Apple’s version of the device is large, uncomfortable, and too heavy to wear for long. And its competitors are not much better. The device will increasingly become smaller and more powerful, but for now, wearing one as an infinite virtual monitor for the entire workday is impossible.

Space

VR generally needs space for the wearer to move around. The Vision Pro is very good at overlaying virtual items into the physical world around the wearer, but for an application that requires the wearer to be fully immersed in a virtual world, it is a poor experience to pantomime moving through a confined space. Immersion is best when the movements required to interact are small or when the wearer has adequate space to participate.

Haptics

“Haptic”  feedback is the sense that physical objects provide. Think about turning a doorknob: You feel the surface, the warmth or coolness of the material, how the object can be rotated (as opposed to pulled like a lever), and the resistance from the springs. 

Phones provide small amounts of haptic feedback in the form of vibrations and sounds. Haptics are on the horizon for many VR platforms but have yet to be built into headset systems. For now, haptics are provided by add-on products like this haptic gaming chair.

What Is VR/AR Good For? 

Even without haptics and free spatial range, immersion and presence in VR is very effective. It turns out that the brain only requires sight and sound to create a believable sense of immersion. Have you tried a virtual roller coaster? If so, you know it doesn’t take much to feel a sense of presence in a virtual environment. 

Live Events

VR and AR’s most promising applications are with live in-person and televised events. In addition to a flat “screen” of the event, AR-generated spatial representations of the event and ways to interact with the event are expanding. A prototype video with Formula 1 racing is a great example of how this application can increase engagement with these events.

Imagine if your next virtual conference were available in VR and AR. How much more immersed would you feel? 

Museum and Cultural Institution Experiences

Similar to live events, AR can enhance museum experiences greatly. With AR, viewers can look at an object in its real space — for example, a sarcophagus would actually appear in a tomb — and access additional information about that object, like the time and place it was created and the artist.

Museums are already experimenting with experiences that leverage your phone’s camera or VR headsets. Some have experimented with virtually showing artwork by the same artist that other museums own to display a wider range of work within an exhibition. 

With the expansion of personal VR equipment like the Vision Pro, the next obvious step is to bring the museum to your living room, much like the National Gallery in London bringing its collection into public spaces (see bullet point #5).

Try Before You Buy (TBYB)

Using a version of AR with your phone to preview furniture in your home is not new. But what other experiences can benefit from an immersive “try before you buy” experience? 

• Test-drive a new car with VR, or experience driving a real car on a real track in a mixed-reality game. As haptic feedback becomes more prevalent, the experience of test-driving will become even closer to the real thing.
• Even small purchases have been using VR and AR successfully to trial their products, including AR for fashion retail, eyeglass virtual try-ons, and preview apps for cosmetics. Even do-it-yourself retailer Lowe’s experimented with fully haptic VR in 2018. But those are all big-name retailers. The real future for VR/AR-powered TBYB experiences will allow smaller companies to jump into the space, like Shopify enabled for its merchants.
• Visit destinations before traveling. With VR, you could visit fragile ecosystems without affecting the physical environment or get a sense of the physical space before traveling to a new spot. Visitors who require special assistance could preview the amenities beforehand. Games have been developed for generic experiences like deep sea diving, but we expect more specific travel destinations to provide VR experiences of their own, like California’s Redwood Forest.

What’s Possible With VR/AR?

The above examples of what VR/AR is good at are just a few ways the technology is already in use — each of which can be a jumping-off point for leveraging VR/AR for your own business.  

But what are some new frontiers that have yet to be fully explored? What else is possible? 

• What if a digital sculptor or 3D model maker could create new three-dimensional models in a three-dimensional virtual space? The application for architects and urban planners is just as impactful.
• What if medical training could be immersive, anatomically accurate, and reduce the need for cadavers? What if rare conditions could be simulated to increase exposure and aid in accurate diagnoses?
• What if mental health disorders could be treated with the aid of immersive virtual environments? Exposure therapy can aid in treating and dealing with anxiety, depression, and PTSD.
• What if highly skilled workers could have technical mentors virtually assist and verify the quality of a build? Aerospace, automotive, and other manufacturing industry experts could visit multiple locations virtually and go where they’re needed most.
• What if complex mathematic-based sciences could provide immersive, data-manipulative environments for exploration? Think of the possibilities for fields like geology, astronomy, and climate change.
• What if movies were told from a more personal point of view? What if the movie viewer felt more like a participant? How could someone’s range of experiences expand with such immersive storytelling?

Continue the AR/VR Conversation

The Vision Pro hasn’t taken the world by storm, as Apple likely hoped. It may still be too early for the market to figure out what AR/VR is good for. But we think it won’t go away completely, either. With big investments like Apple’s, it is reasonable to assume the next version will find a stronger foothold in the market.

Here at Oomph, we’ll keep pondering and researching impactful ways that tomorrow’s technology can help solve today’s problems. We hope these ideas have inspired some of your own explorations, and if so, we’d love to hear more about them. 

Drop us a line and let’s chat about how VR/AR could engage your audience. 

Portable Document Format, or PDF, files have been around since 1992, offering a software-agnostic solution for presenting and sharing digital documents. For organizations that existed before the ’90s, PDFs became an easy way to move from physical to digital; they could take the same documents they used to print and now share them digitally as PDFs.

A few years after PDFs were officially launched, CSS came onto the scene as the preferred computer language for styling web pages. Over the following three decades, PDF capabilities grew alongside CSS and other digital technologies, giving creators new ways to lay out and publish their content.

Fast forward to today. Developers worldwide (Oomph among them) have been making websites for a while. We have online forms, interactive databases, and of course, plain old text on a webpage. And yet, PDFs persist.

What’s So Bad About PDFs?

Mobile Phones

Think of the last time you tried looking at a PDF on your phone. First off, there’s the issue of finding it. Depending on your operating system and browser, the file might open right in a new browser tab, or it might download and disappear into some folder you forgot about until this exact moment. (And of course, when you find the folder, you realize this is the fifth time you’ve downloaded this same file.)

Now that you’ve opened the file, you see the tiny text of an 8.5” x 11” page shrunk to a quarter of its intended size. So you pinch, zoom, and drag the page around your screen. You might rotate your phone to the dreaded horizontal orientation to fit a whole line of text at once. If this PDF is a fillable form, you may be simply out of luck on your mobile device unless you’re ready to go down a rabbit hole of separate apps and workarounds.

If, for just a minute, we want to ignore the massive amount of mobile usage — including the 15% of American adults who fully depend on phones for internet access — there’s plenty more cause for PDF concern.

Accessibility

Let’s talk about accessibility. There’s a good chance that your digital properties, including PDFs, are legally required to conform to accessibility standards. This is true for government entities — both federal and more recently, state, local, and district governments, thanks to a Title II update — as well as businesses and nonprofit organizations. 

Beyond the legalities, the CDC reports that about 27% of American adults have a disability. While not all 70 million of these people use a screen reader, we know some people use assistive technology even if they don’t identify as having a disability. (When’s the last time you pressed a button to open a door just because your hands were full or to let a large group of people pass through?) Improvements for the sake of accessibility, more often than not, lead to a more effortless, more intuitive experience for everyone.

While it’s possible to make a PDF accessible, the process for doing so is extensive and involves several manual checks. This can be so time-consuming and specialized that businesses and professionals dedicate themselves entirely to remediating PDFs for accessibility. 

Of course, making a website accessible isn’t as easy as plug-and-play, but accessibility should already be built into the system. Content editors who are not technical professionals can publish accessible content with relative ease on an accessible website platform (as long as we can all remember not to link “click here”) but are typically left to their own devices when it comes to documents.

Brand Reputation

Beyond these critical issues, there are a few more problems that are less vital to users but could have a negative business impact. 

For one, documents like PDFs open up a whole world of styling possibilities. The flexibility might feel like a benefit at first, but give it a little time and I’m certain you’ll start seeing inconsistencies from one document to the next. Add in a few more people preparing these files, and those small differences will pile up, giving users an impression that maybe the business is not quite as put together as they thought. (Not to mention that every change in presentation is asking users to understand a new format, slowing them down or confusing them.) Consistency is key to building a trustworthy brand; every unnecessary variation erodes that trust.

There’s also the near certainty that the information provided in PDFs will need updating. When that happens, you’d better make sure to delete the old file in favor of the new one and update all your links. Since the file format made it easy (or necessary) for users to download the content to their devices, there’s a greater chance that they’ll hold onto old information, even though a newer version is now on the website.

Finally, storing important information in PDFs gives you less control over optimizing for search engines. Google has a tough time reading PDF content (though proper tagging and metadata will help), so these files often rank lower in search results than webpages with similar content. The more that content lives in PDFs and not webpages, the more your SEO will suffer, and the less likely people will be to find and consume your content.

What You Can Do Instead

Like I said, PDFs solved a real problem… 30 years ago. They still have their place today, but more often than not, there’s a better way.

Does It Need To Be a PDF?

When the PDF is just a basic document of text, we recommend turning that into a basic webpage of text. It’s easy to say, but making it happen might mean taking a fresh look at why that information is in a PDF in the first place.

Custom Layout

If you’re using PDFs to create a certain layout, consider how you can achieve something similar through CSS. You might be able to build something you like using the layout and style options already available in your CMS, but you probably won’t create a perfect 1:1 match. 

Any design in a Word or Google document can also exist on a webpage. If there’s a certain design you use time and time again in your PDFs that you just can’t recreate with the web editing tools, you might need some new code. It becomes an exercise in prioritization to weigh the benefits of building a custom layout against the time and cost of doing so. 

Also, remember that a design that works well for a printed page may not be the best design for a responsive webpage. Rather than recreating the exact layout digitally, ask yourself what you’re trying to achieve with the layout and whether there’s a better way to meet that same goal. While unique designs may be more difficult to create on a webpage than a PDF, I’d urge you to consider this a benefit in most cases. Limitations create consistency, which will most likely simplify the experience for both content editors and users.

Designing for Print

Speaking of print, that might be another reason for including PDFs. You may know that a portion of your audience will want to print out the page, maybe to annotate it or to have it on hand as they complete a related task.

In reality, you can serve this user without sacrificing everyone else’s online experience. Developers can use targeted CSS to customize how a webpage will print or export — including what content will display and its styling. Going this route affects how the page will print with the browser tool, and you could even provide a “Print” link if that’s a common need. Ultimately, targeted CSS means the printed content can look as similar or different from the webpage as needed. 

Process 

Another common cause for PDFs is that they’re simply baked into the content publishing process. Whether from fear of changing approved content or a lack of knowledge around what’s possible in the CMS, content teams may use PDF uploads as a fallback for publishing the information quickly and moving on.

A solution here may be to bring your site editor into the process sooner. As the web expert, they can speak to what will work well and what might need to change when moving the content to a webpage. The site editor may need to be heavily involved at first, but their load should lighten as the writers and other team members learn the website’s needs. 

In some cases, it might also be worth building new CMS templates, such as content types. This can be especially helpful for reinforcing consistency when several people manage the website. If the content needs to follow a specific format, a highly structured edit form can act as an outline. You can share this template with the original content creators so that everyone is working toward a shared goal. 

Repurposed Content

Most likely, your organization does more than manage a website. Maybe you have a brick-and-mortar office with brochures and paperwork, or you host webinars with branded slide decks. There are plenty of reasons you might create and share documents other than uploading them onto your website, but you still want the same information available online. And since it’s already put together, the easiest way to share it could be to upload the PDF.

Unfortunately, this is a situation where easy doesn’t cut it. The same tri-fold brochure that looks professional and appealing on a reception desk can be confusing and annoying on a computer or phone. A printed form works great for in-office visitors, but a web form can give users the benefits of autocomplete and progressive disclosure they’ve come to expect online. 

The best experience for your users requires attention to their context. Ultimately, we need to be intentional and thoughtful about what users need in their current situation, which may require different presentations of the same content.

Embrace Digital

We’re not expecting to see the end of PDFs on websites anytime soon. For one, sometimes it’s simply out of your control. Maybe you’re providing an official government form that only exists as a fillable PDF. Even if the document is internally produced, change may be lengthy and involved, requiring buy-in from those who hold the purse strings.

While we wait for the world to change, we can advocate for a better user experience. If a PDF “needs” to stay, maybe you can duplicate the most important content onto the page linking to it. If you have any control over the document itself, you can test for accessibility and make sure it’s properly tagged. Get started with the tools and guidance we’ve collected in this accessibility resources document.

How easily your audience can access your information and services sets the tone for how they perceive your organization. The good news is that there’s so much you can do to make their experience positive, no matter how they choose to interact with your content. If you need help, let us know.

The Brief

Our Approach

The Results

A world without third-party cookies is fast approaching. Big-name browsers like Safari and Firefox already block them by default, and Google Chrome —  the biggest browser of them all —  is set to follow. 

First, a quick refresher: Websites use cookies to store data in your browser specific to that website and other sites. The question, though, is who the website is storing the data for. Third-party cookies store data that allows advertising services to track your behavior on any given site, while first-party cookies are those a website uses for its own purposes. 

Like most things, not all cookies are created equal. As browsers transition to these new defaults, some will make the grade, while others will be blocked for good. What does this mean for your website, and how can you get ahead of the change? We’ll walk you through it. 

Are Cookies Really Going Away? 

That depends on the type of cookies your site uses. Browsers are slowly blocking third-party cookies by default — those associated with cross-site tracking for ad networks like Facebook or LinkedIn — but first-site, or same-site, cookies will remain. 

That means that if retargeting is essential to your paid marketing strategy, you may need to rethink your approach. But any cookies you use to support your site features and functionality can keep on keeping on, assuming your users have agreed to the use of those cookies on your site. For example, you may be able to keep track of previously viewed content and use that information to suggest other relevant content to that user. So don’t say goodbye to your cookie consent services either; you still have to give users the chance to opt out of any first-party cookies. 

Why Now? Haven’t We Been Using Cookies Forever? 

While cookies have been a web-surfing staple for almost as long as we’ve been using the internet, that’s not necessarily a good thing. 

Legislation like GDPR in Europe, the California Consumer Privacy Act, and the New York Privacy Act are tightening restrictions on the use of consumer data, and rapidly increasing cybersecurity threats in recent years have illuminated the risks of large-scale data storage. Consumers have also begun to prize their privacy, realizing that their information is valuable and no organization should be looking over their shoulder as they browse. 

Ultimately, phasing out third-party cookies is about doing what’s best for your users. Making the move now can help instill trust in your website, since users know you aren’t capturing their data behind the scenes. Cookie consent forms also put the data you do use out in the open, showing users that your organization takes their privacy seriously and is prepared to protect it. 

How Will The End of Third-Party Cookies Impact My Industry? 

Not all organizations will feel the shift equally. We’ve seen some verticals get ahead of the curve, while others are naturally less reliant on third-party cookies. Here are some key industry-specific areas to consider. 

Healthcare

Strict privacy laws and regulations like the Health Insurance Portability and Accountability Act (HIPAA) have turned healthcare organizations into pioneers in this area. The Office of Civil Rights even published a bulletin warning organizations about third-party cookies. 

Many of the healthcare brands we support at Oomph are already focused on safeguarding user privacy because they’re used to doing it with medical records. One of our clients, for example, is already exploring adopting an in-house analytics tool hosted on their own server. If your healthcare organization is relying on third-party cookies for any marketing efforts, analytic insights, or other website features, start thinking now about the best way to phase them out. 

Higher Education

Many institutions we work with are using third-party cookies because of digital efforts to drive student enrollment. When implementing personalization cookies, be sure they are implemented with the proper “SameSite” attribute value. Then be sure to engage your vendors; we’ve encouraged many of our higher education clients to explore how their vendors are preparing for this transition.  

Nonprofits

Like higher education, nonprofits should review the vendors and larger ad networks they rely on to build their volunteer base or drive donations. Many nonprofits don’t use these services, but those that do should get ahead of the change, otherwise you may stand to lose an important fundraising channel. 

4 Steps To Prepare for the End of Third-Party Cookies

Cookies, analytics, and cross-site tracking might all sound like areas best left to the pros. But there’s a lot you can do to prepare your organization for the move away from cookies, as well as critical opportunities to pull in a vendor to maintain the functionality you need. 

Audit Your Site

A website audit should always be your first step. Taking stock of the cookies you use is the best way to get a handle on the changes you’ll need to make. Tapping your web partner is a great idea here, too. Your vendor should be able to identify existing third-party cookie warnings, which can help shape your audit. 

For example, while we were updating a client’s email marketing integration recently, Chrome notified our developer that our client’s vendor was sending third-party cookies. We then reached out to the vendor to continue the conversation, knowing that those cookies had to be addressed.

Identify Affected Cookies 

The goal of your audit is to identify all third-party cookies that won’t make the cut. Don’t stop by just listing the cookie, either. Review what function it serves and the role it plays in your organization’s digital footprint. You may have to get rid of the cookie, but that doesn’t mean you have to ditch the strategy it’s tied to. 

Reach Out to Your Vendors

Ask vendors about their plans to handle the transition away from third-party cookies, and feel out whether they’ll still be able to offer the service they currently provide. Consider it a red flag if the vendor is uninformed or unprepared; you might have to seek out alternatives if there’s even the slightest chance your current vendor will be defunct by the end of the year. 

Design Alternatives

The end of third-party cookies is daunting, but it’s also exciting. Take this opportunity to innovate on your users’ behalf. How can you design engaging new experiences that still exceed their expectations? That’s more than possible, so long as you have the right tools in place.

This could be a self-hosted analytics tool you build yourself or new local storage solutions to replace the role of cookies. You might also consider a fully authenticated experience for the users of your site. Lean on a trusted partner here, too. Vendors with website expertise can guide you toward the right solution for you and your users.

Cookies on the Brain? 

For many organizations, this is the most they’ve thought about cookies in years. Third-party cookies have become so essential to building a business online, and yet they’ve largely flown under our radar. But while this change may feel overwhelming, making the switch doesn’t have to be. 

Here at Oomph, we see this as a golden opportunity for organizations to put their users first, and we’re already taking steps to help our clients do just that. 

Need a hand bringing your website into a world beyond third-party cookies? Let’s talk about it.

THE BRIEF

THE APPROACH

Multiple color themes

Site authors choose from five color themes, each supporting light and dark mode viewing. Every theme was rigorously tested to conform with WCAG AA (and sometimes AAA), with each theme based on a palette of 27 colors (including grays) and 12 transparent colors.

User preferences

Site visitors can toggle between light or dark mode or use their own system preference, along with adjusting font sizes, line height, word spacing, and default language.

Mobile first

Knowing that many site visitors will be on mobile devices, each design component treats the mobile experience as a first-class counterpart to desktop.

Examples: The section menu sticks to the left side of the view port for easy access within sections; Downloads are clearly labelled with file type and human-readable file sizes in case someone has an unreliable network connection; galleries appear on mobile with any text labels stacked underneath and support swipe gestures, while the desktop version layers text over images and supports keyboard navigation.

High Accessibility

Every design pattern is accessible for screen readers and mobile devices. Color contrast, keyboard navigation, semantic labeling, and alt text enforcement all contribute to a highly accessible site. Extra labels and help text have been added to add context to actions, while also following best practices for use of ARIA attributes.

Performance aware

Each page is given a performance budget, so design components are built as lightly as possible, using the least amount of code and relying on the smallest visual asset file sizes possible.

THE RESULTS

High-quality content management systems (CMS) and digital experience platforms (DXP) are the backbone of modern websites, helping you deliver powerful, personalized user experiences. The catch? You have to pick your platform first. 

At Oomph, we have a lot of love for open-source platforms like Drupal and WordPress. Over the years, we’ve also built applications for our clients using headless CMS tools, like Contentful and CosmicJS. The marketplace for these solutions continues to grow exponentially, including major players like Adobe Experience Manager, Sitecore, and Optimizely.

With so many options, developers and non-developers with a project on the horizon typically start by asking themselves, “Which CMS or DXP is the best fit for my website or application?” While that is no doubt an excellent question to consider, I think it’s equally important to ask, “Who is going to implement the solution?” 

CMS/DXP Solutions Are More Alike Than You Might Think

I recently attended the annual Healthcare Internet Conference and spoke with quite a few healthcare marketers about their CMS tools. I noticed a common thread: Many people think their CMS (some of which I mentioned above) is hard to use and doesn’t serve them well. 

That may very well be the case. Not all CMS tools are created equal; some are better suited for specific applications. However, most modern CMS and DXP tools have many of the same features in common, they just come at different price points. So here’s the multi-million dollar question: If most of these products provide access to the same or similar tools, why are so many customers displeased with them? 

Common Challenges of CMS/DXP Implementation

Often, we find that CMS users get frustrated because the tool they chose wasn’t configured to meet their specific needs. That doesn’t necessarily mean that it was set up incorrectly. That’s the beauty of many of today’s CMS and DXP products: They don’t take a one-size-fits-all approach. Instead, they allow for flexibility and customization to ensure that each customer gets the most out of the product.

While enticing, that flexibility also burdens the user with ensuring that their system is implemented effectively for their specific use case. In our experience, implementation is the make-or-break of a website development project. These are just a handful of things that can derail the process:

1. The implementation partner didn’t fully understand how their client works and configure features accordingly.
2. The demands of user experience overshadowed the needs of content editors and admins. 
3. Hefty licensing fees ate away at the budget, leaving behind funds that don’t quite cover a thorough implementation. 
4. The project was rushed to meet a tight deadline. 
5. The CMS introduces new features over time that add complexity to the admin or editing experience. 
6. Old features get sunsetted as new capabilities take their place. 

Most of the work we do at Oomph is to help our clients implement new websites and applications using content management systems like Drupal. We have decades of combined experience helping our clients create the ideal user experience for their target audience while also crafting a thoughtful content editing and admin experience that is easy to use.

But what does that look like in practice? 

4 Steps for a Successful CMS Implementation

Implementation can be the black box of setting up your CMS: You don’t know what you don’t know. So, we like to get our clients into a demo environment as soon as possible to help them better understand what they need from their CMS. Here’s how we use it to navigate successful CMS implementation: 

1. Assess the Capabilities of the CMS

The first step can be the most simple at face value. Consider what the CMS needs to do for you, then find a CMS that includes all of those features. Content modeling (more on that below) is a key part of that process, but so is auditing your team’s abilities. 

Some teams may be developer-savvy and can handle less templated content-authoring features. Others may need a much more drag-and-drop experience. Either use case is normal and acceptable, but what matters is that you identify your needs and find both a CMS and an implementation process that meets them. That leads us to the next point.

2. Test-Drive the CMS Early and Often

You wouldn’t buy a car without test-driving it first. Yet we find that people are often more than willing to license a CMS without looking under the hood.

Stepping into the CMS for a test drive is a huge part of getting the content editing experience right. We’ve been designing and engineering websites and platforms using CMS tools for well over a decade, and we’ve learned a thing or two along the way about good content management and editing experiences. 

Even with out-of-the-box, vanilla Drupal, the sky’s the limit for how you can configure it. But that also means that nothing is configured, and it can be difficult to get a sense of how best to configure and use it. Rather than diving into the deep end, we work with our clients to test the waters. We immediately set up a project sandbox that offers pre-configured content types, allowing you to enter content and play with a suite of components within the sleek drag-and-drop interface.

3. Align User Experience with Content Authoring

Beyond pre-configured content and components, our sandbox sites include a stylish, default theme. The idea is to give you a taste both of what your live site could look like and what your content authoring experience might be. Since so many teams struggle to balance those two priorities, this can be a helpful way to figure out how your CMS can give you both. 

4. Finalize Your Features & Capabilities 

While a demo gives you a good idea of the features you’ll need, it might include features you don’t. But discovering where our pre-built options aren’t a good fit is a good thing — it helps us understand exactly what YOUR TEAM does and does not need.

Our goal is to give you something tangible to react to, whether that’s love at first type or a chance to uncover capabilities that would serve you better. We’ve found this interactive yet structured process is the CMS silver bullet that leads to a better outcome. 

Content Modeling

Another key part of our project workflow is what we call content modeling. During this phase, we work with you to identify the many content types you’ll have on your website or application. Then, we can visualize them in a mapping system to determine things like: 

• What relationships exist between these different content types?
• Who should have access to a content type, and what governance should be in place to ensure all content is accurate, on brand, and approved for publishing?
• What features do you need to support content at every level? For example, at the field level, do you need a drop-down with predefined values that only certain people can edit, or do you need an open-text field a content editor can customize? 

With a solid content model in place, we can have a higher level of confidence that our CMS implementation will create the right content editing experience for your team. From there, we actually implement the content model in the CMS as soon as possible so that you can test it out and we can make refinements before getting too far along in the process.

Content Moderation & Governance

Many clients tell us they either have too much or too little control over their content. In some cases, their content management system is so templated or rigid that marketing teams can’t quickly spin up landing pages and instead have to rely on development teams to assist. Other teams have too much freedom, allowing employees to easily deploy content that hasn’t been approved by the appropriate team members or strays from company brand standards. 

Here at Oomph, our mantra is balance. A good content editing process needs both flexibility and governance, so teams can create content when they need to, but avoid publishing content that doesn’t meet company standards. Through discovery, we work with clients to determine which content types need flexibility and which ones don’t. 

If a content type needs to be flexible, we create a framework that allows for agility while still ensuring that users can only select approved colors, font types, and font sizes. We also identify which content needs to be held in moderation and approved before it can be published on the website. 

Taking the time to discuss governance in advance creates a CMS experience that strikes the right balance between marketing freedom and brand adherence. 

Implementation Turns a Good CMS Into a Great One

Modern CMS/DXP solutions have mind-blowing features, and they will only continue to get more complex over time. But the reality is that while picking a CMS that has the features you need is important, how it’s configured and implemented might matter even more. After all, how helpful is it to have a CMS with embedded artificial intelligence if making simple copy updates to your home page is a nightmare? 

Implementation is the “it” factor that makes the difference between a CMS you love and one you’d rather do your job without.

Interested in solving your CMS headaches with better implementation? Let’s talk.

Have you ever waved to someone and they didn’t wave back? Awkward, right? But are you sure they could see you and recognize you? Was the sun in their eyes? Were you too far away? Were you wearing a face mask?

There is a similar situation with your branding on your website. On a smaller mobile device, is your logo legible, or are the words shrunk down and too small? Are the colors high-contrast enough to be seen on a sunny day? Is there consistency between your social media avatar and your website, between your print materials and your digital advertising? Can customers recognize your brand wherever it might be displayed? 

For your brand to be the most successful, it takes a little extra effort to think through all of these possible scenarios. But it’s worth it, or your customers will give you the cold shoulder, whether they intended to or not. 

This extra bit of strategy and planning around your brand is called “Responsive Branding.” Just like responsive design, where your website’s content adapts to the device a customer is using, responsive branding adapts to the device, the medium, and the platform while also considering situations like low light, high light, animated, or static.

Oomph works with organizations across industries to build or refresh responsive brands that serve and delight their users across the full spectrum of digital experiences. Here’s what we’ve learned about responsive branding and our tips for creating one that works. 

What Is Responsive Branding?

Let’s first start with what you’ve probably already heard — responsive web design. Coined by Ethan Marcotte in 2010, the “responsive” part came to mean that a web design responded to the size of the screen, from a phone to a tablet to a widescreen desktop monitor. 

Then came responsive logos. These take the elements of the main logo and adapt them for different sizes and use cases. A logo might have too much detail to be legible as a small social media icon, for example.

Responsive Branding blends these ideas and looks at the design system holistically. A successful responsive brand may include:

• A logo version for different sizes and applications. Variations might include one with the tagline, one without, one with a mark and typeface, one just the name, one just the mark, the possibilities go on!
• Secondary logo options which may include abbreviations, monograms, or different combinations of the main elements
• When applicable, an internationalized version of the wordmark and tagline
• A color palette that can provide variation while addressing accessibility and situations of low light or high glare
• A fluid typography system that provides contrast between sizes within different size media (including print!)
• A fluid spacing system
• Motion when appropriate, like video intros and outtros

Why Responsive Branding Matters

Your business makes a huge investment in building a brand that stands apart from the competition while communicating your personality and value. You are building trust with customers through every interaction. When your brand works well in one situation but not another, it erodes trust. 

A strong brand will be clear, understandable, and memorable for all users in all situations. Whether you have physical locations or digital ones, the brand works with the same consistent strength and message every time.

When you invest in a responsive brand, you: 

• Make your brand more visible. More users can connect with you when you have a brand that’s both recognizable and responsive. Given that 60% of consumers are more likely to buy from a brand they recognize, the opportunity cost of not getting this right is huge. 
• Improve accessibility. Digital accessibility means people of all abilities can use your website and experience your brand. Up to 1 in 4 American adults live with a disability, so a lack of accessibility means fewer customers to reach. For visual brand elements, that means considerations for color blindness, low vision, and cognitive impairments like dyslexia. 
• Create a more consistent brand. Responsive branding equips your team with the tools to express your brand effectively across mediums. That means less time involved in building new assets and a more consistent experience that meets your users’ high expectations.

3 Elements of a Responsive Brand

A responsive brand is more than a shape-shifting logo. The most responsive brands make strategic use of these three elements: 

1. Logo

Your logo is the first piece of your brand that customers will recognize. Using a single-state logo can compromise that impression — a logo that looks great at a large scale is often unintelligible as a small icon. 

Responsive logo designs help ensure your logomark is clear and impactful no matter where you apply it. Beyond the size considerations we mentioned, it should include different formats like horizontal, vertical, and square to support many different digital, social, and print platforms. 

Some other techniques we use to create scalable logos include:

• Dropping words or lettering
• Dropping the icon or image
• Creating an abbreviation version
• Stacking the icon/image and text/lettering
• Combining separate elements into a single icon
• Simplifying details and shapes within logo marks
• Varying thickness and white space to make small logos more legible

Oomph Tip: It’s okay to take several design rounds to get it right. Iterating helps uncover where you’ll use the logo, what it must convey, and which colors and iconography can best support that purpose. We went through several design iterations with our client AskRI before settling on a bold, simple font and clear chat bubble icon that plays off the state of Rhode Island’s distinctive shape. 

Color Palette

A responsive color palette is less about picking complementary shades on a color wheel and more about creating an experience that works in all situations. People with visual impairments and people on low-lit smartphones, for example, rely on high-contrast color combinations to engage with your brand. 

Start by following the Web Content Accessibility Guidelines (WCAG), which include specific recommendations for color contrast ratios. Colors that meet that standard include light text with dark backgrounds, or vice versa. 

Depending on where your brand appears, you may need to adjust your color palette for different settings. For example, your full-color logo might look stunning against a solid white background but becomes illegible against bright or dark colors. A single color logo is useful for some digital use cases like Windows web icons and iOS Pinned Tabs. In non-digital spaces, single color logos are great when color printing isn’t an option, such as with engraving or embroidery. Build out alternate color variations where necessary to make sure your palette works with you – not against you – across your materials. 

Oomph Tip: If your brand palette is already set in stone, try playing with the brightness or saturation of the values to meet recommendations. Often your brand colors have a little wiggle room when combinations are already close to passing corformance ratios. Check out our article about this issue for more pointers.

Typography and Layouts

Responsiveness is also important to consider when structuring web pages or marketing collateral. The most legible layouts will incorporate adaptable typography with clear contrast and simple scaling. 

When selecting a font, be sure to think about: 

• Minimum legible sizes. When is small too small? It depends, of course, but don’t forget older customers, those with low vision, or those in situations that make reading more difficult. Use at least a 16px size for digital products and 12pt size for print. These might change depending on the font, but these sizes are a great place to start.
• Inclusive typefaces. Many designers overlook how understandable certain letterforms appear to be. A way to quickly review is to look at the number 1, lowercase l (L), and uppercase I (i) of any typeface. Then also look at the capital O, the zero, and the lowercase o — 1lI O0o. Can you tell the difference when these characters are out of context? If you can’t, then your customers might have trouble as well. Use your judgment, but also use this trick to expose possible problems with your communication. These five keys to accessible web typography are a great place to start. 
• Scaling ratios. Similar to a musical scale of harmonious notes, a typographic scale is a collection of font sizes that work well together. Using a typographic scale helps to make your text visually appealing and readable for different users across different devices. Some examples include exponential scales, where you multiply the previous font size by a ratio to get the next font size, and Fibonacci sequences, where you add a number from the Fibonacci set to the base font value to get a new size in the scale. 

Oomph Tip: Don’t go it alone. Tools like Typescale and Material UI’s The Type System can simplify typography selection by recommending font sets that meet usability and scalability requirements. And the U.S. Design System has some suggestions as to which typefaces are the most accessible.

How To Get Started With Responsive Branding

To create a responsive brand that resonates, you first have to identify what elements you need and why you need them. That second part is your secret sauce: finding a balance between a design your users can recognize and one that inspires them. 

A design audit can zero in on the needs of your brand and your audience, so you can create a responsive design system that meets both. Not sure where to start? Let’s talk.

Change is the only constant in life, and the same goes for accessibility. Our understanding of how to create truly accessible websites is always evolving, and so are the standards for measuring if we’ve succeeded. 

The most recent update to the Website Content Accessibility Guidelines (WCAG) — released on October 5, 2023 — is the latest attempt to help brands make their digital experiences more accessible for all users.

Don’t panic, WCAG 2.2 isn’t an overhaul. But it does shift the previous standards, delivering more specific and, in some cases, more realistic guidelines that make compliance easier (good news, website managers!). While WCAG 2.2 isn’t cause for alarm, it is something to get out in front of. Here’s what to know about WCAG, the ins and outs of the latest updates, and what it all means for your website.

What Is WCAG, Anyway? 

The Web Content Accessibility Guidelines set the standard for accessible website design. WCAG first issued design guidance in 1999, but the 2008 WCAG 2.0 laid the groundwork for accessibility today. Those standards created a framework for designing websites that are perceivable, operable, understandable, and robust for people of varying abilities. 

2018’s WCAG 2.1 wasn’t a radical departure from its predecessor, but it did add criteria related to mobile devices and users with vision and cognitive impairments. By 2023, accessibility had become widely understood and embraced as essential for inclusive design. That shift helped usher in WCAG 2.2, an update based on multiple years of research and review.

WCAG 2.2 adds nine new success criteria split across three different levels, A, AA, and AAA:

• Level A: This is the WCAG minimum, and it now includes two additional success criteria.
• Level AA: Websites that achieve AA status go beyond the basics. We advise our clients to achieve Level AA as much as possible, depending on their audience. 
• Level AAA: Websites that implement all WCAG guidelines to the highest degree can achieve AAA status. We recommend our clients do so when it suits their website and their users’ needs. For example, a healthcare organization serving older patients may need the highest level of color contrast on its site, while a university serving young students may not.

The WCAG 2.2 update didn’t just add criteria; it made some criteria obsolete, others weaker, and still others more essential than ever. Specifically, WCAG 2.2 promoted 2.4.7 Focus Visible from Level AA to Level A, which means all websites will need visual indicators that show which page feature is in focus. It also changed the recommended size of touch targets, making it easier for designers everywhere to comply.

What WCAG Standard Am I Required to Meet? 

The standard you’re required to meet depends on your industry: 

• State and Local Governments: Organizations in the public sector have the most explicit accessibility requirements. The Department of Justice (DOJ) recently announced a proposed rule that requires state and local governments to meet WCAG 2.1 Level AA standards for their websites and mobile apps.
• Private Sector: Accessibility in the private sector is less regulated, but complying with WCAG guidelines is in your best interest. One reason is that noncompliance could open your company up to a lawsuit. A recent report estimated that 4,220 ADA website lawsuits would be filed by the end of 2023 — almost double the number filed in 2018.

Though there is no official standard in courts, the DOJ has referenced WCAG 2.1 Level AA in past filings. We expect the courts to slowly start referencing 2.2 as cases catch up, but it might take another year for version 2.2 to become the standard. 

While wanting to stay out of court is understandable, legal requirements are only one reason to adopt WCAG. Millions of users around the world use screen readers and other assistive devices. Those users have buying power and they want to engage with your organization, whether that’s registering to vote, signing up for a class, or making an appointment with their healthcare provider. When your website is accessible, you’re able to connect with the broadest audience possible — likely earning more loyal users in the process.

WCAG 2.2 Checklist

While achieving inclusive website design is an exciting prospect, the nuts and bolts of getting there can feel anything but. Here, we help you visualize what the new guidelines mean in practice. You might be surprised by how accessible your website already is. 

Guideline 2.4: Navigable

The standards under guideline 2.4 address anything that will make it easier for users to move through your website.

2.4.11 Focus Not Obscured (Minimum) (AA)

• What It Means: The indicator that signals which page element is in focus is unobscured. “Sticky” elements on the page that don’t move as the user scrolls are the most common culprits that obscure key features. 
• How To Succeed: People who can’t use a mouse need to see where the keyboard has focus. You’ll have succeeded if the item that has keyboard focus is at least partially visible as a user moves from one interactive element to another. 

2.4.12 Focus Not Obscured (Enhanced) (AAA)

• What It Means: This also addresses the visibility of the keyboard focus, but it offers a path for organizations that want to go the extra mile.
• How To Succeed: You can satisfy 2.4.11 with partial visibility, but 2.4.12 requires complete visibility of the keyboard focus. 

2.4.13 Focus Appearance (AAA)

• What It Means: This is an additional measurement criterion for how a website visually indicates what the keyboard focuses on. WCAG recommends a 3:1 contrast ratio for the colors for the focus state vs. the non-focus state and an outline or border around the entire element that is at least 2 CSS pixels thick. Background colors are acceptable as long as they still satisfy the contrast ratio.
• How To Succeed: WCAG 2.1 was ambiguous about what it meant for a focus indicator to be visible. This update clarifies what’s required with clear benchmarks for contrast and thickness/visibility.

Guideline 2.5: Input Modalities

An “input” is an action a user takes to elicit a response from your website — think clicking a button or dragging and dropping a feature. These standards govern the design of those inputs. 

2.5.7 Dragging Movements (AA)

• What It Means: When an interface provides drag-and-drop functionality, there should be a simple pointer alternative that does not require drag-and-drop. This is more relevant for apps and web tools that will need to provide an alternative interface. 
• How To Succeed: This standard serves users who can’t use a mouse or touch screen to drag items. You meet the standard by allowing a user to choose not to use the supplied drag-and-drop functionality unless dragging is considered “essential.”

2.5.8 Target Size (Minimum) (AA)

• What It Means: A minimum size and minimum space for an interactive element allows a user to choose one action without accidentally triggering a nearby action.
• How To Succeed: Some people with physical impairments may not be able to click buttons that are close together. For example, they might hit the “Cancel” button instead of “Submit,” forcing them to start the process over again. You can succeed with this guideline by ensuring the size of the target for pointer inputs is at least 24 by 24 CSS pixels, with some exceptions. 

Guideline 3.2: Predictable

This guideline covers repeating features that may appear across your web pages, such as email sign-up forms or support widgets. 

3.2.6 Consistent Help (A)

• What It Means: When a site or app has a help feature, it appears in the same location consistently.
• How To Succeed: People who need help can find it more easily if it’s in the same place. If a web page contains help mechanisms that repeat across pages, they should occur in the same order relative to other content on the page — unless the user initiates the change. Those help items can include human contact details, human contact mechanisms, self-help options, or a fully automated contact mechanism (i.e., a chat feature). 

Guideline 3.3: Input Assistance

Many websites include elements that help users take certain actions. This could include directing a user to re-enter information or to make sure two fields match. Guideline 3.3 addresses this type of assistance, increasing WCAG’s support of those with cognitive disabilities. This puts the onus on developers to provide simple and secure methods for all users.

3.3.7 Redundant Entry (A)

• What It Means: Ask for information only once in the same session.
• How To Succeed: Some people with cognitive disabilities have difficulty remembering what they entered. If you’re asking the user to re-enter information they previously added, the field must either be auto-populated or the previous answer must be available for the user to select. The exception is if the user is re-entering information essential or required for security or the previous information is no longer valid.

3.3.8 Accessible Authentication (Minimum) (AA)

• What It Means: Don’t make people solve, recall, or transcribe something to log in.
• How To Succeed: Some people with cognitive disabilities can’t solve puzzles, memorize a username and password, or retype one-time passcodes. This guideline considers remembering a password or solving a puzzle (like a CAPTCHA) a cognitive function test. Websites that comply won’t require that step unless the step also provides an alternate authentication method, an assistive mechanism, a test with simple object recognition, or a test to identify non-text content the user provided to the website. 

3.3.9 Accessible Authentication (Enhanced) (AAA)

• What It Means: This builds upon 3.3.8, offering developers a greater opportunity to include users with cognitive disabilities. 
• How To Succeed: The success criteria for 3.3.9 are narrower than for 3.3.8. Websites meet the enhanced standard when a cognitive function test isn’t part of authentication unless the website also offers an alternative authentication method or a mechanism to assist the user with the test. 

Walking the Walk of WCAG

A commitment to accessibility is two-fold. It requires understanding what the most recent guidelines are (the talk) and putting those guidelines into practice (the walk). 

While it might seem like Level AAA accessibility is the way to go, the reality is that accessible websites are nuanced. Some level of accessibility is non-negotiable, but the ideal level for your site very much depends on your industry, your users, and how mature your website is — all factors we can better assess with an accessibility audit. 

If you’re building a new website, embedding WCAG principles is smart. But if you’re WCAG 2.1 compliant and a refresh is a year or two off, WCAG 2.2 may be able to wait. Curious about where your website stands? Let’s talk about it.

“If you don’t make it accessible, it won’t be usable.”

Accessibility was in the air at Drupal GovCon 2023. The topic dominated during conference sessions and attendee conversations alike — not surprising, given its importance for municipalities and governments.   

Users have the same expectations for government websites that they do for any other brand’s site: simple, secure, and accessible user experiences that render well on any device. Much of the content at this year’s GovCon focused on the knowledge, tools, and services government teams need to create accessible sites ( and the challenges that can arise along the way). 

Over three days in Bethesda, Maryland, 600 designers, developers, and other Drupal pros working in government gathered to learn, improve, and innovate. We were lucky to be among them this year. 

Here, we pull back the curtain on what we learned, who we met, and what we’re excited to put into action now that we’re home.  

But First, Why Do We Attend Drupal GovCon? 

Drupal GovCon combines two passions for Oomph: immersing ourselves in all things Drupal and helping our government clients create websites that are truly built for the people. We attended this year’s event to:

• Stay connected to the Drupal community. Oomph has been building in Drupal since 2008, and we love its philosophy of transparency and collaboration. The company stays active by attending events like DrupalCon, participating in its mentorship program, hosting local meetups and events, and contributing new features to Drupal’s ever-growing offerings.   
• Get ideas and inspiration. We valued seeing how other developers use Drupal and speaking with those working in government about what a successful government-developer partnership looks like to them. 

During the event, we networked with fellow developers, squeezed our way into plenty of jam-packed sessions, and presented our own session on accessibility audits. All the while, we looked for opportunities to build upon the Drupal work Oomph has already done for governments and municipalities like RI.gov.

Oomph Presents: The Many Shapes and Sizes of Accessibility Audits

“All websites are not created equal. And neither are accessibility audits.” 

That’s our accessibility philosophy, and it’s also the opening line from our session, which was part of GovCon’s accessibility track. Many attendees hadn’t conducted an accessibility audit before, so this session focused on the basics: what to audit, what tools to use, and actionable deliverables digital teams can use for auditing and implementation. 

Roughly 25 attendees joined to learn key considerations like: 

• The components of an audit. Consider the people and the work. That is, who needs to support the audit (think website owner, development team, and more) and the work the audit will require (defining the scope, choosing the tools, and assigning a budget and timeline). 
• Critical audit tools. The best tools for the job depend on your level of experience. We covered 22 of them and explained which tools to use if you’re a beginner, intermediate, or advanced developer/auditor. 
• Inclusivity. Accessibility makes your website more usable, but it’s important to actively build experiences that include people of all abilities. The Voluntary Product Assessment Template (VPAT) keeps inclusivity front and center.
• Remediation. An audit is only effective if it’s actionable. We offered some tips for turning audit insights into a path to improvement. 

To dive deeper, check out our roundup of accessibility resources here. 

Our Must-Watch Drupal GovCon Sessions

Like all Drupal events, GovCon packed a lot of learning into just three days. While there were insights aplenty in every session we attended, these are the ones to watch from start to finish (or rewatch, in our case). 

Automating Accessibility Testing With DubBot

This session was both pragmatic and inspiring. Presenter Jesse Dyck of Evolving Web started by reminding us all that accessibility is how we ensure truly equal access to information — a key tenet of government communications. 

He then explained how tools like DubBot, an automated testing tool, can perform accessibility testing, provide quality assurance, and even take the pulse on your SEO efforts. Beyond the how-tos, Jesse also offered his own best practices for identifying and managing key data points. 

Navigating the Digital Realm: A Journey Through the Eyes of a Screen Reader User

Amid all the tools and tech, it’s sometimes easy to forget that we’re innovating for people who use assistive devices to access critical information. Matthew Elefant, managing director at Inclusive Web, conducted a live demonstration of how blind and visually impaired people navigate the internet. The session brought a powerful human lens to the challenges people with disabilities face any time they get online when Chris, a tester working with Matthew, remotely walked through his experiences and challenges often including navigating websites with a screen reader. 

Matthew reminded us that accessible websites aren’t necessarily usable and recommended some key opportunities to bridge that gap. 

Editoria11y v2: Building a Drupal-Integrated Accessibility Checker

John Jameson designed Editoria11y v1 to meet an important Drupal need: a robust yet intuitive disability checker. During this session, John walked through his wishlist for Editoria11y v2 — check more complex HTML code and enable users to dismiss non-critical alerts, among others — and explained how he engineered each one (spoiler alert: a long list of mentors). 

His session affirmed the innovative and supportive power of the Drupal community and taught us some of his most effective techniques for building complex web applications. 

Honorable Mention: How AI Works and How We Can Leverage It

Artificial intelligence (AI) is the talk of the tech world, but it’s a bit of a sticky subject for governments and municipalities. Though AI can introduce efficiencies, it can also compromise compliance in the highly regulated public sector. 

Michael Scmid offered some real-world ways to use AI, like training a language learning model (LLM) (think ChatGPT) or generating images — all with a focus on how those tools fit into a decoupled architecture like Drupal. This session is a great watch for anyone interested in understanding options for how to set up your own LLM.

Building Community at GovCon

Year after year, Drupal continues to shine because of the community it builds. At GovCon, we deepened long-held connections and formed some exciting new ones. We even got to meet one of our favorite contractors in person. 

GovCon also echoed many of the conversations our Oomphers are already having. The conference’s timing couldn’t have been better: We brought many of the ideas shared to our recent Squad Summit (our “squads” are dedicated groups of designers, developers, and engineers who serve our clients). Together, our squad explored ways to incorporate emerging accessibility tools into our work and deepened our resolve to build a Web that works for everybody.  

Let’s Talk GovCon

Attended GovCon and can’t get enough of the accessibility conversation? Couldn’t make it but want to brainstorm about how you can put these insights into action on your website? 

Let’s talk about it.

ARTICLE AUTHORS

Kathy Beck

Senior UX Engineer

Hi, I’m Kathy, and I’ve been working with Drupal for over 10 years. As a UX Engineer here at Oomph, I am focused on front-end development and site building and I collaborate with the back-end engineering team and the design team. I am constantly thinking about accessibility and test solutions in multiple browsers as well as screen readers and automated tools.

More About Kathy

Julie Elman

Senior Digital Project Manager

As a Digital Project Manager at Oomph, my main responsibilities include building and maintaining client relationships, managing projects, and collaborating with our talented development and creative teams to execute and deliver top-quality projects.

More about Julie