Last Updated: April 24, 2026

Our Commitment to Accessibility

QuickScores is committed to ensuring digital accessibility for all people, including those with disabilities. We are continually improving the user experience for everyone and applying the relevant accessibility standards to ensure we provide equal access to all of our users.

Conformance Status

The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA. QuickScores is working to achieve WCAG 2.1 Level AA conformance.

QuickScores is partially conformant with WCAG 2.1 Level AA. Partial conformance means that some parts of the content do not fully conform to the accessibility standard. We are actively working to address known accessibility issues and improve conformance across all of our digital properties.

A full per-criterion Accessibility Conformance Report (VPAT® 2.5Rev WCAG edition), dated April 24, 2026, is available upon request for organizations conducting procurement reviews. See the Assessment and Evaluation section below for details.

Accessibility Features

QuickScores includes the following accessibility features:

Navigation Accessibility

• Keyboard-Accessible Navigation: Our navigation menu is fully keyboard accessible using standard Tab key navigation, with proper focus indicators on all menu items.
• Skip Navigation Link: A "Skip to main content" link appears as the first keyboard-focusable element on every page, allowing screen reader and keyboard users to bypass repetitive navigation.
• Semantic HTML: Our pages use proper HTML5 semantic elements including header, nav, main, footer, and aside for clear page structure.
• Landmark Regions: ARIA landmark roles help screen reader users navigate page sections efficiently.

Visual Accessibility

• High Contrast Themes: QuickScores offers 8 accessible color theme variants (Black, Blue, Green, Navy, Orange, Purple, Red, and Tan) designed to meet WCAG 2.1 AA contrast requirements with a minimum 4.5:1 contrast ratio for normal text.
• Enhanced Focus Indicators: Visible focus indicators (2px dotted outlines using theme colors) help keyboard users understand which element currently has focus across all interactive elements.
• Responsive Design: Our interface adapts to different screen sizes and supports zooming up to 200% without loss of content or functionality.
• Windows High Contrast Mode: Our CSS includes support for forced-colors media queries to respect Windows High Contrast Mode settings.

Keyboard Accessibility

• Keyboard Navigation: Our accessible navigation menu and many interactive elements can be accessed and operated using only a keyboard. We are working to ensure all interactive elements meet this standard.
• Focus Indicators: Visible focus indicators help keyboard users understand which element currently has focus.
• Skip Navigation: Skip links allow keyboard users to bypass repetitive navigation and move directly to main content.

Screen Reader Support

• Semantic Structure: Our pages use proper HTML5 semantic elements and ARIA roles to communicate page structure to screen readers.
• Proper Heading Hierarchy: All public pages use logical heading structure (h1 through h6) without skipping levels to aid screen reader navigation.
• Text Alternatives: All informative images and icons on public pages include meaningful alternative text for screen reader users.
• Form Labels: All form inputs on public pages have programmatically associated labels for clear screen reader announcement.

Reduced Motion & Dynamic Content

• Reduced Motion Support: Our CSS honors the prefers-reduced-motion media query site-wide, suppressing transitions and animations for users who have requested reduced motion in their operating system settings.
• Windows High Contrast Mode: The forced-colors CSS media query is honored so that the product respects Windows High Contrast Mode palette choices.
• Live Region Announcements: Two global ARIA live regions (#aria-live-region with aria-live="polite" for informational messages and #aria-live-alert with role="alert" for urgent errors) are injected on every page and hooked into Toastr notifications, DataTables page/filter/sort events, modal open and close, form validation, and aria-busy state changes on dynamic content, giving assistive technologies a single uniform status channel.
• Auto-Enabled Accessibility Mode: Organizations serving US municipalities of 50,000 or more residents (per 2020 US Census data) are automatically enrolled in Accessibility Mode to remove the administrative burden from clients with an April 2026 ADA Title II deadline.
• Per-User Override: Individual visitors can enable Accessibility Mode for themselves via the footer toggle; the choice is persisted in a 30-day cookie regardless of the organization's default.

Accessibility Mode

QuickScores offers an optional accessibility mode that can be enabled at both the organization level and individual user level. When enabled, accessibility mode provides enhanced visual contrast and additional accessibility features for users who need them.

For Organization Administrators: You can enable accessibility mode for your entire organization through your organization settings in the admin panel. Organizations serving US municipalities of 50,000 or more residents (per 2020 US Census data) have Accessibility Mode automatically enabled to support compliance with the April 2026 ADA Title II deadline.

For Individual Users: Users can enable or disable accessibility mode through the toggle in the page footer. If your organization requires accessibility mode, the toggle will be disabled and display "(Required)" to indicate it cannot be changed.

Third-Party Content

Certain screens embed third-party widgets whose accessibility is governed by each vendor's own Accessibility Conformance Report. QuickScores currently relies on two such integrations:

• Clover (CartConnect) card-entry tokenizer on the payment-completion screen.
• Google Maps embeds on location-detail pages.

QuickScores warrants the accessibility of the surrounding page chrome and the handoff to and from these widgets. The internal accessibility of each widget is as reported by its respective vendor.

Known Limitations

Our public-facing Accessibility Conformance Report (see Assessment and Evaluation below) lists the specific WCAG 2.1 criteria where QuickScores currently reports Partially Supports or Does Not Support. The open items behind those classifications are summarized here in plain language:

• Authenticated Pages: Public-facing pages are covered by the current WCAG 2.1 Level AA conformance claim. Authenticated and administrative pages are being extended during the April–May 2026 remediation cycle, which is adding ARIA attributes, converting legacy <input type="button"> controls to native <button>, adding <label for> associations on form fields, and filling in landmark regions.
• Accessible Theme Palette Regressions: The Orange and Tan accessible theme variants still carry theme-specific header H1, logo, and H2 contrast regressions queued for the next palette review pass. A smaller residual issue on the Blue theme's header-link color on a few marketing pages is queued for the same pass. All other accessible theme variants (Black, Green, Navy, Purple, Red) pass WCAG AA on the tested page set.
• Zebra-Row Link Contrast: On one listing view (ResultsDisplay.php), the zebra-row link color #1f6bb6 on #e7e7e7 measures 4.42:1, just below the 4.5:1 WCAG AA minimum. A single-commit fix to either the link color or the alternating row background is tracked.
• Form Labels on Contact, Login, and Forgot Password: A small number of pre-existing label_missing reports remain on the Contact, Login, and Forgot Password forms. These are tracked in the ongoing form-audit pass.
• Session Timing Affordance: Legacy authenticated pages do not currently display an in-app session-expiry warning or a one-click extend control. A session-keepalive dialog is on the April–May 2026 remediation roadmap.
• Organization-Uploaded Cover Photos: A small number of organization-uploaded cover photos carry the generic alternative text alt="cover photo". An upload-time requirement for descriptive alt text is being added.
• Help Drawer Video Captions, Transcripts, and Audio Description: The Help Drawer surfaces prerecorded tutorial videos via YouTube and Vimeo embeds. Most videos carry platform-provided captions; a small number are known to be missing captions, and the library does not yet ship full text transcripts or audio-described alternative tracks. A library-wide captions, transcripts, and audio description pass is in progress.
• Third-Party Widget Internals: The Clover (CartConnect) tokenizer and Google Maps embeds described above in Third-Party Content are covered by their respective vendor ACRs.

We are prioritizing these remaining issues. For a detailed timeline, please see our Accessibility Roadmap below.

Assistive Technologies

QuickScores aims to be compatible with the following assistive technologies:

• Screen Readers: JAWS, NVDA, VoiceOver, TalkBack
• Screen Magnification Software: ZoomText, MAGic
• Speech Recognition Software: Dragon NaturallySpeaking
• Alternative Input Devices: Switch controls, eye tracking, mouth sticks

Browsers and Devices

QuickScores supports modern web browsers and is being tested for compatibility with common assistive technologies including:

• Safari with VoiceOver on macOS and iOS
• Chrome and Firefox with NVDA on Windows
• Edge with Narrator on Windows
• Chrome with TalkBack on Android

Mobile Applications

The QuickScores mobile application (iOS and Android) is designed with accessibility in mind and supports:

• VoiceOver (iOS) and TalkBack (Android) screen readers
• Dynamic text sizing
• High contrast and dark mode support
• Voice control and switch control

Accessibility Roadmap

We are committed to continuously improving accessibility. Our accessibility program is organized into three horizons:

Completed (2026 Q2)

• WCAG 2.1 Level AA remediation across all public-facing pages: semantic HTML5 landmarks, heading hierarchy, form labels, descriptive alt text, consistent focus indicators, and proper navigation patterns.
• Eight accessible color theme variants (Black, Blue, Green, Navy, Orange, Purple, Red, Tan) with WCAG-tuned SCSS palettes.
• prefers-reduced-motion CSS media query honored site-wide.
• forced-colors CSS media query support for Windows High Contrast Mode.
• Auto-enable of Accessibility Mode for US organizations in municipalities of 50,000 or more residents (per 2020 US Census data).
• Global ARIA live region infrastructure (#aria-live-region and #aria-live-alert) wired into Toastr notifications, DataTables events, modal open and close, form validation, and aria-busy transitions on dynamic content.
• Publication of the VPAT® 2.5Rev WCAG edition Accessibility Conformance Report (April 24, 2026).

Short Term (2026 Q3-Q4)

• Authenticated-page WCAG 2.1 Level AA remediation: ARIA attributes, native <button> conversions, <label for> associations, and landmark regions (in progress, April–May 2026 cycle).
• Orange and Tan accessible palette regressions on header H1 / logo and H2 contrast.
• Site-wide zebra-row link contrast fix on ResultsDisplay.php.
• Session-keepalive dialog with an in-app expiration warning and one-click extend control for long-lived authenticated forms.
• Help Drawer captions audit plus a transcripts and audio-description pass across the tutorial library.
• Upload-time requirement for descriptive alt text on organization-uploaded cover photos.
• Expansion of the automated WAVE sweep to cover authenticated pages.

Long Term (2027 Q2+)

• Pursue WCAG 2.2 Level AA conformance as standards evolve.
• Integrate automated accessibility testing into the CI/CD pipeline.
• Commission a third-party external accessibility audit.
• Provide accessibility training for content creators and organization administrators.

Feedback and Contact Information

We welcome your feedback on the accessibility of QuickScores. Please let us know if you encounter accessibility barriers:

• Email: support@quickscores.com
• Mailing Address:
  QuickScores LLC
  1303 Cheyenne Drive
  Richardson, TX 75080
• Contact Form: Submit a message through our contact form

We try to respond to accessibility feedback within 2 business days. When reporting an accessibility issue, please include:

• The page URL where you experienced the issue
• A description of the problem
• The assistive technology you were using (if applicable)
• Your browser and operating system

Formal Complaints

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

U.S. Department of Justice

Civil Rights Division
Disability Rights Section
950 Pennsylvania Avenue, NW
Washington, D.C. 20530
File a complaint online
Phone: 1-800-514-0301 (voice)
TTY: 1-800-514-0383

Assessment and Evaluation

This accessibility statement was originally drafted on April 15, 2026 and most recently reviewed on April 24, 2026. QuickScores is conducting ongoing evaluation using:

• Self-evaluation: Internal assessment by the QuickScores development team.
• Automated testing: WebAIM WAVE API scans across a representative set of 30 pages per accessible theme variant, plus an internal WCAG contrast toolkit that maps failing foreground/background pairs back to the SCSS source variable that produced them.
• Manual testing: Tab-only keyboard navigation, macOS VoiceOver + Safari spot-checks, and semantic structure review against the accessibility tree.
• User feedback: Reports from users about accessibility barriers submitted to support@quickscores.com.

A Voluntary Product Accessibility Template (VPAT®) Accessibility Conformance Report (ACR), based on the VPAT® 2.5Rev WCAG edition and dated April 24, 2026, is available upon request for organizations conducting procurement reviews. Please contact support@quickscores.com to request a copy.

Technical Specifications

Accessibility of QuickScores relies on the following technologies to work with the particular combination of web browser and any assistive technologies or plugins installed on your computer:

• HTML5
• WAI-ARIA (Accessible Rich Internet Applications)
• CSS3
• JavaScript (ECMAScript 2015+)

These technologies are relied upon for conformance with the accessibility standards used. JavaScript is required for some interactive features to function properly.

Limitations and Alternatives

Despite our best efforts to ensure accessibility of QuickScores, 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.

If you experience difficulty using QuickScores: We are committed to providing you with alternative access. Please contact us using the information above, and we will work with you to provide the information or service you need in an accessible format.

Accessibility Standards

This website aims to conform to the following standards:

• Web Content Accessibility Guidelines (WCAG) 2.1 Level AA
• Section 508 of the Rehabilitation Act (U.S. Federal Standard)
• Americans with Disabilities Act (ADA) Title II Digital Accessibility Requirements

Additional Resources

For more information about web accessibility, please visit:

• W3C Web Accessibility Initiative (WAI)
• ADA.gov - Americans with Disabilities Act
• WebAIM - Web Accessibility In Mind
• Section508.gov - Federal Accessibility Standards

Effective Date: April 24, 2026

Last Updated: April 24, 2026

We are committed to providing an accessible website for all users. If you have any questions or feedback about this accessibility statement or the accessibility of QuickScores, please contact us.