Equal Employment Opportunity Commission (EEOC.gov)
Redesign for the Modern Era

A complete usability overhaul for one of the most diverse user bases in America.

TOOLS

Adobe XD, Webflow, Adobe Illustrator, Github, Google Suite

DESIGN GOAL

  • Balance technical accuracy with ease of comprehension
  • Increase accessibility to fit user demographics
  • Provide clear, relevant guidance
  • Simplify and refresh UI

PROJECT SCOPE

Unsolicited UX and UI redesign of EEOC.gov, personal project.


Bulk of work was completed working part time over 4 months.

ROLE

Lara Garrison

UX Research, UX Design, Information Architecture, Prototyping, UI Design

(Note: EEOC.gov went through an independent official redesign after the initiation of this project)

What is EEOC.gov, and why does it exist?

The Equal Employment Opportunity Commission (EEOC) is the US agency responsible for enforcing the civil rights legislation which protects American workers from discrimination in their working lives. It covers protection for such significant issues as sex, race, national origin, and disability status.

They are the primary bastion in enforcing our civil rights legislation as it relates to one's ability to earn a living, and therefore play a critical role in American society.

There are three major categories of users, each with different reasons for visiting the site:

Employees

  • Specific policy
  • How and when to register a complaint
  • Possible results

Employers

  • Specific policy
  • How to comply
  • What to do if accused

general researchers

  • General policy
  • Role of EEOC
  • Programs & results

I brainstormed some simple personas to see what an Employee and Employer's needs might look like in real life:

User persona for Employee Sarah BeckettUser persona for Employer Clement Brown

So, is EEOC.gov fulfilling its role?

The nature of their mission gives EEOC.gov an especially diverse user base, and as the official access point for information and action regarding U.S. law, EEOC.gov has a moral obligation to be clear, accurate, comprehensive, and accessible, in order to facilitate fair resolution of disputes for every American.

How well is their current site living up to their mission? I would say, not well:


Majority of the home page is dedicated to information which is irrelevant to most users, and lacks clear CTAs for common issues:

Original Home Page

Information architecture is unclear and seemingly redundant:

Original Sitemap

Content pages are difficult to skim, and lack effective accommodation of user goals:

Original Pregnancy content page

Initial Usability Testing Plan

A quick overview of the original site generated plenty of ideas for improvement, but before starting I wanted to know how actual users interacted with the site, and whether they had the same experience I did.

I recruited 5 individuals for qualitative in-person testing who met the following criteria:


Each was recorded performing 3 tasks:

  1. Find guidance on what to do as an employer charged with discrimination
  2. Find a number to call for information on breastfeeding rights
  3. Find a local EEOC Field Office
View full Usability Testing Plan

Testing Results

  1. Issue: All testers found navigating the site to be confusing and frustrating. Many similar-sounding yet ambiguous page names left them skimming unrelated pages and hitting 'back' multiple times.
  2. Issue: Writing style of the content was difficult to parse for all but one tester. Testers stated that content pages use legal jargon, do not define terms, use verbose and repetitive phrasing to refer to potentially straightforward concepts, contain many links and phone numbers, and that all this together leaves pages very difficult to skim.
  3. Issue: Four out of five testers were unable to complete at least one task (exclusively due to combination of the above issues).
  4. Issue: Three out of five testers appeared to be frustrated or 'deflated' after interacting with the site.
Initial user testing results

Design Goals

I then set out to redesign what a positive EEOC.gov experience might look like, focusing on the following factors:

Initial Prototypes

Lofi Web Task 1: Find advice for chargee.

LoFi Mobile Task 2: Find advice on breastfeeding rights.

User Testing of Prototype

Using the same selection criteria as before, I had 7 new people use the new prototype to complete the same 3 tasks.

Overall, they were able to find the information more quickly, took more of a direct path, and expressed less frustration than users of the original website.

They also gave very useful feedback on lingering pain points, which prompted changes and a second iteration of wireframes:

  1. Issue: Confused about where on website the 'Help Center' feature lands them.
    Change: Added bread crumbs on content pages and distinct 'Help Center' icon throughout site.
  2. Issue: Complained of too many links, and relevant information spread among too many pages.
    Change: Reduced the total number of links and pages (yet retained scannability) by moving select content into expandable drop-down panels.
  3. Issue: During task as employer, slogan was perceived as passive-aggressive and accusatory.
    Change: Relegated slogan to home page only.
  4. Note: Two of seven testers hovered over sitemap button in footer before completing task, but did not click it.
    Change: Added visible sitemap to footer of desktop version.
  5. Change: Tweaks made to copy and visual composition.

High-Fidelity Prototype

Using Adobe XD I created style sheet with a clear, classic design aesthetic, and a set of Hi-Fi user flows:


Task 1: Guidance for Chargee (Web) HiFi

Task 2: Breastfeeding Rights (Mobile) HiFi

Clickable Prototype

Accessibility Notes

Significant accessibility improvements were made in the following realms:

Visual:
Increased use of white space and visual blocks, improved use of headings, increased text size, ensured all color contrast adheres to strictest "AA" standard.

Cognitive: Simplified navigation, simplified writing style, added "Help Center" functionality.

Language: Added visual language selection indicator (flag) and positioned it prominently in the header.

Takeaways

Areas for Improvement

I could have saved time by being more intentional about keeping wireframes separate from content development and style development. I worked on multiple things at the same time as inspiration struck, and that lead to wasted effort as things were iterated upon. In the future I will implement clearer delineations between different design realms to avoid re-work.

Some of the colorful & complex visual backgrounds I used are more vibrant than I would now choose for a service like this, and I think would be more appropriate for a different brand. I would keep the overall UI palette but tone it down to be less playful and more professional.

After I recorded two prototype testers hovering over the sitemap link (but not clicking it), I added an expanded visual sitemap to the footer. At the time I felt unsure about that design choice but decided to prioritize (possibly redundant) functionality above slickness. If I were to spend more time on this project I would do more research to see if users actually find the footer-sitemap useful, and if so, explore ways to make primary navigation better.