kass logo wht letters
Contact US
Client Portal

Web Accessibility Statement

Last updated: August 20, 2026

This web accessibility statement explains how Kass Construction & Development, Inc. builds a website that every visitor can use, including people who rely on screen readers, screen magnification, voice control, or keyboard-only navigation. Accessibility is treated as part of how the site is built and maintained, not as an afterthought.

Which standard do we work to?

The Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These are the internationally recognized criteria used to judge whether digital content is usable by people with disabilities, and they are the benchmark referenced by most accessibility regulation in the United States.

The guidelines are published by the World Wide Web Consortium Web Accessibility Initiative, federal guidance for businesses is summarized by the US Department of Justice, and the technical standards for federal accessibility are maintained by the US Access Board.

What is our current conformance status?

Partially conformant with WCAG 2.1 Level AA. This web accessibility statement reports that status honestly rather than claiming more. Partially conformant means most of the site meets the standard and some content does not yet fully conform. We publish this honestly rather than claiming full conformance, because accessibility on a site with regularly published articles is continuous work rather than a finished state.

What accessibility features are already in place?

The measures below are active on this website today. Each one is either built into the templates or applied to every article as it is published.

  • Skip to content link. Keyboard and screen reader users can bypass the navigation and jump straight to the main content of any page.
  • Descriptive alternative text on images. Every image in our articles carries alt text describing what it shows, so the content still makes sense when images cannot be seen.
  • Semantic heading structure. Pages use a single H1 followed by a logical H2 and H3 outline, so assistive technology can navigate a page by its sections.
  • Keyboard navigation. Menus, links, buttons, and form fields can be reached and operated without a mouse.
  • An accessibility toolbar. A widget on every page lets visitors adjust text size, contrast, link highlighting, and related display preferences.
  • Declared page language. Each page declares its language so screen readers pronounce content correctly, and a translation tool is available for visitors who prefer another language.
  • Continuous automated scanning. Pages and articles are scanned as they are published, and issues are logged and remediated rather than left in place.
  • Color contrast and readability testing. Text and background combinations are checked against contrast requirements, and article readability is tested as part of publication.

Where are we still improving?

Three areas are known to fall short and are being worked on. Naming them is more useful to you than a blanket claim of compliance.

  • Third-party embedded content. Maps, video players, and similar embedded services are controlled by their providers and we cannot alter their internal markup. Where an embed is the only source of information, we provide the same information as text on the page.
  • Older documents and downloads. Some documents published before our current standards were adopted may not be fully tagged for screen readers. We are reviewing and replacing them, and we will supply an accessible version of any document on request.
  • Complex tables and diagrams. Our guides use comparison tables to summarize technical material. We are reviewing these so that each one reads clearly in a linear order for screen reader users.

How do we test the website?

Automated scanning on every page, plus manual checks. Automated tools catch most issues, but they cannot judge whether alt text is meaningful or whether a page makes sense when read aloud, so both are used.

  • Automated accessibility scanning of every page and article at publication
  • Keyboard-only navigation testing of menus, forms, and interactive elements
  • Color contrast analysis of text against its background
  • Readability testing of article content
  • Review of heading order and alternative text as part of publishing

Guidance on how people actually use assistive technology, including survey data on screen reader use, is published by WebAIM.

What should you do if something is not accessible?

Tell us, and we will get you the information another way while we fix it. If a page, document, or feature on this website prevents you from finding what you need, contact us using any of the methods below and describe the page and the difficulty. We will respond, work with you to provide the content or service through an alternative method, and correct the underlying problem.

Please include the address of the page, a short description of the problem, and the assistive technology or browser you were using. That detail lets us reproduce the issue and fix it properly rather than guessing.

Who does this web accessibility statement cover?

Kass Construction & Development, Inc., a state-licensed (CGC1529472) boutique luxury builder in East Fort Lauderdale, serving Broward, Palm Beach, and Miami-Dade counties. This web accessibility statement applies to kassconstruction.com and all of its pages and articles, including the guides in our Insights library. You may also want our Privacy Policy, our Terms and Conditions, or the contact page.

Scroll to Top