Using this site
Last updated July 31, 2026
What we are aiming for
People come to this site because a City inspector wrote up their building. That is not an audience we get to make assumptions about. Plenty of the owners we work for are elderly, many are managing a property from a distance, and some use a screen reader or a keyboard rather than a mouse. A site they cannot use is a site that fails at its one job.
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We are telling you what we aim for and what we have actually done, which are two different things.
An honest statement of where we are
What we have built in
- Real text, not pictures of text. Every heading, price and service name is selectable, searchable and readable by a screen reader.
- Semantic structure: one H1 per page, headings in order, real lists, real buttons and real links, so a screen reader can navigate by landmark and heading.
- Full keyboard operation. Every link, button, form field and the estimate flow can be reached and used with Tab and Enter, and focus is visible.
- Form labels attached to their fields, so tapping a label focuses the input and a screen reader announces what it is asking for.
- Colour contrast: body text and the navy-on-white and white-on-navy combinations used throughout are chosen to clear the 4.5:1 ratio for normal text.
- Colour is never the only signal. Anything marked by colour is also marked by text, a label or an icon.
- Text resizes. The layout reflows to 200% zoom without content being cut off or requiring sideways scrolling.
- Decorative images are hidden from screen readers rather than announced as meaningless filenames.
What we know is not right yet
Being specific here is the point. These are the known gaps:
- Before-and-after sliders. The gallery uses a drag handle to wipe between the condition we found and the finished work. Dragging is a poor experience without a mouse. Both photographs exist and are described, but the comparison itself is harder to use by keyboard than it should be.
- Photograph descriptions. Our job photographs carry short alt text naming the trade and the building type. It is accurate but thin. Somebody who cannot see the image gets less from the gallery than somebody who can, and that gap is real.
- The address lookup. Results appear below the field after you submit. The change is announced, but the flow was designed visually first and is being reviewed.
- No formal audit. Everything above is our own testing. We have not paid for an independent review.
These are being worked on. We would rather list them than pretend they are not there.
Tell us about a barrier
If any part of this site stopped you doing what you came to do, we want to know, and we will fix it. You do not need to know the technical term for the problem. “I could not get the form to work with my screen reader” is a perfectly good report.
Call (224) 425-6059 and tell us what page you were on, what you were trying to do, and what you use to browse. A person answers Monday to Saturday. If it is easier to have somebody report it on your behalf, that is fine.
You never have to use the website
The phone is a full alternative, not a fallback
If it is easier for a family member, a building manager or a caseworker to deal with us on your behalf, that is completely normal here and we will work with whoever you nominate.
How to reach us
Chicago Code Pros
8131 N Ozanam Ave, Niles, IL 60714
(224) 425-6059
info@chicagocodepros.com
A person answers Monday to Saturday, 7am to 6pm. Requests about your information can be made on the phone; you do not need to put anything in writing.

