A WCAG 2.1 Level A and AA report for the Online Water Bill customer site, using the ITI VPAT® 2.5 WCAG edition. This is a vendor-authored Accessibility Conformance Report, not a third-party lab certificate.
Product description: Cloud utility billing for a water association or city utility. This report covers the customer website: the association homepage, sign in, create account, guest pay, and My Account (bills, usage, pay, autopay, and paperless). Card fields in Stripe Payment Element are Stripe's product. Staff, field, meter-reading, maps, inventory, and Coral phone are not in this report. Association-written homepage and CMS copy is the association's content.
Applicable standards: WCAG 2.1 Level A and Level AA. WCAG 2.0 is included because it is part of 2.1. WCAG 2.2 is not claimed. Section 508 and EN 301 549 tables are not in this edition.
Evaluation methods: Source review of the customer-facing Vue pages and shared form controls. Automated checks in the product test suite, including skip link, landmarks, form errors, labels, and payment method radios. Keyboard and focus patterns in Button, Input, Select, and ModalBase. No third-party laboratory audit. No full screen-reader pass of every tenant theme. Findings are as of the report date.
Terms:
This report is not a claim that every screen is certified. Gaps listed as Partially Supports are remediated as they are found. A later edition will replace this one.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Partially Supports | Decorative icons in our chrome are hidden from assistive tech. Association homepage photos and CMS images may lack alternative text. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The customer site does not ship prerecorded audio-only or video-only media. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | The customer site does not ship prerecorded synchronized media. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | The customer site does not ship prerecorded video. |
| 1.3.1 Info and Relationships | Partially Supports | Sign-in, create account, guest pay, and My Account use labeled fields. Payment history tables expose column headers. Some custom widgets and association CMS markup may not expose every relationship. |
| 1.3.2 Meaningful Sequence | Supports | Customer flows follow a single-column reading order that matches the DOM. |
| 1.3.3 Sensory Characteristics | Supports | Instructions name the field or action. They do not rely on shape, size, or position alone. |
| 1.4.1 Use of Color | Partially Supports | Form errors are also announced as text. Some status chips may lean on color in addition to a word. |
| 1.4.2 Audio Control | Not Applicable | The customer site does not play audio automatically. |
| 2.1.1 Keyboard | Partially Supports | Sign-in, create account, guest pay, and My Account are built for keyboard use, including saved-method radios. Stripe card fields follow Stripe. Some tenant-specific widgets have not had a full keyboard pass. |
| 2.1.2 No Keyboard Trap | Supports | Focus can leave our dialogs and pages. Stripe fields are Stripe's control. |
| 2.1.4 Character Key Shortcuts | Not Applicable | The customer site does not register single-character shortcuts. |
| 2.2.1 Timing Adjustable | Partially Supports | Signed-in sessions can expire. There is not a customer-facing extend-time control on every timeout. |
| 2.2.2 Pause, Stop, Hide | Supports | The customer site does not use a required moving, blinking, or auto-updating information region. |
| 2.3.1 Three Flashes or Below Threshold | Supports | The customer site does not flash more than three times in one second. |
| 2.4.1 Bypass Blocks | Supports | A skip link moves keyboard users to the main landmark. |
| 2.4.2 Page Titled | Supports | The document title includes the association name for that site. |
| 2.4.3 Focus Order | Partially Supports | Forms and dialogs follow a forward order. Some homepage layouts can place decorative blocks in the tab order before the main action. |
| 2.4.4 Link Purpose (In Context) | Supports | Customer chrome links have a purpose from the link text or the surrounding sentence. |
| 2.5.1 Pointer Gestures | Supports | Customer tasks do not require a multipoint or path-based gesture. |
| 2.5.2 Pointer Cancellation | Supports | Activation is on the up event for buttons and links we ship. |
| 2.5.3 Label in Name | Partially Supports | Visible labels are used as the accessible name on shared inputs. A few icon-only controls rely on an aria-label. |
| 2.5.4 Motion Actuation | Not Applicable | The customer site does not require device motion to operate a feature. |
| 3.1.1 Language of Page | Supports | The root language is English. |
| 3.2.1 On Focus | Supports | Moving focus does not submit a form or change context by itself. |
| 3.2.2 On Input | Partially Supports | Most fields wait for a button. Guest pay account and invoice fields auto-advance after five digits. |
| 3.3.1 Error Identification | Supports | Sign-in, create account, and guest pay announce lookup and payment errors with an alert. |
| 3.3.2 Labels or Instructions | Supports | Shared inputs expose a visible label. Required fields are marked in the control. |
| 4.1.1 Parsing | Supports | Pages are generated from well-formed templates. Duplicate IDs are treated as defects when found. |
| 4.1.2 Name, Role, Value | Partially Supports | Shared Button, Input, Select, and dialogs expose name, role, and state. Some custom homepage blocks are still being aligned to that pattern. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The customer site does not present live synchronized media. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | The customer site does not ship prerecorded video. |
| 1.3.4 Orientation | Partially Supports | Pages reflow in landscape and portrait in a current browser. Some mobile web-app meta tags request portrait on a few WebViews. |
| 1.3.5 Identify Input Purpose | Partially Supports | Sign-in, password reset, and create-account name fields use autocomplete tokens. Other customer fields may not yet identify purpose. |
| 1.4.3 Contrast (Minimum) | Partially Supports | Default chrome aims at 4.5:1 for body text. An association can set brand colors that fail contrast on some text or buttons. |
| 1.4.4 Resize Text | Supports | The viewport allows pinch-zoom. Text can be enlarged to 200 percent in a current browser without turning zoom off. |
| 1.4.5 Images of Text | Supports | Customer chrome uses real text. Association logos are images of a mark, not sentences. |
| 1.4.10 Reflow | Partially Supports | Sign-in, pay, and My Account reflow on a narrow viewport. Some wide tables on My Account may need horizontal scroll. |
| 1.4.11 Non-text Contrast | Partially Supports | Focus and input borders in the default theme are visible. Association colors can weaken non-text contrast. |
| 1.4.12 Text Spacing | Supports | Customer pages do not clip when a user increases line, letter, or word spacing to the WCAG values. |
| 1.4.13 Content on Hover or Focus | Partially Supports | Most extra content is in a dialog the user can dismiss. Some tooltips have not been verified for hover and focus dismiss. |
| 2.4.5 Multiple Ways | Partially Supports | Customers reach pages from the homepage, the menu, and a direct URL. There is no site-wide search on the customer site. |
| 2.4.6 Headings and Labels | Supports | Customer pages use a page heading. Form labels describe the field. |
| 2.4.7 Focus Visible | Partially Supports | Shared buttons and inputs show a focus-visible outline. Not every homepage control has been verified. |
| 3.1.2 Language of Parts | Partially Supports | The page language is English. Association CMS text in another language may not set a language attribute on that passage. |
| 3.2.3 Consistent Navigation | Supports | The customer header and menu stay in the same relative order across pages. |
| 3.2.4 Consistent Identification | Supports | Pay, sign in, and account actions keep the same names across the customer site. |
| 3.3.3 Error Suggestion | Partially Supports | Known field errors describe what to fix. Some server errors return a general message. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Partially Supports | A payment is confirmed in the pay flow before Stripe charges. Not every financial change has a separate review step. |
| 4.1.3 Status Messages | Partially Supports | Sign-in, create account, and guest pay errors use an alert. Some success toasts may not be exposed as a status message. |
Stripe publishes its own accessibility materials for Payment Element. Coral inbound phone is optional AI customer service and is outside this web ACR. Staff and field screens are a later report.
VPAT® is a registered service mark of the Information Technology Industry Council (ITI). This page follows the required VPAT heading fields and term definitions. ITI does not review or approve this report.
Online Water Bill LLC
Email: info@onlinewaterbill.com
Mailing address: PO Box 33, Deer, AR 72628