Website ADA Compliance in Kansas: A Guide to Website Accessibility

Website ADA Compliance in Kansas: what this guide covers

Website ADA Compliance in Kansas means making your site usable for people with disabilities and following federal accessibility rules that apply in the state. This guide explains who is covered, the technical standard most organisations use, how to audit a site, the priority fixes, and what to do if you get a complaint.

How the law applies in Kansas

The Americans with Disabilities Act is a federal law. It applies across all states, including Kansas. Title II covers state and local government services. Title III covers public accommodation businesses. Agencies and courts often treat websites as part of those services or places of public accommodation. That is why many Kansas businesses and public entities follow established accessibility standards for their websites.

Which accessibility standard should Kansas organisations use?

Most organisations adopt the Web Content Accessibility Guidelines, commonly called WCAG. WCAG 2.1 at level AA is the widely accepted target used by courts, agencies, and digital accessibility teams. Section 508 is a separate federal standard for federal agencies and contractors. Use WCAG 2.1 AA for public-facing sites unless a contract or agency rule requires a different level.

Who in Kansas must prioritise website accessibility?

• State and local government websites (Title II).
• Businesses open to the public, such as shops, restaurants, hotels, healthcare providers, universities, and entertainment venues (Title III).
• Organisations that receive federal funding should also consider Section 504 and Section 508 requirements for digital content.

Quick audit: how to check your site now

Start with a short audit you can do in one afternoon. That will reveal the most common and visible issues.

• Run an automated scanner on key pages. Choose at least three different tools and compare results.
• Test keyboard navigation. Try tabbing through the site until every interactive item is reachable and the focus order makes sense.
• Check screen reader output. Use NVDA on Windows or VoiceOver on Mac to confirm headings, links, and form controls are announced correctly.
• Check colour contrast with a contrast checker for normal text and large text.
• Open PDFs and documents to confirm they are tagged and readable by assistive technology.

Tools commonly used for audits

• Automated rule checkers to find missing alt text, ARIA errors, and contrast failures.
• Browser dev tools and accessibility panes for manual inspection.
• Screen readers for real-world testing.
• User testing with people who have disabilities to find issues machines miss.

Common accessibility issues and how to prioritise fixes

Fix issues that block access first. Then tackle higher-effort changes.

Priority fixes (do these first)

• Text alternatives for images and non-text content. Add meaningful alt attributes to images that convey information.
• Keyboard operability. Ensure menus, forms, and dialogs can be used without a mouse.
• Form labels and error messages. Every input must have a label. Error messages must be programmatically associated with the input.
• Descriptive link text. Avoid “click here” and use links that describe the destination.
• Headings structure. Use semantic heading tags in logical order so screen reader users can scan pages.

Medium-term improvements

• Focus visible states. Make sure keyboard focus is clearly visible and follows a logical order.
• Captions and transcripts for multimedia. Add captions for video and transcripts for audio content.
• Accessible PDF and document authoring. Use proper tagging and structure when saving PDFs.
• Fix ARIA usage. Use WAI-ARIA only to enhance native semantics, not to replace them.

Long-term work

• Integrate accessibility into design and development workflows.
• Train content editors to write accessible content and manage images and documents correctly.
• Set up continuous testing and remediation cycles.

Step-by-step remediation plan for a Kansas website

1. Commission a full accessibility audit of representative pages and templates.
2. Produce a prioritized remediation list: critical, high, medium, low.
3. Assign owners for each task: developer, content editor, product manager.
4. Deploy critical fixes first, then iterate. Keep stakeholders informed with dates and scope.
5. Retest after each release. Log defects and track closure rates.
6. Publish an accessibility statement and an accessibility contact method.
7. Schedule user testing with people who use assistive technology twice a year.

Accessibility statement: what to publish

There is no official ADA certification. An accessibility statement shows intent and transparency. Include the following elements:

• A clear statement of your commitment to accessibility and the standards you use, for example WCAG 2.1 AA.
• Which parts of the site are covered and any known exclusions such as third-party content.
• How people can request assistance or report barriers, with an email or a form and a response time.
• Information on ongoing efforts and a last updated date.

Sample wording you can adapt

We are committed to making our website accessible. We follow WCAG 2.1 AA standards and review our site regularly. If you need assistance using any part of this site, please contact us with the page URL and the issue. We will respond and provide alternatives where possible.

What to do if you receive a complaint or demand letter in Kansas

Do not ignore a complaint. Take these practical steps:

• Preserve communications and the current site content. Capture screenshots and server logs if possible.
• Contact legal counsel experienced in accessibility matters. Consider an outside accessibility consultant for an independent audit.
• Perform a focused audit of the pages cited in the complaint and produce a remediation plan with timelines.
• Communicate a good-faith plan to the complainant or their representative, and execute the remediation promptly.

Hiring help in Kansas: who to look for

Search for providers that offer both technical audits and manual user testing. Ideal teams include front-end developers familiar with semantic HTML, accessibility specialists who know WCAG 2.1 AA, and people experienced with assistive technologies. Ask for examples of successful remediations and references from public sector clients if you work with government.

Ongoing governance: keep accessibility current

• Include accessibility checks in your release checklist.
• Train all content authors on accessible writing and image handling.
• Schedule periodic audits and user testing to catch regressions.

Resources to learn and follow

• WCAG 2.1 guidelines from the W3C.
• WAI-ARIA Authoring Practices for interactive controls.
• Official ADA information from the U.S. Department of Justice.
• Section 508 guidance for federal sites and contractors.

Quick checklist for Kansas website owners

• Do an automated and manual audit of key pages today.
• Add missing alt text and fix form labels as urgent tasks.
• Ensure keyboard navigation and visible focus are working.
• Publish an accessibility statement and contact method.
• Plan regular user testing and technical reviews.

If you need help building an audit scope, remediation roadmap, or an accessibility statement tailored to Kansas organisations, consider engaging an accessibility specialist who can work with your developers and legal counsel.