How remediation works
We start from an audit or a scan report and work through the findings in priority order. Some fixes are quick and affect many pages at once, such as adding a language attribute to a template or giving the search button a name. Others take more thought, such as a menu that traps keyboard focus or a booking form that a screen reader cannot complete.
- Triage. We group issues by how many people they block and how many pages they affect.
- Fix at the source. We change templates, themes, components, and content, not just one page at a time.
- Retest. Every fix is checked again by hand with a keyboard and a screen reader, not only by a scanner.
- Document. You get a record of what changed, what is left, and what needs a decision.
Fixes we commonly make
- Meaningful alternative text for images, and empty alternative text for purely decorative ones
- Labels, instructions, and error messages on forms
- Clear link and button names, not repeated phrases such as "click here"
- Logical heading structure and page landmarks that help people move around
- Keyboard access to menus, sliders, tabs, and pop ups, with visible focus
- Text and background colors with enough contrast
- Captions and transcripts for video and audio
- Accessible versions of key PDFs, forms, and agendas
- Correct, minimal use of ARIA attributes
Platforms we work with
Most small business and local government sites run on a content management system such as WordPress, Wix, Squarespace, or Weebly, or on a site builder sold to a specific industry. Each has limits. Some let us edit templates and code. Others limit what a site owner can change. We tell you up front what can be fixed on your current platform and what cannot. If the platform itself is the obstacle, we say so and explain your options, which may include a redesign. We do not recommend a rebuild when fixes will do.
Third party tools and widgets
Online payment forms, scheduling tools, chat widgets, map embeds, and document viewers often come from other companies. We test them and, where we can, configure them for accessibility. Where we cannot, we help you ask the vendor to fix it, find an alternative, or offer another way for people to complete the same task.
What remediation cannot promise
Even a carefully remediated site needs upkeep. New pages, new plugins, and new documents can add new barriers. We cannot promise legal protection or a perfect result. We can promise honest work, fixes made in the real code, and a clear record. For upkeep, see ongoing accessibility maintenance.
General information, not legal advice. Automated testing cannot establish full ADA compliance or guarantee protection from lawsuits. It finds some kinds of barriers quickly. A person still has to test the rest. Ask a qualified attorney how the law applies to you.
Frequently asked questions
Do I need a new website to be accessible?
Often not. If your site is on a platform that lets us fix templates and content, repair is usually the better first step. We only recommend a redesign when repair would not make sense.
Can an accessibility plugin do this for me?
A plugin can help with a few things, but it cannot repair every problem in a site's underlying structure. Real remediation changes the site itself.
How do we know the fixes worked?
We retest with automated tools, a keyboard, and a screen reader, and we give you the results.