Our commitment
Government Window is committed to making this website and the resident-facing payment experiences we operate usable by everyone, including people who use assistive technology. Payments are the part of government most residents actually touch, and a payment channel nobody can complete is not a payment channel.
The standard we work to
We design, build and test against the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. Accessibility is included in design review, development and QA rather than treated as a remediation exercise after launch.
What that means in practice
- Every interactive element is reachable and operable by keyboard
- A visible focus indicator is present at all times
- Form fields have persistent visible labels, not placeholder-only labels
- Errors are described in text and announced to assistive technology
- Text and interface controls meet AA contrast requirements
- Animation is decorative and respects the reduced-motion system preference
- Pages work at 200% zoom without horizontal scrolling
- Content structure uses semantic headings and landmark regions
Alternatives to the web
Accessibility also means choice of channel. A resident who cannot or prefers not to use a web form can pay through a bilingual toll-free IVR line, at an agency counter, or with help from our support team on the phone.
Known limitations
Accessibility is a continuous obligation rather than a one-time certification. Where we identify a barrier we treat it as a defect and schedule a fix. Third-party components and agency-supplied content may occasionally fall short of our standard; we work with those providers to resolve issues.
Reporting a barrier
If you encounter a barrier on this website or on a Government Window payment page, please tell us. Reports from people using the site are the most useful accessibility input we receive, and we respond to every one.
- Email: support@governmentwindow.com
- Phone: 877-575-7233 (Mon–Fri, 8:00 AM – 5:00 PM ET)
Please include the page address, what you were trying to do, and the assistive technology and browser you were using if you know them.
For agencies
If your jurisdiction has a specific conformance requirement, accessibility policy or procurement standard, bring it to the requirements session. It shapes configuration decisions and is far cheaper to accommodate before launch than afterwards.