Skip to main content
Bluenilla

Accessibility statement

This site is built to the standard we sell.

Bluenilla is committed to making this website usable by everyone, including people who navigate with a keyboard, a screen reader, a magnifier, or voice control. We publish this statement because every public entity we work with is expected to publish one, and because a vendor who sells accessibility should be willing to be measured against it.

Conformance summary

Conformance target
WCAG 2.1 Level AA
Conformance status
Fully conformant, with the exceptions noted below
Last evaluated
Applies to
bluenilla.com and all pages under it
Evaluated by
Bluenilla LLC (self-evaluation)

01The standard we measure against

WCAG 2.1 Level AA, the standard the rule actually names.

The Web Content Accessibility Guidelines are the reference for making web content usable by people with disabilities. There are three levels: A, AA, and AAA. The Department of Justice's Title II rule adopts WCAG 2.1 Level AA as the technical standard for state and local government web content, so that is the target for this site and for every site we build.

“Fully conformant” means that at the last evaluation every applicable success criterion was met on every page we publish, with only the exceptions listed in the limitations section below. It is a claim about a date, not a permanent condition: content changes, browsers change, and so this page carries the date it was last checked.

02How this site was evaluated

Automated scanning, then a person at a keyboard.

A scanner alone is not an audit. Roughly a third of the WCAG success criteria can be checked by software; the rest require judgment about whether a page is genuinely usable. This site was last evaluated on using all four methods below.

  1. 01

    Automated scanning

    Every page is scanned against the WCAG 2.1 AA rule set. Automated tools reliably catch contrast, missing names, and structural errors, but they detect only a fraction of the criteria, so they are the beginning of our testing and not the end of it.

  2. 02

    Manual keyboard testing

    Each page is operated end to end with the keyboard alone: tab order against visual order, a focus indicator visible at every stop, no keyboard traps, and the skip link reaching the main landmark. Forms are submitted empty and with bad input to confirm errors are announced and reachable.

  3. 03

    Manual screen reader testing

    Pages are read with NVDA on Windows and VoiceOver on macOS and iOS. We check heading order, landmark navigation, table headers read against their cells, form labels and error text, and that anything decorative stays silent.

  4. 04

    Zoom and reflow

    Verified at 200% browser zoom and at a 320 pixel viewport width with no horizontal scrolling and no loss of content or function.

03Known limitations

What we know is imperfect.

At the last evaluation we found no outstanding WCAG 2.1 AA failures on the pages of this site. The items here are the boundaries of what we can control rather than defects we are carrying, and we list them because a statement that claims perfection is not worth reading.

If you find something we have missed, we would genuinely rather hear it than not. Reporting a barrier is described below.

  • Documents published by others

    Meeting minutes, budgets, and ordinances supplied to us as PDFs may not be tagged for accessibility. We do not alter the content of a public record. Where a PDF is not accessible we will provide the same information in an accessible format on request, and we advise clients on producing tagged documents going forward.

  • Third-party embeds

    Where a page embeds a service we do not control, such as a mapping tool or a payment portal, that vendor governs its own accessibility. We test embeds before use, disclose what we find, and will help pursue a remedy or an accessible alternative with the vendor.

  • Linked external sites

    This statement covers pages we publish. Sites we link to, including state and federal resources, are outside our control and are not covered by it.

04Reporting a barrier

Tell us what did not work, and we will answer you.

If any part of this site prevented you from doing what you came to do, please tell us. You do not need to know which guideline applies or use any particular terminology. Describing the page you were on, what you were trying to do, and what happened is enough.

It helps if you can tell us the browser and any assistive technology you were using, but please do not let a missing detail stop you from writing.

How to reach us

Mail
Bluenilla LLC
Mount Joy, Lancaster County, PA

Our response time

  • Within 2 business daysWe acknowledge your report and tell you who is handling it.
  • Within 10 business daysWe give you our findings and either a fix or a dated plan, plus the information you were after in another format if the fix will take longer.

Reports about a township or borough site we maintain are passed to that municipality the same day, since the public entity remains responsible for its own content under Title II.

05Formal complaints

If our answer does not resolve it.

Contacting us is not a precondition for anything else, and it does not limit any right you have. If you are not satisfied with our response, you may file a complaint with the Civil Rights Division of the United States Department of Justice at civilrights.justice.gov. If your concern is about a township or borough site, that municipality also has its own ADA grievance procedure and, in most cases, a designated ADA coordinator.

This statement was prepared on and applies to bluenilla.com. It is reviewed whenever the site changes materially, and at least once a year.