Why Starting Small Leads to More Accessible Sites

Accessibility is a critical concern for any website aiming to serve a broad audience. A common pitfall is beginning with a grand vision and only later considering how various users—particularly those with disabilities—will interact with the site. A bottom-up design approach, which builds a site’s foundation on specific user details rather than broad concepts, offers a way to keep those needs central from the first step.

Defining a Bottom-Up Perspective

Traditional top-down design starts with the big picture and breaks it into smaller components. A bottom-up philosophy inverts this process, addressing minute details first and assembling them into a cohesive whole. This method is especially relevant to accessibility because it mirrors the cognitive processes of many neurodivergent people, who research suggests often show a bias toward bottom-up thinking over the top-down approach common in neurotypical users. This includes visual thinkers who process in images, pattern thinkers who see connections, and verbal thinkers who rely on word details.

An analogy for these two methods is how one approaches writing an essay. A top-down writer begins with a central argument and builds an outline. A bottom-up writer might instead freely jot down ideas as they come, find connections, and only later organize them into an outline and final structure.

In web design, bottom-up thinking means starting with the specifics of the user experience. You might first determine a readable layout for a single article, see how that informs other pages, and gradually build up to full site categories. The approach can be even finer: designing a mobile menu placement for better one-handed reach, then building the drop-down content around that choice, which in turn influences the larger layout to accommodate elements lower on the screen. In all cases, the core idea is to begin with the most specific problems a user might face and address them in sequence.

Prioritizing User Needs Over Designer Preference

The primary benefit of a bottom-up method is that it places user needs at the forefront. Top-down approaches can seem organized, but they often produce a site that reflects the designer's own choices and beliefs rather than serving the audience. This is evident in common usability complaints, such as a social media feed that auto-refreshes, breaking the user's place, or a platform that makes watch history difficult to find without a tutorial. Such issues arise when UX is treated as an afterthought. Notably, reports indicate that a vast majority of the largest homepages still contain errors relating to Web Content Accessibility Guidelines (WCAG).

Looking at real-world examples, a multi-billion-dollar holding company's homepage might prioritize a simple, direct presentation of information, but a lack of menus, poor color contrast, and small fonts make it hard to read and overwhelming. In contrast, a UK charity's homepage shows a better focus on user needs with clear menus, a simple but readable color scheme with strong contrast, and a font that aids legibility.

Building Accessibility In, Not Bolting It On

A top-down strategy can necessitate shoehorning features into an existing design. Consider a government agency that builds a site with high-resolution images, bright colors, and interactive charts. They later realize that screen reader users cannot access the image content, keyboard-only users struggle with layered submenus, and the bright colors hinder readability for the visually impaired. Adding captions after the fact disrupts the intended visual flow, and adjusting the colors requires a complete rethink of the palette. If these details had been part of the initial build, they could have been accommodated without compromising the aesthetic.

An example of unintended consequences is a website with numerous menus added to condense information, but their inconsistent placement—some at the top, some at the bottom, plus a scrolling top bar—feels like an afterthought, creating clutter and confusion. Redesigning a system to fix such usability issues is difficult and can introduce errors, with some sites reporting major traffic losses after a redesign. However, a bottom-up alternative that addresses usability from the beginning results in a more functional, accessible website. A museum site, for instance, maintains simplicity with a smaller number of menus all consistently located at the top, making navigation easier and more predictable.

Expanding Awareness of Diverse Needs

Starting from the ground up improves your ability to catch accessibility concerns that you might otherwise miss. When you start with the big picture, it is easy to overlook the details that affect how people actually use the site. Given that an estimated 16% of the global population—around 1.6 billion people—have a significant disability, the range of needs is vast. Many designers lack firsthand experience with these conditions, which makes overlooking them more likely. By asking how everyone can use a specific feature from the start, you can bridge that knowledge gap and create a product that serves a wider population equitably. Building a site with considerations for high contrast, a calm palette, clear typography, and simple menus from the outset ensures that accessibility is a core feature rather than a repair.

When Top-Down Still Makes Sense

A top-down approach isn’t without merit. It’s an efficient way to lock in a consistent brand image, since every decision traces back to one overarching concept. That central idea also creates a clear design hierarchy, which makes it easier for teams to resolve questions quickly by deferring to broader goals or leadership. In many cases, this organization translates into faster design cycles.

However, if serving a diverse audience is the primary objective, bottom-up tends to win out. While it can be harder to keep everyone aligned on a single design philosophy, the approach typically yields a more functional website. Problems surface and get solved early, and the attention to detail is far greater. The trade-off is that these benefits often come with longer design cycles and higher costs.

The right choice may come down to team preference and working style. Some people thrive under top-down direction, while others produce better work in a bottom-up environment. A blended model can also work: start with a top-down vision, then refine and implement it using bottom-up tactics.

Making A Bottom-Up Model Work

If a bottom-up approach aligns with your goals, several strategies can help you put it into practice effectively.

Start With Your Users’ Own Words

Bottom-up design centers on the user, so your existing audience is the logical starting point. Survey customers and site visitors about their experiences, both on your properties and others. Ask them where they hit pain points and what features they wish existed. Look for patterns across responses, and treat those commonalities as your roadmap. WCAG standards are a valuable source of inspiration for accessible functionality, but first-hand user feedback should drive the core mission.

Mine Past Projects For Gaps

Your own history is a rich source of insight. Go through old customer feedback, update logs, and previous sites to identify accessibility gaps you’ve missed before. Use those properties yourself to find barriers, then document every issue you want to avoid in the next build.

Documentation matters here more than you might think. Up to 90% of organizations’ data is unstructured, which makes it nearly impossible to analyze later. By organizing your findings and recording your accessible design process as you go, you’ll make future optimization efforts dramatically easier to execute and measure.

Split Work, Share Context

A bottom-up strategy can be time-consuming, and that’s one reason top-down alternatives remain popular. To counter the slowdown, divide work between smaller teams — but don’t let them operate in silos. Those groups need to communicate regularly so their separate efforts add up to a cohesive whole.

A DevOps approach is particularly well-suited here. DevOps has helped 49% of adopters achieve a faster time to market, and 61% report higher-quality deliverables. It provides structure for both individual, detailed work and team-wide syncs, keeping productivity high even when you’re working from the details up.

Foundations For Accessible, Ground-Up Design

An accessible website is impossible without a detail-oriented philosophy, and bottom-up is that philosophy in action. It’s the most practical way to serve a broader audience across many fronts — expanding your reach into new niches while making the web more equitable in the process.

The Web Accessibility Initiative’s WCAG standards are a practical starting point. They don’t prescribe a design method, but they do spell out the critical user needs and pain points your design should address. The initiative also offers a free Digital Accessibility Foundations course for designers and developers who want a comprehensive baseline before they begin.

Familiarity with these standards and user needs makes it easier to understand your audience before you design a single interface. From there, you can build a platform that meets current requirements and encourages use among people of all backgrounds and abilities.

For further reading, these titles offer solid perspectives on accessibility-centered, user-first design practices:

  • Inclusive Design for a Digital World: Designing with Accessibility in Mind by Regine M. Gilbert
  • Practical Web Inclusion and Accessibility: A Comprehensive Guide to Access Needs by Ashley Firth
  • Don’t Make Me Think, Revisited: A Common Sense Approach to Web Usability by Steve Krug

Pairing bottom-up thinking with resources like these helps you create sites that don’t just meet accessibility standards — they actively invite use by everyone.