Skip to main content
CK Works

Accessibility

Web Accessibility

Reviews, prioritized findings, and practical fixes that make your site work for people using keyboards, screen readers, captions, and magnification.

  • Scope agreed before the work starts
  • Works alongside your team or vendor
  • Written against WCAG 2.1 Level AA
cityofgreenridge.gov/contact
City of Greenridge

Home / Contact Us

Contact the Planning Department

We're here to help. Send us a message and we'll respond as soon as we can.

Your full name*

Jordan Lee

Email address*

jordanlee@email
!Enter a valid email address (example@domain.com).

What is this about?*

Select a topic

Please select a topic so we can route your message.

Message*

Briefly describe your question or request.

Send message
Illustrative accessibility review

What accessibility means

Different ways of using the same website.

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.

Keyboard
Use the website without a mouse.
Screen reader
Hear the content and structure read aloud.
Zoom & reflow
Enlarge content without breaking the layout.
Captions
Access video and audio content.
Voice controls
Navigate and complete tasks by voice.

What CK Works reviews

Four areas of the website experience.

Navigation & Structure

Can people find their location and move through the website?

  • Keyboard access
  • Navigation and menus
  • Focus order
  • Headings and structure

Forms & Important Actions

Can people understand instructions, correct errors, and complete tasks?

  • Forms and labels
  • Instructions and hints
  • Error messages
  • Buttons and important journeys

Content & Presentation

Can people perceive, enlarge, hear, and adapt the content?

  • Color contrast
  • Zoom and reflow
  • Alternative text
  • Captions and motion

Documents & Connected Systems

Can people use the supporting files, portals, embeds, and third-party tools?

  • PDFs and documents
  • Downloads and files
  • Portals and embeds
  • Third-party tools

The exact pages, templates, documents, systems, and user journeys included are defined before each review.

How the work happens

From review to practical improvements.

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.

  1. Review

    We work through the agreed pages, templates, and journeys to confirm where people meet barriers that actually stop them.

  2. Prioritize

    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.

  3. Improve

    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.

  4. Maintain

    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

A clear path forward.

Each review ends with practical information your team can act on.

DefinedScope

Pages, templates, documents, and journeys reviewed.

PrioritizedFindings

Confirmed barriers organized by user impact.

PracticalGuidance

Evidence, WCAG references, and recommended fixes.

NextSteps

What CK Works can address and what should be rechecked.

How these tools help

A scan is a starting point, not a verdict.

Automated checks can surface patterns quickly. Understanding whether someone can complete a real task still requires human judgment.

Finds patterns

Automated checks

Find detectable, objective failures quickly, and catch regressions over time.

  • Labels Fields with no programmatic name
  • Contrast Text below the minimum ratio
  • Structure Heading order and landmarks
Needs context

Human judgment

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

Preparing state and local government websites for Title II requirements.

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

  • Websites
  • Mobile apps
  • Documents
  • Online forms
  • Resident portals
  • Vendor systems

FAQ

A few useful questions.

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

Make the next step easier for more people.

Send over your site and a little context about who uses it, and I'll suggest a practical starting point.