Accessibility Statement

Our commitment

Greene Insurance is committed to making this website usable by everyone, including people who browse with a screen reader, a keyboard only, voice control, a switch device, magnification, a custom stylesheet, or simply a browser zoomed to 200%.

We treat accessibility as part of building the page, not as a plugin bolted on afterwards. This site runs no accessibility overlay, no "accessibility widget", and no third-party remediation script — those tools frequently make things worse for the assistive technology users they claim to help, and they cannot fix markup that was wrong to begin with.

The standard we hold ourselves to

We target the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the W3C. It is the standard most commonly referenced in US accessibility law and the one our carriers and vendors are measured against.

Conformance status: we self-assess this site as conforming to WCAG 2.1 Level AA. That assessment is ours, based on testing described below. It has not been certified by an independent auditor, and we would rather tell you that than imply a third party signed it off.

What we have actually done

Specifics, so you can check us rather than take our word for it:

• Semantic structure and landmarks. Every page uses real HTML elements — one <h1>, headings in order, lists that are lists, tables with header cells and captions — inside labelled <header>, <nav>,<main>, and <footer> landmarks. A screen reader can jump between regions instead of reading through them.
• A skip link. The first thing focusable on every page is "Skip to content", and it becomes visible when it takes focus.
• Keyboard operability throughout. Everything interactive is reachable and operable with a keyboard, in a tab order that follows the visual order. There are no keyboard traps. The mobile menu is a native <details> disclosure rather than a scripted drawer, so it works with the keyboard by default and cannot break.
• Visible focus. A two-pixel focus ring with an offset is drawn on every focusable element, in both light and dark themes. We never remove the outline without replacing it.
• Colour contrast. Body text and interface text meet at least 4.5:1 against their background, and large text and meaningful non-text elements meet at least 3:1. The measured ratios are recorded as comments next to the colour tokens in the source, and our brass accent is restricted to borders, fills, and large text precisely because it does not clear 4.5:1 at body size. Colour is never the only way we convey information.
• Reduced motion. The site honoursprefers-reduced-motion: animations, transitions, and smooth scrolling are switched off when your system asks for that. There is nothing that auto-plays, auto-scrolls, flashes, or moves without you starting it.
• No third-party embeds. No chat widget, no video player, no embedded map, no advertising frame, no webfont from a CDN — so no inaccessible component sneaks in through someone else's script, and the page cannot shift under you while a remote asset loads. Our own fonts are served from this origin and the two used at the top of the page are preloaded; if one is still arriving, text renders in a fallback face first and may reflow once.
• Dark mode. The site follows your system colour preference, and the dark palette is contrast-checked separately rather than being an inverted afterthought.
• Text that scales. Type and spacing are set in relative units, so the site reflows without loss of content at 200% zoom and down to a 320-pixel-wide viewport. You can override our fonts and colours with your own stylesheet and the pages still work.
• Legible by default. Text faces drawn for screen reading, generous line height, and text measures capped at a comfortable line length. Nothing is justified, and nothing is set in an image.
• Meaningful link text. Links say where they go. Images that carry meaning have alt text; decorative graphics are hidden from assistive technology instead of being described pointlessly.
• Declared language. Every page declareslang="en" so screen readers use the right pronunciation rules.
• It works without JavaScript. Including the quote form. If a script fails, is blocked, or was never allowed to run, the site still functions.

Forms and the quote request

Forms are where accessibility usually falls over, so the quote request got the most attention:

• Every control has a real <label> tied to it, not a placeholder pretending to be one.
• Related controls are grouped in <fieldset> elements with a <legend>, so the structure of the form is announced, not just implied by visual spacing.
• Required fields are marked visually and programmatically, and the required-ness is announced rather than conveyed by a red asterisk alone.
• Hints and format requirements are associated with their field using aria-describedby, so they are read out with the field instead of being missed.
• autocomplete attributes are set correctly, so your browser or password manager can fill in your name, address, email, and phone for you.
• type and inputmode are correct, so phone and numeric fields bring up the right keyboard on a touch device.
• Validation errors come from the browser's native mechanism, which moves focus to the first field needing attention and announces the message.
• Touch and click targets are large enough to hit, with the label itself clickable.
• There is no time limit on completing the form, and nothing changes context when you tab out of a field.

How we test

• Keyboard-only walkthroughs of every page and the whole quote form, in more than one browser.
• Automated checks in the browser's built-in accessibility and contrast tooling on each page before it ships.
• Manual review of the accessibility tree — headings, landmarks, labels, and names — rather than trusting an automated score, which can only catch a minority of real barriers.
• Zoom to 200% and a 320-pixel viewport, checking for reflow, clipping, and horizontal scrolling.
• Both colour schemes, and forced-colours / high-contrast mode.
• Screen-reader spot checks on the pages that carry the most weight: the home page, coverage pages, claims, and the quote form.

The site is reviewed when it changes and at least twice a year. The date at the top of this page is the last full review.

Known limitations

Being specific about what is imperfect is more useful than claiming everything is fine:

• Documents from carriers. Policy forms, applications, and declarations pages are produced by insurance companies, not by us. Some are scanned images with no text layer and no tagging, and we cannot fix them at the source. Ask us and we will read one to you, summarise it in an accessible email, or get an accessible version from the carrier.
• The client portal. Self-service policy documents and certificates live in a third-party portal we license rather than build. Its accessibility is the vendor's, and it does not meet the bar we set for this site. We raise defects with the vendor, and in the meantime anything the portal does, a person here will do for you by phone or email.
• No independent audit. Our conformance claim is a self-assessment. An external audit is worth doing and we have not done one.
• Assistive-technology coverage. We test with the screen readers and browsers we have. Combinations we have not tried may behave differently, and we would genuinely like to hear about it if yours does.

Getting information another way

Anything on this site is available in another format, free, and without you having to explain why you want it:

• Large print, on paper, posted to you.
• Plain-text or accessible-PDF versions of any page, quote, proposal, or policy summary, by email.
• Read aloud and explained over the phone, for as long as it takes — this is what we do all day anyway.
• In person at our office, 118 Ridgeline Court, Suite 240, Asheville, NC 28801.
• Through a friend, family member, carer, or authorised representative you nominate.

If you use a TTY or a relay service, dial 711 to reach us through Telecommunications Relay Services. You can also request that all future correspondence come to you in a particular format and we will record it against your file so you never have to ask twice.

Tell us about a problem

If any part of this site blocks you, we want to know — a report from someone who hit the barrier is worth more than another automated scan.

It helps if you can tell us the page, what you were trying to do, and what happened — plus the browser and any assistive technology you were using. If that is too much to gather, send what you have. We will not send you away for an incomplete report.

What we will do about it

• We acknowledge every accessibility report within 2 business days.
• We give you a substantive reply — the fix, a timeline, or an honest explanation of why it is hard — within 10 business days.
• While a fix is pending, we give you the information or the service another way immediately. You should never have to wait on our backlog to get insured.
• If you are not satisfied with our answer, ask for it to be escalated to the agency principal, and say so in your reply — that is not a formality, it goes to a different person.

Related: Privacy Policy · Terms of Use · Security