Inclusion
Vision, motor, cognitive users…
What is web accessibility? Including every user
Web accessibility is the set of practices that let people with disabilities—and everyone else—use sites and apps: perception, keyboard navigation, screen readers, contrast, understandable forms. W3C's WCAG structures criteria (A/AA/AAA). Beyond ethics and law, it is product quality and technical SEO.
In one sentence
Web accessibility makes interfaces usable by the widest audience, including assistive tech.
Key points
- WCAG: perceivable, operable, understandable, robust.
- Keyboard, focus, sparingly used ARIA, semantic HTML.
- Contrast and text alternatives for media.
- Test with tools and real users.
Term at a glance
- Web accessibility
- A11y · WCAG · Digital accessibility
- English term
- Web accessibility
- Domain
- UX & performance
- Category
- Accessibility
- Level
- Beginner to intermediate
What does “web accessibility” mean exactly?
Not a magic plugin: semantic HTML, labels, focus states, and tested flows.
Screen readers rely on structure (headings, landmarks, accessible names).
For a Quebec SME, accessibility widens the market and anticipates growing public requirements.
How do you improve accessibility?
- 01
Audit
Automated tools + manual keyboard/screen-reader review.
- 02
Fix foundations
Semantics, contrast, labels, form errors.
- 03
Bake into the design system
Accessible components by default.
- 04
Sustain
Criteria in Definition of Done and CI.
Concrete web accessibility example
A Montreal medical booking portal adds labels, visible focus, and field-linked error messages. Screen-reader tests pass; mobile abandonment also drops—clarity helps everyone.
What is web accessibility for?
Compliance
Public procurement and internal policies.
UX quality
Clarity for all, including mobile.
SEO / robustness
Healthy HTML structure.
Pros and cons of accessibility work
- Wider audience
- Better overall UX
- Lower legal risk
- More robust components
- Initial effort on legacy
- Auto-tools false greens
- Team training required
- Bad ARIA makes things worse
Accessibility vs aesthetic design alone?
| Web accessibility | Aesthetic design alone | |
|---|---|---|
| Goal | Real use by everyone | Look / brand |
| Criteria | Measurable WCAG | Subjective |
| Keyboard / AT | Required | Often forgotten |
| Outcome | Inclusion + quality | Pretty but sometimes unusable |
Why accessibility matters for a Quebec SME
Inclusion also converts. An unreadable form costs leads. Public RFPs and large buyers increasingly require WCAG AA—cheaper to integrate early.
FAQ
Which WCAG level?
AA is the usual target for public web and many companies.
Is an auto tool enough?
No—it misses focus, reading order, and context.
Only for disability?
No: age, bright sun on mobile, occupied hands…
Cost?
Cheaper baked into design than rushed before an RFP.
Related terms
Sources and references
Want a pragmatic WCAG accessibility audit on your site or portal? We can prioritize fixes.
Talk about accessibility