Accessibility Statement

Accessibility Statement

Effective date: September 22, 2026 · Version 1.0

VUGA Enterprises LLC, operating IsMyBillWrong.com, is committed to making this service usable by everyone, including people who use assistive technology. Medical billing disputes are time-limited and consequential; nobody should miss a deadline because a page would not work with their screen reader.

Conformance target

We aim to conform to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, which is the standard incorporated by Section 508 of the Rehabilitation Act via 36 CFR Part 1194.

Current status: partially conformant. "Partially conformant" means most of the standard is met, and the exceptions we are aware of are listed below rather than left for you to discover. We publish this as an honest status, not a marketing claim.

What we test, and how

Accessibility checks run automatically on every change, not as an occasional audit:

• Automated WCAG 2.1 A/AA checks (axe-core) run in continuous integration and block

a release on any serious or critical finding.

• The same checks run at 320, 768 and 1280 CSS pixel widths, so reflow and

small-screen layout are covered rather than assumed.

• Keyboard-only traversal is asserted by automated tests for the core journey:

uploading a bill, giving consent, reading findings, and managing an account.

• Colour contrast is verified against the palette tokens; text that cannot be

resolved to a definite contrast ratio fails the build rather than passing quietly.

• Every page is asserted to have exactly one main landmark and a working

"skip to main content" link as its first focusable element.

Conformance report (WCAG 2.1 Level AA)

This table follows the structure of a VPAT / Accessibility Conformance Report.

Principle 1 — Perceivable

| Criterion | Level | Status | Remarks | |---|---|---|---| | 1.1.1 Non-text Content | A | Supports | Decorative SVGs are aria-hidden; data tables carry captions. | | 1.2.x Time-based Media | A/AA | Not applicable | The service contains no audio or video. | | 1.3.1 Info and Relationships | A | Supports | Native semantic elements throughout; fieldsets and legends on grouped inputs. | | 1.3.2 Meaningful Sequence | A | Supports | Single-column reading order; no CSS-reordered content. | | 1.3.3 Sensory Characteristics | A | Supports | Instructions never rely on shape, size or position alone. | | 1.3.4 Orientation | AA | Supports | No orientation lock. | | 1.3.5 Identify Input Purpose | AA | Supports | Autocomplete tokens on identity and contact fields. | | 1.4.1 Use of Color | A | Supports | Findings and statuses carry text labels, not colour alone. | | 1.4.3 Contrast (Minimum) | AA | Supports | Body text meets 4.5:1 and large text 3:1 against the paper background. | | 1.4.4 Resize Text | AA | Supports | Relative units; layout holds at 200% zoom. | | 1.4.5 Images of Text | AA | Supports | No images of text other than the social preview image. | | 1.4.10 Reflow | AA | Supports | No horizontal scrolling at 320 CSS pixels; asserted in automated tests. | | 1.4.11 Non-text Contrast | AA | Supports | Focus indicators and control borders meet 3:1. | | 1.4.12 Text Spacing | AA | Supports | No fixed line heights that clip adjusted text. | | 1.4.13 Content on Hover or Focus | AA | Supports | Disclosures are click/keyboard activated, dismissible, and persistent. |

Principle 2 — Operable

| Criterion | Level | Status | Remarks | |---|---|---|---| | 2.1.1 Keyboard | A | Supports | Full journey operable by keyboard; scrollable regions are focusable. | | 2.1.2 No Keyboard Trap | A | Supports | No modal dialogs exist; disclosures use native details. | | 2.1.4 Character Key Shortcuts | A | Supports | No single-character shortcuts. | | 2.2.1 Timing Adjustable | A | Supports | No session time limit is imposed on reading. | | 2.2.2 Pause, Stop, Hide | A | Supports | No auto-updating or moving content. | | 2.3.1 Three Flashes | A | Supports | No flashing content. | | 2.4.1 Bypass Blocks | A | Supports | A skip link is the first focusable element on every page. | | 2.4.2 Page Titled | A | Supports | Every page has a unique, descriptive title. | | 2.4.3 Focus Order | A | Supports | DOM order matches visual order; focus is moved deliberately after pagination. | | 2.4.4 Link Purpose (In Context) | A | Supports | Link text is meaningful; no bare "click here". | | 2.4.5 Multiple Ways | AA | Supports | Navigation, footer links, sitemap and search-engine indexing. | | 2.4.6 Headings and Labels | AA | Supports | One h1 per page; descriptive headings and labels. | | 2.4.7 Focus Visible | AA | Supports | A visible focus ring on every interactive element. | | 2.5.1 Pointer Gestures | A | Supports | No multipoint or path-based gestures. | | 2.5.2 Pointer Cancellation | A | Supports | Activation occurs on the up-event. | | 2.5.3 Label in Name | A | Supports | Accessible names begin with the visible label. | | 2.5.4 Motion Actuation | A | Supports | No motion-actuated functionality. |

Principle 3 — Understandable

| Criterion | Level | Status | Remarks | |---|---|---|---| | 3.1.1 Language of Page | A | Supports | Every page declares its language; the language selector sets it. | | 3.1.2 Language of Parts | AA | Supports | Language names carry their own lang; untranslated passages are marked. | | 3.2.1 On Focus | A | Supports | Focus alone never changes context. | | 3.2.2 On Input | A | Supports | The language selector uses links and an explicit control, never navigate-on-change. | | 3.2.3 Consistent Navigation | AA | Partially supports | See known limitations — some pages carry no header navigation. | | 3.2.4 Consistent Identification | AA | Supports | Repeated controls are labelled consistently. | | 3.3.1 Error Identification | A | Supports | Errors are announced in text via role="alert". | | 3.3.2 Labels or Instructions | A | Supports | Every input has a persistent visible label. | | 3.3.3 Error Suggestion | AA | Supports | Messages say how to correct the problem. | | 3.3.4 Error Prevention (Legal, Financial, Data) | AA | Supports | Payment and deletion are confirmed and reversible or clearly warned. |

Principle 4 — Robust

| Criterion | Level | Status | Remarks | |---|---|---|---| | 4.1.2 Name, Role, Value | A | Supports | Native controls; aria-expanded and aria-current where applicable. | | 4.1.3 Status Messages | AA | Supports | Processing and results use role="status" / aria-live="polite". |

Known limitations

We would rather name these than let you find them:

1. Navigation is not present on every page. Several pages currently render

content and a footer without a top navigation bar. Every page is still fully reachable and the footer provides navigation, so this is a consistency gap (3.2.3) rather than a blocker. It is scheduled to be fixed.

1. Simplified Chinese uses your system font. We self-host fonts for every other

script; a complete Chinese webfont is too large to serve responsibly, so Chinese text renders in your device's own font. On rare devices without a Chinese font installed, some characters may not display.

1. Translations are machine-generated. Content in languages other than English

is produced by machine translation and may read awkwardly or, in places, be wrong. Where a translation and the English text conflict, the English version is the operative one. Please report anything confusing or incorrect.

1. Automated testing is not a substitute for people. Our checks are automated

and have not yet been supplemented by a formal audit with users of assistive technology. We welcome reports from people who use this service with one.

Assistive technologies

The service uses standard HTML semantics rather than custom widgets, so it is expected to work with current versions of screen readers including NVDA, JAWS, VoiceOver and TalkBack, and with speech-recognition and screen-magnification software. We do not claim verified support for any specific combination beyond the automated and keyboard testing described above.

Tell us about a barrier

If any part of this service is difficult or impossible for you to use, please tell us — including which page, what you were trying to do, and the assistive technology you were using, if any.

Email: [email protected]

We will acknowledge your report within 5 business days and tell you what we intend to do about it and when. If a barrier blocks you from meeting a billing deadline, say so in your message and we will treat it as urgent and help you complete the task another way.

This statement

This statement applies to IsMyBillWrong.com. It was last reviewed on the effective date above, and is reviewed whenever the accessibility test results change. It is provided for general information and, like our other published documents, is not legal advice.