Why accessibility is no longer optional housekeeping
Accessibility is not a polish item. It is basic website maintenance. If people cannot read the text, move through the menu, fill out a form, or understand what a button does, the site is broken for them. That is the symptom. The cause is usually boring: weak color contrast, sloppy headings, missing labels, tiny tap targets, or a keyboard trap pretending to be design.
For small businesses, artists, and charities, accessibility affects visitors, donors, and clients who already have limited patience. It also affects search visibility and performance in the practical sense: clear pages are easier to use, easier to scan, and less likely to lose people halfway through a task. Google’s Core Web Vitals guidance makes the same point from another angle: faster, more stable pages create a better real-user experience. See Google’s Core Web Vitals guidance.
What WCAG 2.2 adds, in plain English
WCAG means Web Content Accessibility Guidelines. WCAG 2.2 is the current baseline from the W3C. It does not ask for magic. It asks for websites that people can actually use. The 2022 update adds and clarifies practical checks such as larger touch targets, better focus visibility, and fewer surprises during form use. Read the source: WCAG 2.2 and the W3C summary, What’s New in WCAG 2.2.
Two terms matter immediately:
- Accessibility: whether people with different abilities can perceive, understand, navigate, and use the site.
- Usability: how easily people complete a task once they arrive.
They overlap. A site can be “pretty” and still fail both.
A 30-minute self-check
Set a timer. Open the site on a laptop and a phone. Then inspect the basics. Not the brand poetry. The mechanics.
- Text alternatives — Every meaningful image needs alt text. If an image carries information, the alt text should say what the visitor needs to know, not what the file name says.
- Headings — Use one clear H1, then logical H2s and H3s. Headings are not decorative large text. They are the site’s skeleton.
- Contrast — Low-contrast text is not subtle. It is unreadable. Check text, buttons, and link states against their backgrounds.
- Keyboard access — Can you reach menus, links, buttons, and forms with Tab alone? If not, the site excludes keyboard users and often screen reader users too.
- Focus visible — When you tab through the page, can you see where you are? If the focus ring is hidden, the interface is guessing badly.
- Forms — Labels should be visible and specific. “Name” is fine. “Your details” is lazy. “Required” fields should be marked clearly.
- Target size — WCAG 2.2 pays more attention to touch targets. Tiny links and microscopic close buttons are not helpful on a phone.
- Link clarity — “Read more” is weak unless the surrounding context makes the destination obvious. A link should tell the reader where it goes.
If you want the standard itself, use the W3C’s Understanding WCAG 2.2 pages as the reference, not random blog summaries with confidence issues.
Common problem areas for artists and charities
Artists and charities have different workflows, but they keep running into the same failures.
| Area | Common blocker | What to fix |
|---|---|---|
| Galleries and portfolios | Images without useful alt text or captions | Describe the work, the medium, and the reason the image matters |
| Donation pages | Forms with unclear labels, broken focus order, or too many fields | Shorten the flow, label each field, and test the keyboard path |
| Event pages | Dates, times, and locations buried in decorative layouts | Put the facts near the top and keep them text-based |
| Contact pages | Forms with missing instructions or error messages that explain nothing | Say exactly what went wrong and how to correct it |
Nonprofit UX research from Nielsen Norman Group keeps circling the same point: reduce friction, especially in donation and contact flows. That is not a trendy opinion. It is a survival habit. NN/g’s nonprofit UX guidance is worth the read if your charity site keeps losing people at the last step.
How accessibility and performance work together
Accessibility and speed are not separate departments. Slow pages increase drop-offs. Messy layouts increase confusion. Tiny controls increase errors. A site that loads fast but is hard to use is still a bad site; it just wastes time more efficiently.
That is why a practical checkup looks at both content structure and performance basics. If pages are overloaded with giant images, unstable layout shifts, or popups that fight the visitor, the accessibility problem and the performance problem are probably the same problem wearing different hats.
Fix it yourself, or ask for support?
Some fixes are manageable in-house. Others are trap doors.
- Probably manageable: rewriting alt text, improving headings, adding labels, editing button text, tightening copy, and checking color contrast.
- Probably needs support: inaccessible theme behavior, broken navigation menus, form plugins with bad markup, checkout flows, embedded widgets, and anything that fails keyboard testing across the site.
If the problem lives in the theme or plugin behavior, changing text on top will not cure it. That is the web equivalent of painting over a cracked pipe.
If you need a broader service overview, see website design support and SEO services. For a direct conversation, use the contact page. For background on the site, there is also about. And if you want more practical notes, browse the blog or return to the home page.
Next-step checklist
- Run the 30-minute self-check on desktop and mobile.
- Fix the obvious blockers first: alt text, headings, labels, contrast, and tap targets.
- Test a full keyboard path through your most important pages.
- Review forms, donation steps, and event/contact pages separately.
- Use the W3C WCAG 2.2 standard as your reference, not a social-media summary of it.
- If the problem is structural, get support before it multiplies.
Accessibility is not a bonus feature. It is the difference between a website that works and a website that merely exists.