Conformance status

GO-180 aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. These guidelines explain how to make web content more accessible to people with a wide range of disabilities. Conformance with these guidelines helps ensure that the platform is accessible to the broadest possible audience.

While we strive for WCAG 2.1 Level AA conformance, some content may not yet fully conform. We are actively working to identify and resolve any gaps.

Standards we target

• WCAG 2.1 Level AA— the W3C web content accessibility guidelines, the floor for federal accessibility compliance.
• Section 508of the Rehabilitation Act — required for any service that may be used by federal employees and veterans interacting with federal benefits.
• ADA Title III— the Americans with Disabilities Act standard for places of public accommodation, including digital services.

Technologies relied upon

The accessibility of GO-180 relies on the following technologies to work with the particular combination of web browser and assistive technologies or plugins installed on your computer:

• HTML5 — semantic markup with appropriate landmark regions (main, nav, aside, header, footer).
• CSS— responsive design with high-contrast color pairs verified against WCAG AA contrast ratios.
• JavaScript— progressive enhancement for interactive features; core content remains accessible without JavaScript where possible.
• WAI-ARIA— Accessible Rich Internet Applications attributes for dynamic content, custom widgets, dialogs, and live regions not fully described by native HTML semantics.

These technologies are relied upon for conformance with the accessibility standards used.

Built-in accessibility features

• Skip-to-content link on every page (Tab from page load to access).
• Keyboard navigation— every interactive element is reachable and operable with keyboard alone.
• Screen-reader landmarks — semantic HTML5 (main, nav,aside) with ARIA roles where the structure isn't self-describing.
• Reduced-motion support — honors prefers-reduced-motion; animations collapse to static state for users with vestibular disorders or migraine sensitivity.
• Crisis line— dial-tap and SMS-tap links so the 988 / 838255 numbers can be activated directly without copy-paste.
• Color contrast— brand palette verified against WCAG AA contrast ratios (minimum 4.5:1 for normal text, 3:1 for large text).
• Focus indicators— visible focus rings on every interactive element, meeting WCAG 2.4.7 Focus Visible requirements.
• Resizable text— all text can be resized up to 200% without loss of content or functionality.
• Form labels — all form inputs have associated labels, either visible or via aria-label / aria-labelledby.

Assessment methods

GO-180 assesses the accessibility of our platform through the following methods:

• Self-evaluation— our development team performs regular accessibility reviews using automated tools and manual testing.
• Automated testing— axe-core and Lighthouse accessibility audits run during development and in our CI/CD pipeline.
• Manual testing— keyboard-only navigation testing, screen-reader testing (VoiceOver, NVDA), and high-contrast mode verification.
• User feedback— we incorporate accessibility feedback from our veteran user community into ongoing improvements.

Known limitations

Despite our efforts to ensure accessibility of GO-180, there may be some limitations. Below is a description of known limitations and potential solutions. Please contact us if you observe an issue not listed below.

• Form-label coverage— ongoing audit of signup and profile flows to ensure full label association across all form controls.
• Login modal— focus trap and ARIA attribute review is in progress.
• Dark mode— not yet shipped; will ship with verified WCAG AA contrast pairs for all color tokens.
• Automated axe-core testing— being integrated into every pull request to catch regressions before deployment.
• Third-party content— some embedded third-party widgets (payment forms, maps) may not fully conform to WCAG 2.1 AA. We work with vendors to improve their accessibility.

We are actively addressing these gaps and prioritize accessibility fixes alongside feature development.

Feedback and contact information

We welcome your feedback on the accessibility of GO-180. If you encounter accessibility barriers or cannot use any part of the platform because of a disability, please tell us so we can fix it. Use whichever channel is easiest:

• Email accessibility@go180.ai— we aim to respond within two business days.
• Contact form— pick "Accessibility issue" from the topic dropdown.

We try to respond to accessibility feedback within two business days and to resolve identified issues within 10 business days.

Email accessibility@go180.ai

Enforcement procedure

If you are not satisfied with our response to your accessibility concern, you may file a complaint with the appropriate enforcement body:

• U.S. Department of Justice — for ADA Title III complaints, visit ADA.gov.
• U.S. Access Board— for Section 508 complaints related to federal technology standards, visit access-board.gov.

Veterans may also contact the Section 508 Program for assistance with federal information technology accessibility.

Crisis support

If you are a veteran in crisis, please reach out to the Veterans Crisis Line. They are always available:

• Call 988 and press 1
• Text 838255