"The government tender requires accessibility AA level, our site fails, and we deliver in three weeks." That is how a mid-sized firm bidding on public contracts put it. Their site looks great, but screen readers cannot read the buttons, the keyboard cannot reach the menu, and contrast fails across the board. Accessibility is not something you bolt on with a plugin the day before launch — it touches design, frontend structure, and content, and done right it benefits not only users with disabilities but your SEO and everyone squinting at a phone in the sun.
Where It Fits vs Where It Does Not
Good reasons to do accessibility now:
- Bidding on government, education, or healthcare contracts that explicitly require WCAG AA or a national standard.
- Public-facing brand sites and ecommerce wanting broader reach and better SEO.
- Mid-redesign — build accessibility into the design rather than patching later.
Where to defer:
- Internal, login-only back-office tools with no legal requirement.
- One-off campaign pages taken down in days (poor ROI).
- A site about to be rebuilt — do not spend heavily patching the old one.
Alternatives Matrix
| Option | Pros | Cons | Cost tier |
|---|---|---|---|
| One-click overlay widget | Installs fast, live same day | Symptom only, widely criticized as not truly compliant, can invite complaints | Low (monthly) |
| Self-taught DIY fixes | Cheap, team learns know-how | Slow, easy to miss, no professional audit | Low (labor hours) |
| Professional remediation (design + frontend + audit) | Truly compliant, lifts SEO and UX together | Needs upfront effort and timeline | Mid-high (project) |
Note: overlay widgets are highly contested internationally, with lawsuits in several regions where widgets failed to deliver real compliance — do not treat them as a liability shield.
Full Process (Tools and Deliverables)
- Phase 1 Audit (3-5 days): automated scans with axe DevTools/Lighthouse plus manual keyboard and screen-reader (NVDA/VoiceOver) testing; deliver an issue list with severity grading.
- Phase 2 Design fixes (1 week): against WCAG 2.2, fix contrast, focus styles, and touch-target size; deliver updated Figma and color specs.
- Phase 3 Frontend build (2-3 weeks): add semantic tags, ARIA, keyboard operation, form labels and error hints, image alt text; deliver a testable staging build.
- Phase 4 Content and docs (3-5 days): organize alt text and video captions; deliver an accessibility statement page and maintenance guide.
- Phase 5 Re-test and sign-off (2-3 days): re-run automated and manual tests; deliver a compliance report and maintenance checklist.
Real Cost Breakdown
- Audit fee: small sites roughly NT$15,000-40,000.
- Remediation hours: by page count and severity, commonly NT$60,000-200,000.
- Hidden costs: video captioning (per minute), writing alt text, the accessibility statement page, and re-test fees on every future redesign.
- Maintenance cost: without a gatekeeper, new content erodes compliance over time — the most-overlooked long-term cost.
Reality vs What Clients Imagine
- Clients imagine "a plugin makes it compliant"; in reality overlays often fail a manual audit and can add legal risk.
- Clients imagine "accessibility is for a few people"; in reality contrast, keyboard operation, and clean structure lift everyone's experience and SEO.
- Clients imagine "do it once and it is permanent"; in reality every new content addition can break compliance without a gatekeeping process.
Common Traps and How to Avoid Them
- Treating an automated scan as compliance: automated tools catch only 30-40% of issues — add manual keyboard and screen-reader testing.
- Padding with an overlay widget: use real native fixes; do not outsource legal risk to a widget.
- Checking contrast only on the primary color: also check hover, disabled, and error states.
- Forms without labels and error hints: every field needs a readable label and a clear error message.
- Alt text like "image 1": describe the content and function; mark decorative images as empty.
Success Metrics + 90-Day Roadmap
- Day 30: zero critical automated-scan errors; key flows (home to contact to checkout) fully keyboard-operable.
- Day 60: manual audit re-test done, accessibility statement published, team has a "new-content checklist."
- Day 90: track organic-search impressions and bounce-rate change; fold accessibility checks into every release.
Decision Checklist
- ☐ Does my site have a contract or legal accessibility requirement?
- ☐ Can I complete the main flows with a keyboard?
- ☐ Can a screen reader read all buttons and forms?
- ☐ Is main text/background contrast AA (4.5:1 for normal text)?
- ☐ Do all non-decorative images have alt text?
- ☐ Do videos have captions?
- ☐ Do form fields have labels and error hints?
- ☐ Are focus styles visible?
- ☐ Do I have an accessibility statement page?
- ☐ Does someone gatekeep compliance for new content?
- ☐ Did I redesign in the last 3 months without re-testing?
- ☐ Do I understand the legal risk of overlay widgets?
FAQ
Can I just use an accessibility overlay widget?
Not recommended as a compliance solution. It fails a rigorous manual audit, and there are lawsuits internationally where widgets did not deliver real compliance. Native remediation is the real fix.
How long and how much does accessibility take?
A small site takes about 4-6 weeks from audit to re-test, commonly NT$75,000-240,000, depending on page count and current severity. Doing it during a redesign is most cost-effective.
Does accessibility really help SEO?
Yes. Semantic tags, alt text, and clean structure are how both search engines and screen readers parse content — the overlap is large.
Which WCAG level should I target?
Most contracts and practice target AA. Some AAA criteria are too strict for a whole site and are usually reserved for specific content.
Call to Action
ScriptWalker offers "website accessibility audit and remediation," audits from NT$15,000, and a free quick scan to show where you stand. Contact us:
- Email: [email protected]
- Phone: 0916-224-047
- LINE: @ufv9089p