Blind-led accessibility consulting, clearly explained
Accessibility feedback with real user signal, clear writing, and no consultant fog.
I’m Wes. I test websites, apps, and digital workflows the way screen reader and keyboard users actually experience them, then show teams what is breaking and what to fix first. The portfolio and audio work are here too, but accessibility leads the story on purpose.
Fastest route
If you need accessibility help, start with consulting. If you want proof of how I test and write findings, go to the portfolio. If you are here for music, the audio work has its own page.
Why teams reach out
- Blind-led accessibility feedback grounded in real screen reader use and lived experience
- Clear findings and fix guidance without consultant vagueness
- Plainspoken communication that helps teams move instead of stall
Choose the lane
Most people arrive needing one clear next step, not an elaborate brand speech.
Pick the lane that fits what brought you here. The rest of the page should confirm you are in the right place fast.
Accessibility consulting
Find where the product starts losing people, then focus the team on the fixes that matter most.
Audits, testing, fix guidance, and working sessions shaped by lived blind experience and hands-on evaluation of actual user flows.
- Screen reader and keyboard testing for real user flows
- Remediation guidance your team can act on
- Support for websites, apps, SaaS, and internal tools
Accessibility portfolio
See how I test, write findings, and make sense of accessibility issues in real-world situations.
This is for hiring managers, collaborators, or anyone who wants evidence of the work instead of a vague claim to care about accessibility.
- Case-study style reviews and real findings
- Hands-on testing methods and assistive technology context
- A cleaner path for employment conversations
Audio work
Mixing, mastering, and Pro Tools help for artists who want the work to feel finished, not just exported.
The audio side has its own page, its own tone, and a cleaner path for artists and producers who do not need to sort through accessibility copy first.
- Mixing and mastering for release-ready work
- Workflow help inside real sessions
- Separate messaging for artists and producers
What makes the work different
The value is not just that issues get found. It is that the findings sound like a real user, and the next step is obvious.
Lived perspective
Blind-led feedback changes what gets noticed, how friction is described, and what the team understands about actual impact.
Writing teams can use
Findings are only useful if product, design, and engineering can act on them. Clear language is part of the service, not an afterthought.
No split identity problem
The site keeps accessibility as the lead story while still giving the audio work a legitimate home instead of hiding it or letting it muddy the pitch.
How work tends to start
A small amount of honest signal early is usually more valuable than a giant accessibility document later.
Most engagements start with a target flow, a page set, or one area the team already knows is shaky.
Start with the part that already feels risky.
You do not need a perfect brief. A broken signup flow, checkout path, dashboard pattern, or internal workflow is enough to begin.
Test what a real user would actually try to do.
The point is not collecting decorative issues. The point is seeing where a task falls apart for screen reader and keyboard users.
Leave with guidance your team can use right away.
That can mean findings, prioritization, remediation direction, or a working session to help the right fix happen faster.
How I work
Direct feedback, practical next steps, and no fake agency voice.
I care about making the work usable. That means clear findings, honest prioritization, and language people can act on without translation.
Best fit
- Teams that want blind-led accessibility input and direct remediation guidance
- Hiring managers who need more than a resume bullet list to evaluate accessibility work
- Artists and producers who want the audio lane without accessibility messaging getting in the way
- People who prefer plain language over consultant theater
Easy first step
If you already know what you need, reach out. If you are not sure yet, that is fine too.
Send a link, a rough description, or even just the problem you keep running into. I can help sort out the next step from there.