Web accessibility
Accessibility is a priority, not an afterthought
If someone can't read your text, reach your buttons, or finish your form, they can't become your customer. Lorien Web audits your site against WCAG and hands you a plain-language, prioritized list of what's in the way—and how to clear it. Audits are conducted by Phil Linley, a professional member of the International Association of Accessibility Professionals (IAAP).
Why it matters
Not a checkbox—whether people can use your site
Accessibility gets treated as a finishing touch, something to bolt on if there's time. That's backwards. It's the foundation that decides who can do business with you at all.
Someone is trying to hire you right now
A customer using a keyboard or a screen reader hits a form they can't complete, a button they can't reach, text they can't read—and they leave. You never see the sale you lost. Accessibility is whether people can actually do business with you.
The legal exposure is real and growing
Website accessibility lawsuits and demand letters land on small businesses and nonprofits every year, citing the ADA and WCAG. An honest audit tells you where you stand before a letter does.
Built in, it's cheap. Bolted on, it's expensive
Accessibility folded into how a site is built costs almost nothing. Retrofitting it after a problem—or a complaint—costs far more. The earlier you look, the less it takes to fix.
The same work lifts SEO and speed
Clean headings, real labels, semantic structure, fast pages—the things that help a screen reader are the things search engines reward. Accessibility and findability are the same craft.
What an audit covers
The places people actually get stuck
Lorien reviews your site the way the people you're losing experience it—by keyboard, by screen reader, in bright sun on a phone—against the WCAG standard.
Keyboard and focus
Every action reachable and operable without a mouse, with a focus outline you can actually follow.
Screen-reader semantics
Headings, landmarks, labels, and alt text that let assistive tech announce the page in an order that makes sense.
Color and contrast
Text and controls that stay legible for low-vision users and in bright sunlight on a phone.
Forms and errors
Labelled fields, clear error messages, and flows that don't trap or confuse the people trying to reach you.
Motion and media
Animations that respect reduced-motion preferences, and media with captions or text alternatives.
Structure and reading order
A logical document outline so the page holds together for everyone, however they read it.
What you get
A report you can act on, not file away
The point isn't a 90-page PDF nobody reads. It's a clear picture of what to fix, in what order, and why.
01
A plain-language report
No jargon dump. Each issue described in terms of who it affects and why it matters, so a non-developer can follow it.
02
Prioritized by impact
Sorted from the things blocking people today to the smaller polish—so you know what to fix first and what can wait.
03
Concrete fixes, not vague advice
Specific recommendations tied to WCAG, written so your team or Lorien can act on them directly.
04
A path forward
Fix it yourself, hand it to Lorien, or a bit of both. The audit is yours either way—no obligation to rebuild.
Common questions
Straight answers before you reach out.
Request an accessibility audit
Send a message
What are you building?
A few sentences is plenty. I’ll reply with honest thoughts — not a sales script.