Navigation & Structure
Can people find their location and move through the website?
- Keyboard access
- Navigation and menus
- Focus order
- Headings and structure
Accessibility
Reviews, prioritized findings, and practical fixes that make your site work for people using keyboards, screen readers, captions, and magnification.
Home / Contact Us
We're here to help. Send us a message and we'll respond as soon as we can.
Your full name*
Email address*
What is this about?*
Please select a topic so we can route your message.
Message*
Briefly describe your question or request.
What accessibility means
Web accessibility means removing barriers that prevent disabled people from navigating, understanding, and using a website.
It can be built into a new site or improved on an existing one.
What CK Works reviews
Can people find their location and move through the website?
Can people understand instructions, correct errors, and complete tasks?
Can people perceive, enlarge, hear, and adapt the content?
Can people use the supporting files, portals, embeds, and third-party tools?
The exact pages, templates, documents, systems, and user journeys included are defined before each review.
How the work happens
We find meaningful barriers, prioritize what matters, and help improve the experience. Knowing what to fix first is usually more useful than knowing everything at once.
We work through the agreed pages, templates, and journeys to confirm where people meet barriers that actually stop them.
Each confirmed barrier is ranked by how many people it affects and how much it blocks them, so the fixes that matter are obvious instead of buried in a long list.
We fix what we can reach directly in the code, and write plain guidance for anything owned by a vendor, a content editor, or another team.
Accessibility slips as content and components change. We can stay involved to check new work before it ships and keep the ground you gained.
What you receive
Each review ends with practical information your team can act on.
Pages, templates, documents, and journeys reviewed.
Confirmed barriers organized by user impact.
Evidence, WCAG references, and recommended fixes.
What CK Works can address and what should be rechecked.
How these tools help
Automated checks can surface patterns quickly. Understanding whether someone can complete a real task still requires human judgment.
Find detectable, objective failures quickly, and catch regressions over time.
Focus order, meaningful alternatives, clear instructions, recoverable errors, and complete journeys still need a person.
Overlays sit on top. They do not repair the underlying website.
For public entities
The DOJ rule names WCAG 2.1 Level AA as the technical standard for covered web content and mobile applications. We help public entities find the barriers and plan the work before the date that applies to them.
Technical accessibility services, not legal advice or compliance certification.
Compliance dates
Population 50,000 or more
Population under 50,000, and special districts
What may need review
FAQ
Common questions about accessibility reviews, what gets fixed, and how scope is decided.
Scope is agreed before the work starts. A review covers a set of representative pages, templates, and important user journeys, checked with a combination of automated tools and hands-on testing. Documents, portals, and third-party systems are included when they are part of that agreed scope.
Where this connects
Web Accessibility
Send over your site and a little context about who uses it, and I'll suggest a practical starting point.