Accessibility Audit Archives /Tag

What Is a VPAT and Why It Matters
Accessibility in technology is about making sure everyone can use digital products, including people with disabilities. It is not only the right thing to do but also a legal requirement for many organizations. When companies create websites, software, or online tools, they need a clear way to show how accessible those products are.

One common tool for this is called a VPAT, or Voluntary Product Accessibility Template. A VPAT is not a stamp of approval. It does not mean a product is perfect or fully compliant. Instead, it is a clear report that explains how a product meets accessibility rules. In this guide, you will learn what a VPAT is, who needs one, and how to fill it out so others can understand your product’s accessibility.

What Is a VPAT?

The Voluntary Product Accessibility Template is a standard form used to explain how accessible a digital product is. It was first created in 2001 by the Information Technology Industry Council to help vendors follow Section 508 of the Rehabilitation Act. Section 508 is a U.S. law that says technology used by federal agencies must be accessible to people with disabilities.

Since then, the VPAT has grown to cover more rules. Today, it is used to report on Section 508, the Web Content Accessibility Guidelines (WCAG), and the European accessibility standard called EN 301 549. The latest version is VPAT 2.4, with VPAT 2.5 beginning to be used as well.

When a VPAT is filled out, it becomes what is called an Accessibility Conformance Report (ACR). This report is a guide for buyers and procurement teams. It is important to remember that a VPAT is not a certificate. It is simply a trusted format for sharing accessibility information in a way that can be compared, reviewed, and acted on.

Who Needs a VPAT?

VPATs are most often needed by companies that sell to the federal government. Under Section 508, all technology purchased by federal agencies must be accessible. Contractors, vendors, and SaaS providers working with these agencies are expected to provide a VPAT.

But VPATs are not just for federal buyers. State and local governments, universities, and organizations that receive federal funding may also require them. Increasingly, private companies are asking for VPATs before making a purchase.

For vendors, creating a VPAT shows more than compliance. It proves they value inclusivity and transparency. In competitive markets, that can make a difference. Buyers want to work with partners they can trust, and a clear VPAT signals that accessibility is part of your process—not an afterthought.

Which VPAT Version Should You Use?

There are several versions of the VPAT. The right one depends on who will read it.
- Section 508 version: Used in the United States for federal customers.
- EU version: Designed for the European market.
- WCAG version: Focused only on WCAG guidelines.
- INT version: Includes all three standards and is best for global companies.
Most U.S. vendors working with federal agencies use the Section 508 version. Companies with international customers often choose the INT version because it covers multiple standards at once, helping them meet different buyers’ needs with a single report.

Core Elements of a VPAT

A VPAT or ACR has a few main sections:
- Basic Product Details: Name, version, description, date of evaluation, and contact information for the person or team who did the review.
- Accessibility Standards: The rules used in the evaluation, such as WCAG 2.1 or Section 508.
- Testing Methods: How the product was tested, whether through manual checks, automated tools, or by using assistive technology like screen readers.
- Conformance Table: The most important part of the VPAT. Each entry lists the accessibility requirement, shows the level of support, and provides remarks or explanations.
The conformance levels include:
- Supports: The product meets the requirement.
- Partially Supports: The product meets it in some areas but not all.
- Does Not Support: The product fails to meet the requirement.
- Not Applicable: The requirement does not apply to the product.
The remarks section explains the details, such as what works well, what does not, and whether improvements are planned.

Tips for Filling Out a VPAT

When filling out a VPAT, accuracy matters. Accessibility is rarely a simple yes or no. If a product only partly meets a requirement, that should be explained. Avoid vague answers like “supports with exceptions” without details.

The report should be based on real testing. Use manual reviews, automated scans, and assistive technology to see how the product performs. In the remarks, point to real examples, such as how a screen reader reads an image or how easy it is to navigate with a keyboard.

It is also important to make the VPAT itself accessible. Use headings, clear tables, and proper formatting so people who use assistive technology can read it.

The VPAT should be updated often. Products change with new features and fixes, and the VPAT needs to reflect those changes. Always include the date and product version so readers know the information is current.

Finally, be honest. If something does not meet the requirement, say so and explain what you are doing to fix it. Buyers will respect openness more than silence.

Why VPATs Matter Beyond Legal Compliance

VPATs are not just about following the law. They also provide real benefits. Buyers can compare different products more easily. Vendors show they care about accessibility and all their users. Organizations reduce risk by having a clear record of their accessibility work.

In the end, VPATs help build trust. They show that accessibility is a real part of product design and not just an afterthought.

Closing Thoughts

A VPAT turns accessibility testing into a structured report that is easy to understand. It is not a certification and does not claim a product is perfect. Instead, it shows accountability and provides buyers with useful information.

Any organization that offers digital products should see a VPAT as part of an ongoing journey toward accessibility. It is not just about winning contracts but about building products that work for everyone.

If you want help creating a VPAT, understanding the standards, or making sure your documentation is accurate, 216digital can guide you through the process. We are ready to help with clear, practical advice so you can move forward with confidence.
Greg McNeil

August 19, 2025

Testing & Remediation

Accessibility Audit, Accessibility testing, custom accessibility audits, manual audit, Manual Testing, VPAT
How to Fit Accessibility Testing Into Your Sprint
Agile development thrives on fast, iterative progress—and that can make accessibility feel like a hurdle rather than a habit. But accessibility testing doesn’t have to slow you down. In fact, when baked into your sprint process from the outset, accessibility becomes a natural part of your workflow—reducing rework, enhancing code quality, and safeguarding your organization from legal risk.

This guide walks through how to integrate accessibility testing into your Agile sprints without sacrificing speed or innovation. With the right approach, inclusive design becomes a team-wide mindset—and a competitive advantage.

Why Accessibility Testing Belongs in the Sprint

Accessibility testing helps ensure your website or app can be used by people of all abilities, including those who rely on screen readers, keyboard navigation, voice recognition, and other assistive technologies.

Leaving accessibility checks until the end of a project—or worse, after launch—often leads to expensive remediation and a poor user experience. Worse, you could face lawsuits for failing to meet standards such as the Web Content Accessibility Guidelines (WCAG) or U.S. laws, including the ADA and Section 508.

Agile teams are already built for continuous improvement. By incorporating accessibility testing into your sprints, you:
- Catch issues earlier when they’re cheaper to fix
- Avoid bottlenecks during QA
- Improve design clarity and usability for everyone
- Demonstrate a commitment to inclusivity and compliance
Let’s break down exactly how to make this work in practice.

Shift Accessibility Left: Early Planning Wins

To integrate accessibility testing into a sprint, it needs to begin before the sprint starts.

1. Include Accessibility in User Stories

Start by writing user stories with accessibility in mind. Instead of:

As a user, I want to submit a form so I can sign up for updates.

Add accessibility context:

As a screen reader user, I want to submit a clearly labeled, keyboard-navigable form so I can sign up for updates.

This keeps accessibility visible to the entire team and sets the tone for inclusive features from day one.

2. Define Acceptance Criteria

Each user story should include accessibility-related acceptance criteria, such as:
- All buttons must be focusable via keyboard.
- Form fields must include visible and programmatically associated labels.
- Error messages must be conveyed visually and via ARIA alerts.
These criteria guide both developers and testers—and reduce ambiguity when it’s time to validate.

Build Accessibility into Design

Accessibility testing is often easier when designs are inclusive from the start.

3. Collaborate with Designers

Designers should use accessible color contrast, readable font sizes, logical tab order, and meaningful icon labels. Review early wireframes and prototypes against WCAG standards—ideally with tools like Stark or Figma plugins for accessibility.

4. Run Design Reviews

Hold accessibility-focused design reviews during planning or refinement. Spotting issues before development starts saves everyone time. Flag problems like insufficient contrast, unclear buttons, or missing focus indicators.

Develop With Accessibility in Mind

Your dev team is the frontline for accessibility. Setting clear expectations and tools helps them move fast without sacrificing inclusion.

5. Use Accessible Components

Encourage developers to use pre-tested accessible components or frameworks. For example, use accessible modal libraries that manage focus trapping and ARIA attributes out of the box.

6. Lint for Accessibility

Incorporate linters like eslint-plugin-jsx-a11y to catch common accessibility mistakes in code. This provides near-instant feedback—right inside the developer’s editor.

7. Write Semantic HTML

Encourage the use of native HTML elements like <button>, <label>, and <nav> over custom divs and spans. These elements carry built-in accessibility benefits and reduce the need for ARIA workarounds.

Make Testing Part of the Flow

Testing for accessibility isn’t a separate track—it’s part of sprint validation, just like functional testing.

8. Automated Accessibility Tests

Automate what you can using tools like WAVE or Lighthouse. These tools catch issues like missing alt text, ARIA misuse, or low contrast—before code merges.

Run them as part of your CI pipeline, so broken accessibility fails the build just like broken code.

Important Note: Automated tests only catch ~30% of WCAG issues. Manual testing is still essential.

9. Manual Testing in Sprint

Manual checks don’t need to wait for final QA. During development or code review:
- Test keyboard-only navigation
- Use a screen reader (like NVDA or VoiceOver) to verify flows
- Check page headings and tab order for clarity
Spread these tasks across the team so it’s not all on QA or accessibility specialists.

Retrospectives: Keep Improving

Agile is all about continuous learning. Use retrospectives to talk about what worked—and what didn’t—with accessibility during the sprint.

Questions to consider:
- Did we include accessibility in all relevant stories?
- Were any accessibility bugs pushed to a future sprint?
- Are our automated tools giving useful results?
Use this feedback to tweak your workflow, tooling, or documentation.

Tips for Getting Started (or Leveling Up)

If you’re new to accessibility testing in sprints, keep it simple and scale up over time. Here’s a roadmap to get started:
1. Pick one or two automated tools to run in dev and CI.
2. Train your team on basic WCAG principles—especially designers and frontend devs.
3. Set clear accessibility goals in your Definition of Done (e.g., no critical issues, passes keyboard navigation).
4. Assign shared responsibility—accessibility isn’t just the QA team’s job.
5. Start tracking accessibility debt just like tech debt. Tackle it bit by bit.
For teams already doing accessibility work, the next step might be:
- Formalizing a test plan
- Adding assistive tech testing
- Bringing in real users with disabilities for feedback
Don’t Bolt It On—Build It In

Too often, accessibility is treated as an afterthought—an item saved for the backlog or a separate “phase.” But that’s a recipe for stress, rework, and risk.

When you incorporate accessibility testing into your sprint cycle, it becomes routine—not reactive. You don’t have to choose between speed and inclusion. You get both.

And the benefits go beyond compliance. You build better products, open your brand to more users, and reduce friction for everyone.

Need Help Fitting Accessibility Into Your Workflow?

At 216digital, we specialize in helping Agile teams bake accessibility into every phase of the sprint cycle. From audits and remediation to training and ongoing support, our team ensures your products are not only compliant—but more usable and inclusive by design.

Ready to build accessibility into your sprint?

Let’s talk. Schedule a consultation today.
Greg McNeil

July 23, 2025

Testing & Remediation

Accessibility, Accessibility Audit, Accessibility Remediation, Accessibility testing, automated testing, Web Accessibility Remediation, Website Accessibility
When Should Agencies Talk to Clients About Web Accessibility Solutions?
If you’re running a small to mid-size digital agency, you’re used to juggling a lot. Creative direction, project management, client communications, SEO strategy, user experience—the list goes on. And somewhere in that mix, web accessibility often gets lost in the shuffle.

Not because it isn’t important. But because it’s not always obvious where it fits. Should you bring it up during the proposal phase? Wait until design reviews? Or tackle it after launch if an issue comes up?

Here’s the thing: the best time to introduce agency accessibility solutions isn’t “someday.” It’s early. Really early. And the earlier you bring it into the conversation, the easier it becomes to integrate—not just for your client, but for your team, too.

Let’s walk through how accessibility fits naturally into each phase of your process—and how to talk about it in a way that builds trust and positions your agency as a smart, forward-thinking partner.

Start the Conversation About Agency Accessibility Solutions

Accessibility belongs in the earliest conversations you’re having with a client—ideally, during discovery or project planning. When you’re already talking about audience personas, site goals, and technical scope, you’re laying the groundwork for how the entire site will function. This is the perfect opportunity to ask questions like:
- “Do any of your users rely on assistive technology like screen readers or voice navigation?”
- “Are there any compliance requirements or accessibility goals we should be aware of?”
- “Have you ever received feedback from users about accessibility challenges?”
These questions show your client that you’re thinking holistically about their audience. More importantly, you’re helping them see accessibility as a core part of usability and performance—not just a legal concern.

Pro move: include accessibility as a dedicated line item in your proposals. Whether it’s a basic audit, foundational best practices, or a plan for ongoing improvements, showing it in writing reinforces that it’s not optional or extra—it’s essential.

Revisit It During Design Reviews

Design is often where accessibility either starts strong—or goes sideways.

Color palettes, typography, button sizes, spacing—all of these choices affect users with low vision, motor impairments, or cognitive conditions. If you wait until development to flag issues like poor contrast or illegible fonts, you’ll either eat the cost of rework or risk pushing an inaccessible product live.

Instead, build in design checkpoints where agency accessibility solutions are part of the feedback loop. Help clients understand how design decisions translate to real-world usability. For example:
- A gorgeous but pale color scheme might look sleek on a high-end display, but disappear for users with low vision.
- Overly custom cursors or animations may cause issues for people with cognitive sensitivities or motion triggers.
- Fonts without clear letterforms can reduce readability for users with dyslexia or processing disorders.
You’re not just protecting the project from costly changes later—you’re showing the client that good design and accessible design aren’t mutually exclusive. They’re one and the same.

Simple framing tip: “When we design with more users in mind, we increase engagement and reduce support friction. It’s a win for everyone.”

Build Accessibility into Development (Not After)

By the time you hit development, things are moving fast—templates are being coded, features implemented, content loaded. This is where your accessibility groundwork either holds or starts to crack.

Make sure your dev team is on board with basic accessibility practices: semantic HTML, proper heading structure, image alt text, and keyboard-friendly components. These aren’t just nice to have—they’re baseline standards.

And keep your client in the loop, even if you’re not getting deep into technical details. It builds confidence to say:

“We’re coding with accessibility in mind—clean structure, screen reader compatibility, and keyboard navigation all included. If we run into any areas that need custom attention, we’ll flag them and talk through next steps.”

This is also a good time to set expectations around scope. Interactive elements, third-party plugins, or advanced UI components might require extra time to test or fix. It’s better to raise those flags now than scramble after launch.

And yes, it’s still a great place to talk about your agency accessibility solutions and how they support long-term site performance and compliance.

Post-Launch Is Just the Beginning

A successful launch doesn’t mean your work is done—and when it comes to accessibility, it often signals the start of new conversations.

This is when real users interact with the site. It’s also when clients might hear from a frustrated customer, an internal stakeholder with a disability, or worse—receive a demand letter related to ADA compliance.

If you’ve already laid the foundation, your client is more likely to come back to you, not panic-Google another vendor.

Stay proactive. Offer optional post-launch agency accessibility solutions like:
- Quarterly accessibility reviews
- Ongoing monitoring
- Manual and automated testing
- Remediation support and training for content editors
Even light support here builds long-term trust and positions your agency as a reliable, growth-minded partner.

Key message to share: “Accessibility isn’t a one-and-done task. As your site evolves, we’re here to make sure it continues to work for everyone.”

When Legal Risk Enters the Chat

Sometimes, accessibility becomes a priority only after a client gets a legal scare. It’s not ideal—but it’s increasingly common.

In the U.S., accessibility lawsuits have surged in recent years, many of them targeting small and mid-size businesses. And many of those cases are driven by law firms looking for fast settlements, not actual user advocacy.

If a client comes to you in a panic, your role is to stay calm and solutions-oriented. Let them know:
- You’ve handled situations like this before.
- You can help them assess the site’s current status with a thorough audit.
- You’ll work with them to document a remediation roadmap.
- You have trusted partners (or in-house experts) who can assist if the legal stakes escalate.
Your ability to guide them through this process—not with fear, but with structured, proven agency accessibility solutions—can turn a stressful moment into a stronger long-term relationship.

Helpful tone: “You’re not the first to face this, and you’re not on your own. Let’s take smart steps together.”

Make Agency Accessibility Solutions the Default

Ultimately, accessibility should be a standard part of how your agency delivers quality websites—not a surprise line item or reactive fix.

By talking about agency accessibility solutions early and revisiting them often, you’re helping clients:
- Avoid costly legal issues
- Reach broader audiences
- Improve overall usability and performance
- Build reputations as inclusive, thoughtful brands
You don’t have to be an accessibility expert on day one. But you do need to know when—and how—to start the conversation.

Because accessibility isn’t just good practice. It’s good business. And it shows that your agency isn’t just building websites—you’re building experiences that work for everyone.

Ready to Make Accessibility Part of Your Process?

At 216digital, we help agencies like yours turn accessibility into a strategic advantage. From audits to remediation, monitoring to team training, we offer flexible solutions that scale with your projects and support your client relationships.

Schedule an ADA briefing with 216digital, and let’s make every build a little more inclusive—together.
Greg McNeil

June 27, 2025

Testing & Remediation

Accessibility, Accessibility Audit, Accessibility testing, agency accessibility solutions, digital agency, Website Accessibility
How Often Should You Audit Your Website for Accessibility?
You’ve already put in the effort to make your website accessible—and that’s no small thing. But accessibility isn’t something you fix once and forget. As your site evolves, even small changes can introduce new issues. That’s where regular check-ins come in. A web accessibility audit helps you catch problems early, stay aligned with current standards, and keep your site working for everyone.

So how often should you audit your site to maintain that progress? The answer depends on what’s changing—and when. In this article, we’ll break down the key moments when an audit makes sense, the risks of letting things slide, and how ongoing monitoring can help you stay ahead.

Why Web Accessibility Audits Are Critical

A web accessibility audit reviews your website’s design, code, and content to identify barriers that could make it hard—or even impossible—for people with disabilities to use your site. These audits typically test against the Web Content Accessibility Guidelines (WCAG) standards, the ADA (Americans with Disabilities Act), and other regulations.

The risks of not auditing regularly are real for small to midsize businesses. Over the past few years, digital accessibility lawsuits have skyrocketed. In 2024 alone, more than 4,000 web accessibility lawsuits were filed under the ADA—and many of those targeted businesses that were unaware they had an issue.

The cost of defending even a small ADA lawsuit can easily reach tens of thousands of dollars, not to mention the damage to your brand’s reputation. Proactive audits help you spot and fix issues early, keeping your business protected and your customers happy.

When Should You Audit Your Website for Accessibility?

While accessibility should be baked into your website maintenance plan, certain milestones require a full web accessibility audit.

1. After a Website Redesign or Major Update

If you’ve recently rebranded, relaunched, or significantly redesigned your site, it’s critical to schedule a full accessibility audit. Even small navigation, layout, or feature changes can unintentionally introduce new barriers. Testing right after major updates ensures you catch and fix issues before customers encounter them—and before a potential lawsuit arises.

2. Before Launching New Features or Products

Rolling out a new e-commerce section? Adding a chatbot? Introducing video content or online booking? Before new features go live, a web accessibility audit should be part of your quality assurance checklist.

New code, third-party integrations, and interactive tools can create accessibility gaps. Testing pre-launch helps ensure all users can interact with the new elements, no matter what device or assistive technology they’re using.

3. Annually (at Minimum)

Even if your site hasn’t changed much, accessibility standards, best practices, and legal expectations evolve over time. Conducting a comprehensive web accessibility audit at least once a year ensures your site complies with current WCAG standards (currently WCAG 2.1 and moving toward 2.2) and applicable regulations.

Think of it like an annual checkup for your digital presence: it’s much easier and cheaper to maintain accessibility than to fix major problems down the road.

4. After User Feedback or Complaints

If a customer or visitor flags an accessibility issue, that’s a signal to audit right away—not just the problem area but the entire site. User feedback is invaluable because it often reveals real-world issues automated scans might miss. Addressing concerns quickly shows that your business takes accessibility seriously and is committed to serving all users.

5. When Laws or Guidelines Change

New accessibility laws, updates to WCAG standards, or changes in court interpretations can raise the bar for compliance. For instance, the Department of Justice recently released new guidance for web accessibility under Title II of the ADA. When legal standards shift, a fresh audit can make sure you’re aligned with the latest requirements.

Why Ongoing Monitoring Matters

While annual or event-based audits are critical, they’re not enough. Websites are dynamic—they grow, change, and update constantly. New products, marketing campaigns, and blog posts can all introduce accessibility problems over time.

That’s where ongoing accessibility monitoring comes in.

At 216digital, we developed a11y.Radar, a proactive monitoring service that continuously scans your site for accessibility issues. a11y.Radar doesn’t replace manual audits (human expertise is still key!), but it acts as an early warning system—catching errors before they snowball into bigger problems.

With a11y.Radar, you can:
- Receive real-time alerts about accessibility regressions
- Track ongoing improvements
- Maintain continuous WCAG compliance
- Reduce your risk of surprise lawsuits
This approach helps you move from a reactive stance (“fix it after a lawsuit”) to a proactive one (“prevent lawsuits by staying accessible”).

The Cost of Skipping Regular Web Accessibility Audits

Many small to midsize businesses skip regular accessibility audits because of perceived costs or time commitments. But the truth is, not auditing can cost far more.

Ignoring accessibility can lead to:
- ADA lawsuits and expensive legal settlements
- Court-ordered website remediation under tight (and expensive) deadlines
- Loss of customers who can’t use your site
- Negative publicity and damage to your brand’s reputation
- Higher remediation costs later, compared to maintaining accessibility from the start
Investing in regular audits and monitoring is like insurance for your website—and your business future.

How 216digital Can Help You Stay Compliant

At 216digital, we specialize in helping businesses of all sizes navigate the world of web accessibility with confidence. Our phased approach includes:
- Risk Mitigation Audits: A focused first-pass audit to quickly catch and fix high-risk issues.
- Real World Accessibility Audits: Deep manual testing with screen readers, keyboard-only navigation, and assistive technologies to find real-world barriers.
- Ongoing Monitoring with a11y.Radar: Continuous scanning and reporting to help you maintain compliance and stay ahead of risks.
We believe accessibility isn’t a one-time project—it’s an ongoing commitment. That’s why our services are designed to be flexible, scalable, and tailored to your business needs.

Whether starting from scratch, redesigning your website, or needing help managing compliance over time, 216digital can help you build and maintain a site that works for everyone—and protects your business simultaneously.

Keep Progress on Track with Confidence

Accessibility is never truly finished—but that’s a good thing. It means you have an opportunity to keep improving, keep welcoming, and keep your business open to everyone. Staying compliant isn’t about chasing checklists—it’s about maintaining the trust you’ve already worked hard to earn.If you’re wondering whether now is the right time for your next audit, it probably is. A quick conversation can help clarify where you stand and what steps make sense next. Schedule a free ADA accessibility briefing with 216digital, and let’s keep your site moving forward—securely, inclusively, and confidently.
Greg McNeil

April 28, 2025

Testing & Remediation

Accessibility, Accessibility Audit, Accessibility testing, automated testing, manual audit, Manual Testing, Website Accessibility
What to Expect from an Accessibility Audit
Running a business is no small feat. Between managing daily operations, keeping customers happy, and staying on top of your digital presence, it’s easy to overlook something like web accessibility. But in today’s world, where more users rely on assistive technology to browse online, accessibility is no longer optional—it’s essential.

That’s where an accessibility audit comes in. It’s a smart, proactive step that helps you understand how well your website works for people with disabilities and where improvements are needed. It’s not just about avoiding legal trouble—it’s about creating a better experience for all your visitors.

Let’s break it down so you know exactly what to expect.

Why Accessibility Matters

Reaching Every Visitor

Web accessibility is about making sure everyone can use your website—no matter their ability. That includes people who rely on screen readers, keyboard navigation, or voice control, as well as those with visual, hearing, or cognitive challenges.

A more accessible site leads to:
- Better user experience
- Improved search engine visibility
- Increased customer trust
It’s a win for your users and your business.

Reducing Legal Risk

ADA-related lawsuits over inaccessible websites are on the rise, and many target small to mid-sized businesses. In fact over 67% of lawsuits in 2024 were targeting businesses with an annual revenue under $25 million or less.

These cases can be stressful and expensive—even if the issues weren’t intentional.

A professional accessibility audit helps you spot and fix issues early, protecting your business while showing your commitment to inclusion.

What Is an Accessibility Audit?

An accessibility audit is a full review of your website to find any barriers that might stop people with disabilities from using it. These barriers could be anything from missing image descriptions to forms that don’t work with a screen reader.

The audit is based on the Web Content Accessibility Guidelines (WCAG), which provide a clear set of standards for accessible web design. Following WCAG helps ensure your site meets legal requirements—and, more importantly, that it works for everyone.

The Accessibility Audit Process: Step-by-Step

Here’s what typically happens during a full accessibility audit:

Initial Consultation & Scope Definition

The process starts with a conversation. You and your audit team will review your website’s goals, user flows, and top-priority pages—like your homepage, checkout process, or contact form. This helps focus the audit on what matters most.

Automated Testing

Automated tools run quick scans to catch common issues like:
This is a great first step, but automated testing only catches part of the picture. That’s why manual checks are so important.

Manual Evaluation

Accessibility specialists then take a deeper look at your site. They’ll test things like:
- Can users navigate with just a keyboard?
- Are screen readers reading content in the correct order?
- Do buttons and links have clear, accessible labels?
Manual testing finds the issues that machines often miss—and ensures your site works for real people in real situations.

User Testing with Assistive Technology

In some cases, the team may bring in people who use assistive tools daily—like screen readers or alternative input devices—to test your site. Their feedback offers invaluable real-world insight that helps uncover problems no tool or developer could spot alone.

Documentation of Findings

Once testing is done, you’ll receive a report that includes:
- A list of all issues
- Where each problem exists
- The specific WCAG criteria it violates
- Visual examples and code references for clarity
This report serves as your roadmap to fixing issues efficiently.

Prioritization of Issues

Not all issues are created equal. The audit team will help you prioritize based on the following:
- How severe the issue is
- How many users it might impact
- Whether it poses a legal risk
This lets you address the biggest barriers first and build a smart action plan moving forward.

Remediation Recommendations

Finally, you’ll receive clear, actionable guidance for fixing each issue. These recommendations will be tailored to your site’s platform, content, and team capacity. Some fixes might be quick, while others may take more planning—but you’ll know exactly what to do and where to start.

What Happens After the Audit?

Implementing Fixes

After the accessibility audit, it’s time to put the findings to work. Your team—or a trusted partner like 216digital—can help implement those changes, making sure they align with best practices while preserving your brand’s design and functionality.

Team Training

To keep your site accessible over time, it helps to train the people who update it. That could mean a short session on how to use alt text or a checklist for adding new content. A little knowledge goes a long way in preventing future issues.

Ongoing Monitoring

Accessibility isn’t something you check off once and forget about. Websites are living things—they change, grow, and update over time. That means new accessibility issues can pop up without warning, especially as content is added or platforms evolve.

That’s why regular monitoring is key. Running periodic scans, reviewing key pages, and staying alert to new barriers helps you maintain accessibility long after the initial audit. Tools like a11y.Radar, 216digital’s ongoing monitoring service, are designed to make this easier. It quietly keeps tabs on your site, flags issues early, and helps ensure your site stays in line with accessibility best practices—without the need for constant manual checks.

Your Website’s Future Just Got Brighter

A professional accessibility audit gives you more than just a report—it gives you peace of mind. It’s a smart, future-focused way to protect your business, improve your site, and welcome every visitor who comes your way.

At 216digital, we specialize in helping small to mid-sized businesses make sense of accessibility. Our expert-led audits, clear documentation, and hands-on remediation support make the process easy to follow and effective to implement. We help you go beyond compliance—to a website that’s truly inclusive.

If you’re ready to create a better experience for everyone and reduce your legal risk, let’s talk. A more accessible site isn’t just better for users—it’s better for business.
Greg McNeil

April 15, 2025

Testing & Remediation

Accessibility, Accessibility Audit, Accessibility testing, automated testing, manual audit, Web Accessibility, Website Accessibility
How Automated Scans Help (and Fail) Accessibility
Have you ever clicked on a website and immediately gotten lost because nothing seemed to work the way you expected? Maybe you couldn’t find the right button, or the page layout was all over the place. Now imagine facing those same frustrations but with the added challenge of a visual, auditory, or motor disability. Navigating the web shouldn’t feel like an obstacle course—it should be intuitive and inclusive for everyone.

If you’re a website owner or business owner in the United States, you might already know that accessibility is becoming more than just a nice-to-have. It’s a key part of good customer service, protects you from legal risks, and, quite simply, it’s the right thing to do. But where do you start?

One of the first steps many people take is running automated scans.

These scans promise a quick way to spot accessibility issues on your site. Yet, while they can be extremely helpful, they’re far from perfect. In this article, we’ll explore the ups and downs of automated scans—what they can do, where they fail, and how to blend them into a solid strategy that also includes manual testing and expert help.

What Are Automated Accessibility Scans?

Automated scans are software tools that crawl through your website’s code, looking for red flags based on standards like the Web Content Accessibility Guidelines (WCAG)). Think of these tools like the spellcheck in your word processor: they can spot a lot of mistakes, but they can’t always tell you if you’re using the right words in the right context.

What Do Automated Scans Detect?

Plenty of free and paid tools exist. Some are browser extensions (like WAVE or Google’s Lighthouse), while others are built-in services that run regular checks on your website. They’re great at picking up on common coding issues such as:
- Missing or poorly written alternative text on images
- Low color contrast between text and background
- Improper heading levels (skipping from an H1 to an H3 without an H2, for example)
- Misapplied ARIA attributes
- Certain missing form labels
If your site has glaring accessibility mistakes, automated scans can flag those quickly. They’ll often give you a handy list of what’s wrong, along with references to WCAG guidelines or best practices on how to fix each issue. That’s a huge benefit if you’re new to accessibility and need a push in the right direction.

How Automated Scans Can Help You

Let’s look at some of the biggest advantages of automated scans—and how they fit into your overall web development workflow.

Speed and Efficiency

Manual reviews take time, especially for large websites. An automated tool, on the other hand, can process hundreds or even thousands of pages in a shorter timeframe. This is especially handy if you regularly add or change content.

Spotting the “No-Brainers”

Many accessibility issues are straightforward coding mistakes—like forgetting to add “alt” text to images. Automated scanners are perfect for picking up on these. They’re quick, consistent, and thorough in locating these common errors.

Routine Monitoring

Some automated scan tools offer scheduled checks, which is terrific for ongoing maintenance. You can set them to run weekly or monthly scans and then get alerts if something new pops up, letting you address problems before they spiral.

Raising Awareness

For those brand-new to digital accessibility, automated tools can serve as a mini crash course. They highlight rules like ensuring sufficient color contrast or labeling form fields properly, helping you learn accessibility basics as you go.

Ease of Use

Many automated scanners come with user-friendly dashboards or plugins. You don’t have to be a coding genius to interpret most of the results. Often, the tool itself provides guidance on how to fix whatever it finds.

The Real-World Limitations of Automated Scans

As powerful as they are, automated scans also have notable blind spots (no pun intended). If you rely solely on these tools, you could end up with a site that technically passes certain checks but still feels like a maze for users with disabilities.

Lack of Context

A scanner can confirm if there’s alt text on an image, but it can’t determine if that text is accurate or helpful. An automated report might be happy to see you labeled your button as “Button,” but that label doesn’t tell a user what the button actually does.

Missing Nuances

Some accessibility aspects aren’t purely code-based; they’re about user experience and clarity. For example, is your site’s language too complicated for people with cognitive disabilities? Or is the layout tricky for those navigating with a screen reader? Automated tools struggle with these questions because they can’t judge user-friendliness the same way a person can.

False Flags

It’s common to get false positives (where the tool flags a problem that might not actually be a problem) or false negatives (where the tool fails to spot a genuine issue). This can lead you down the wrong path or lull you into thinking your site is perfectly fine when it’s not.

Limited Scenarios

Accessibility is more than code. What happens when someone uses only a keyboard to navigate your site? Or how does your site work for someone who relies on voice commands or a screen reader? Automated scans can’t replicate all these scenarios.

Overconfidence and the Need for Manual Testing

Automated tools can create a false sense of security. Just because a scanner says you’re 90% accessible doesn’t mean your site is truly welcoming for all. This is where manual testing comes in.

Beyond the Scan: Why Manual Testing Still Rules

Manual testing is where you or a tester interacts with your site in a more human way. Yes, it’s more time-intensive, but it’s also where you’ll uncover issues an automated tool can’t detect.

Keyboard-Only Navigation

One of the most fundamental manual tests is trying to tab through your site without using a mouse. If you can’t reach a menu item or submit a form using only the keyboard, that’s a major red flag.

Screen Reader Assessments

Automated scans might say you have alt text in all the right places, but only a real screen reader test will tell you if that text makes sense in context. Does it describe important images properly? Does the reading order make sense, or does it jump around the page?

Real Users, Real Feedback

Inviting people with various disabilities to use your site can reveal issues you never even knew existed. Maybe certain wording is confusing, or a CAPTCHA system is impossible to complete using assistive technology. Nothing beats firsthand feedback.

Manual testing fills the gaps that scanners leave behind, ensuring your site isn’t just “passing a test” but actually creating a positive experience. While it can require more resources (time and possibly hiring outside help), the results are worth it.

Keeping Accessibility an Ongoing Priority

Accessibility isn’t something you do once and forget about. Think of your website as a living, breathing entity: you add content, tweak layouts, and launch new features over time. Each change could introduce fresh accessibility challenges.

So, how exactly do automated scans fit into a more complete approach to accessibility?

Putting It All Together: A Holistic Accessibility Game Plan
1. Start with an Automated Scan – Run a scan and fix low-hanging fruit, such as missing alt text and color contrast problems.
2. Add Manual Checks – Navigate your site using only a keyboard and a screen reader. Identify areas that feel confusing or broken.
3. Get Professional Input – If your site is critical to your business, hire an accessibility specialist for a thorough audit.
4. Keep It Going – Schedule periodic scans, manual audits, and staff training. Accessibility should be part of your workflow.
5. Stay Informed – Follow updates to WCAG and relevant U.S. laws, and continue learning from accessibility experts.
The Best of Both Worlds: Automated and Manual Testing

Achieving true web accessibility requires more than just running a quick scan—it demands a balanced approach that combines the speed of automation with the insight of manual testing. Automated tools can help identify glaring issues, but only real human interaction can ensure a seamless experience for all users. By integrating both strategies, you’re not just checking a compliance box—you’re creating a more inclusive, user-friendly web presence that benefits everyone.

Start your journey toward full web accessibility today—reach out to 216digital using the form below! Our team of accessibility experts is ready to assess your site and provide tailored solutions to ensure that all visitors can easily access your content. Don’t let accessibility remain an afterthought—take the first step towards a more inclusive online presence now.
Greg McNeil

February 13, 2025

Testing & Remediation

Accessibility Audit, Accessibility testing, automated testing, manual audit, Manual Testing, Web Accessibility
The Accessibility Lawsuit Trend No One’s Talking About

In 2025, the world of digital accessibility is more complicated and urgent than ever. Lawsuits over website accessibility are on the rise, and they are changing in ways many businesses haven’t prepared for. In the past, companies would run automated scans and assume they were safe. But a troubling new trend has emerged. Plaintiffs are now basing their legal cases on problems that only show up through manual audits. If your website is relying on automated checks alone, you could be at serious legal risk. This article explains why this shift is happening, how automated scans fall short, and what you can do right now to stay ahead.

Why Automated Scans Are No Longer Enough

Over the years, many accessibility lawsuits pointed to errors found by automated tools. These tools check for missing alt text on images, low color contrast, and other basic issues. But today, plaintiffs’ lawyers and accessibility consultants are using manual audits to find deeper barriers. They test how a site really works for someone with a disability. They check if a keyboard-only user can reach all parts of a form, or if a screen reader can make sense of the menu. These tests go beyond surface-level coding problems.

Now, many businesses find themselves sued even though they passed automated scans. Plaintiffs’ experts show detailed reports from manual audits to prove real-life barriers. Lawyers and judges are giving more weight to these reports, which show that a site may look fine to the naked eye but still fail to support people with disabilities. If businesses don’t adjust, they could face serious legal costs and brand damage.

The Problem with Automated Scans

Automated scans still have their place. They’re great for catching low-hanging fruit like missing alt attributes or basic color contrast issues. However, they’re just one piece of the accessibility puzzle. Here are a few examples:

Contextual Understanding

Tools can’t interpret how a page flows from one element to another or whether a user’s journey makes sense. For instance, an automated tool might confirm that a button has a label. But it won’t confirm if that label makes sense in context—for example, “Click Here” might be flagged as accessible by an automated tool but provides zero context to screen readers.

Dynamic Interactive Elements

If your site has pop-ups, carousels, or complex menus, automated scans might not catch when these elements create focus issues. A user relying on keyboard navigation might get stuck or lose track of where they are on the page.

Human Navigation Patterns

Real users might try multiple paths to accomplish tasks, like making a purchase or filling out a form. Automated tools generally test code in a linear fashion, missing real-world usage patterns.

Advanced ARIA Techniques

ARIA can help screen readers identify custom elements (like drop-downs, tabs, or modals). However, it must be implemented correctly. An automated tool might only check if ARIA attributes exist, not if they are used correctly.

Recent Case Examples Where Automated Scans Failed

Several businesses have learned this lesson the hard way. Although you might read about them in publications like The Wall Street Journal, three notable examples include:

Kramer Knives

A small business specializing in handcrafted knives faced a lawsuit from a visually impaired plaintiff. Kramer Knives believed they were compliant because an automated scan showed few errors. However, manual testing uncovered keyboard navigation issues and unclear labels, resulting in legal action.

Electric Bike Technologies

This e-commerce business was sued for alleged inaccessibility after a plaintiff discovered barriers during manual testing. The automated scans the company had relied on were insufficient, as they didn’t catch certain interactive elements that weren’t accessible to screen readers.

Extract Labs

This CBD and cannabinoid products seller thought their high automated score meant they were safe. However, manual audits found significant barriers—like form fields that weren’t properly labeled and pop-up modals that trapped keyboard focus—leading to a lawsuit.

In each instance, the businesses thought they were protected. But what they missed—those deeper, functional issues—still made their sites inaccessible to real users and vulnerable in court.

How This Shift Could Activate a Wave of Accessibility Lawsuits in 2025

More Lawsuits, More Targets

Since manual audits reveal issues that automated scans ignore, it’s easier than ever for plaintiffs to build a strong legal case. E-commerce stores, healthcare websites, and travel booking sites are especially vulnerable. Their complex forms and interactive features may pass an automated check but fail real-world testing.

The Rise of Copycat Lawsuits

Accessibility lawsuits now follow a pattern. According to recent statistics, 41% of federal court lawsuits in 2024 targeted businesses that had already been sued before. Plaintiffs’ law firms reuse winning strategies again and again. Once they find a successful argument, they apply it to many businesses across different industries. Small businesses without in-house accessibility knowledge become prime targets. They often settle quickly to avoid higher legal costs, which makes them even more attractive to plaintiffs. These copycat lawsuits can destroy a business’s reputation and finances.

What Website Owners Need to Do Now

Going Beyond Automated Scans

It’s clear that if your only strategy is running an automated scan, you’re leaving yourself wide open. You need a multi-layered approach that combines automated scanning with manual audits for a complete look at your site. Manual audits test your website in the same way real users do.

Testers try to navigate using only a keyboard, or with a screen reader, or with special settings to assist low vision. This approach catches hidden barriers that an automated check will never see. If possible, individuals with disabilities should be involved in testing. Their feedback is invaluable because it reflects real-world challenges that neither a tool nor a developer might anticipate.

Creating a Proactive Accessibility Strategy

If you want to stay off a plaintiff’s radar, or at least have a strong defense if sued, take these steps:

Conduct a Full Accessibility Audit

Start with an initial assessment that combines automated tools and manual audits. Identify all major barriers to accessibility on your site.

Remediate the Issues

Fix the problems uncovered by your audit. This might involve updating code, redesigning certain elements for better contrast and clarity, or rethinking how your site’s navigation is structured.

Implement Ongoing Monitoring

Accessibility isn’t a “set it and forget it” project. Every time you add a new product, page, or feature, you could introduce new barriers. Schedule periodic reviews, both automated and manual or sign up for monitoring services like Accessibility Radar (a11y.Radar).

Train Your Team

Developers, designers, content writers—everyone on your team should know the basics of accessibility. Make sure they understand how to write alt text, use headings properly, and maintain keyboard-friendly navigation.

How 216digital Can Help

If you’re feeling overwhelmed, you’re not alone. It’s a big task to ensure your website is fully accessible, especially if you’re new to web accessibility. At 216digital, we focus on making accessibility practical and achievable for businesses of all sizes.

Our experts will test your website the way actual users do. We don’t just point out problems. We help you fix them for the long run. Whether your site needs design tweaks, code adjustments, or content changes, we’ll guide you every step of the way.

We don’t stop there. Accessibility standards change, and we stay on top of new guidelines. We provide ongoing support to make sure your site remains accessible. By combining automated scans with manual audits, our team delivers a full view of your accessibility status.

Take Action Today

Many business owners don’t think about website accessibility until they get served a lawsuit. By then, it may be too late. The better plan is to act now. Start with a thorough assessment and fix any barriers before a plaintiff turns them into a legal case. If you wait, you could face serious penalties, legal fees, and harm to your brand.

To stay protected, schedule a free accessibility risk assessment with 216digital. Our team will show you how manual audits can spot hidden barriers, and we’ll guide you on how to fix them. Avoid the growing wave of lawsuits by making your site accessible today. After all, equal access is not just a legal issue—it’s the right thing to do for your customers and your business.

Remember: automated scans are no longer enough. By embracing manual audits, you can protect your business, serve your customers better, and stay on the right side of the law. Don’t wait until you become the next lawsuit headline. Act now and secure your place as a leader in digital accessibility.

Greg McNeil

February 5, 2025

Legal Compliance

2025, Accessibility, Accessibility Audit, Accessibility testing, ADA Lawsuit, manual audit, Manual Testing, Web Accessibility
Choosing the Right Accessibility Audit for Your Goals
Ensuring your website is accessible to everyone, regardless of their abilities, is a legal obligation and a crucial aspect of good business practice. Digital accessibility is about creating an inclusive web experience, allowing everyone to navigate, interact, and engage with your online content without barriers. A vital component of this effort is accessibility testing, which identifies and helps rectify issues that could prevent users with disabilities from accessing your site. But with so many accessibility audits available, how do you choose the right one for your goals?

This post will explore different accessibility testing methods, their benefits, and how you can select the best approach to meet your needs.

What is Accessibility Testing?

Accessibility testing evaluates a website or digital product to ensure people of all abilities can use it. This includes users with visual, auditory, physical, speech, cognitive, or neurological disabilities. The goal is to identify any barriers that might prevent these users from fully interacting with your site, whether that’s difficulty reading text, navigating menus, or accessing multimedia content.

Accessibility testing typically involves checking against established guidelines, such as the Web Content Accessibility Guidelines (WCAG), which provide a comprehensive framework for creating accessible web content. Testing can be done using various methods, from automated tools to manual assessments by accessibility experts.

Why Your Website Needs Accessibility Testing

Web accessibility is not just a matter of ethics—it’s a legal requirement in many regions, including the United States, where the Americans with Disabilities Act (ADA) mandates that websites be accessible to people with disabilities. Failing to meet these requirements can result in costly lawsuits, damage to your brand’s reputation, and loss of potential customers.

Beyond legal compliance, accessibility testing is essential for ensuring a positive user experience for all visitors. An accessible website can increase your audience reach, improve customer satisfaction, and boost your SEO efforts, as search engines like Google favor easy-to-navigate and understand sites.

Overview of Different Accessibility Testing Methods

Several methods of accessibility testing exist, each with strengths and limitations. Understanding these methods will help you choose the right approach for your goals.

Automated Testing

Automated accessibility testing uses software tools to scan your website for accessibility issues. These tools can quickly identify common problems, such as missing alt text, improper heading structures, or color contrast issues.

Pros: Automated testing is fast, cost-effective, and can cover large portions of your site in a short amount of time. It’s an excellent first step in identifying apparent issues.

Cons: While automated tools can catch many issues, they only cover 30-40% of accessibility guidelines. They can miss more subtle or complex problems that require human judgment.

Manual Testing

Manual testing involves human testers evaluating your website’s accessibility by simulating users’ experience with disabilities. This might include using screen readers, navigating with a keyboard, or testing for cognitive load.

Pros: Manual testing is thorough and can identify issues that automated tools miss, such as keyboard navigation problems, improper use of ARIA (Accessible Rich Internet Applications), or issues with interactive elements like forms and buttons.

Cons: Manual testing is time-consuming and more expensive than automated testing. Expertise and experience are required to assess a site’s accessibility accurately.

Hybrid Testing

Hybrid testing combines automated and manual approaches to determine your site’s accessibility comprehensively. Automated tools are used to quickly identify issues, while manual testing addresses more complex problems.

Pros: Hybrid testing offers the best of both worlds—speed and thoroughness. It ensures that no stone is left unturned in your accessibility audit.

Cons: While more comprehensive, hybrid testing can be more costly and time-consuming than automated tools alone.

Choosing the Right Accessibility Audit for Your Goals

When selecting an accessibility audit, consider your specific goals, resources, and the complexity of your website. Here are a few scenarios to help guide your decision:
- Initial Compliance Check: If you’re new to accessibility and looking for a quick overview of your site’s compliance with basic guidelines, an automated audit might be a good starting point. This can help you identify low-hanging fruit that can be quickly addressed.
- Comprehensive Accessibility Review: For businesses that need a thorough assessment of their website’s accessibility, a hybrid audit combining both automated and manual testing is ideal. This approach will provide a complete picture of your site’s strengths and weaknesses.
- Ongoing Monitoring and Maintenance: If your goal is to maintain accessibility over time and avoid compliance issues, consider an ongoing monitoring service that regularly checks your site for new issues as content and technology change.
Overview of 216digital’s Accessibility Services

At 216digital, we understand that navigating the complexities of digital accessibility can be overwhelming. That’s why we offer a structured approach to accessibility audits through our Phase 1 Risk Mitigation and Phase 2 Real World Accessibility services.

Phase 1: Risk Mitigation Service

This initial phase focuses on identifying and addressing high-risk accessibility issues that could expose your business to legal action. Using automated tools and expert manual review, we prioritize the most critical issues that need immediate attention.

Phase 2: Real-World Accessibility Service

In Phase 2, we dive deeper into the user experience, focusing on real-world scenarios and how users interact with your site. This phase includes extensive manual testing to uncover complex issues and provides actionable recommendations for improving your site’s accessibility.

How Combining Automated and Manual Testing Enhances Accessibility

A combined approach to accessibility testing offers a more robust and reliable audit process. Automated tools quickly handle large-scale issues, but manual testing ensures your site meets the nuanced needs of all users. By integrating both methods, you can create a more accessible and user-friendly website, reducing the risk of missed issues and ensuring a more inclusive experience.

216digital’s a11y.Radar Service for Ongoing Monitoring

Maintaining accessibility is an ongoing process. 216digital’s a11y. Radar service continuously monitors your website, automatically scanning for new accessibility issues as they arise. This service helps ensure that your site complies with accessibility guidelines over time, catching potential problems before they become costly liabilities.

a11y.Radars Key Features include:
- Dynamic Dashboard Display
- Compliance Scans
- Detailed Issues Reports
- Issues Over Time
- Manual Testing Reports
- Email Alerts
- Current Web Compliance Status
How a11y.Radar Helps Prevent Frivolous ADA Lawsuits and Maintains Accessibility Compliance

One of the biggest concerns for businesses today is the threat of frivolous ADA lawsuits. These lawsuits can be costly and time-consuming, even if the claims are unfounded. 216digital’s a11y. Radar service acts as a safeguard, continuously monitoring your site for compliance and helping you address issues before they lead to legal action. By keeping your site up-to-date with accessibility standards, a11y.Radar protects you from lawsuits and ensures a better user experience for all visitors.

Conclusion

Choosing the proper accessibility audit is crucial for ensuring your website meets the needs of all users while staying compliant with legal requirements. Whether you’re just starting with accessibility or looking for a comprehensive review, understanding the different testing methods and services available will help you make an informed decision.

At 216digital, we can help develop a strategy to integrate WCAG 2.1 compliance into your development roadmap on your terms. To learn more about how our experts can help you confidently create and maintain an accessible website that meets both your business goals and the needs of your users, schedule a complementary ADA Strategy Briefing today.
Greg McNeil

August 8, 2024

Testing & Remediation

Accessibility Audit, Accessibility testing, digital accessibility, Web Accessibility, Web Accessibility Solution, Website Accessibility Tools

What Is a VPAT?

Who Needs a VPAT?

Which VPAT Version Should You Use?

Core Elements of a VPAT

Tips for Filling Out a VPAT

Why VPATs Matter Beyond Legal Compliance

Closing Thoughts

Why Accessibility Testing Belongs in the Sprint

Shift Accessibility Left: Early Planning Wins

1. Include Accessibility in User Stories

2. Define Acceptance Criteria

Build Accessibility into Design

3. Collaborate with Designers

4. Run Design Reviews

Develop With Accessibility in Mind

5. Use Accessible Components

6. Lint for Accessibility

7. Write Semantic HTML

Make Testing Part of the Flow

8. Automated Accessibility Tests

9. Manual Testing in Sprint

Retrospectives: Keep Improving

Tips for Getting Started (or Leveling Up)

Don’t Bolt It On—Build It In

Need Help Fitting Accessibility Into Your Workflow?

Start the Conversation About Agency Accessibility Solutions

Revisit It During Design Reviews

Build Accessibility into Development (Not After)

Post-Launch Is Just the Beginning

When Legal Risk Enters the Chat

Make Agency Accessibility Solutions the Default

Ready to Make Accessibility Part of Your Process?

Why Web Accessibility Audits Are Critical

When Should You Audit Your Website for Accessibility?

1. After a Website Redesign or Major Update

2. Before Launching New Features or Products

3. Annually (at Minimum)

4. After User Feedback or Complaints

5. When Laws or Guidelines Change

Why Ongoing Monitoring Matters

The Cost of Skipping Regular Web Accessibility Audits

How 216digital Can Help You Stay Compliant

Keep Progress on Track with Confidence

Why Accessibility Matters

Reaching Every Visitor

Reducing Legal Risk

What Is an Accessibility Audit?

The Accessibility Audit Process: Step-by-Step

Initial Consultation & Scope Definition

Automated Testing

Manual Evaluation

User Testing with Assistive Technology

Documentation of Findings

Prioritization of Issues

Remediation Recommendations

What Happens After the Audit?

Implementing Fixes

Team Training

Ongoing Monitoring

Your Website’s Future Just Got Brighter

What Are Automated Accessibility Scans?

What Do Automated Scans Detect?

How Automated Scans Can Help You

Speed and Efficiency

Spotting the “No-Brainers”

Routine Monitoring

Raising Awareness

Ease of Use

The Real-World Limitations of Automated Scans

Lack of Context

Missing Nuances

False Flags

Limited Scenarios

Overconfidence and the Need for Manual Testing

Beyond the Scan: Why Manual Testing Still Rules

Keyboard-Only Navigation

Screen Reader Assessments

Real Users, Real Feedback

Keeping Accessibility an Ongoing Priority

Putting It All Together: A Holistic Accessibility Game Plan