Grant RTGrant RT
Privacy PolicyTerms of ServiceCookie PolicyAccessibility

GrantRT Accessibility Policy and Statement

Effective Date: September 1, 2026 Version: 1.0 Operator: dakdan LLC, a Colorado limited liability company, doing business as GrantRT Contact: info@grantrt.com Jurisdiction of operation: Colorado, United States of America


1. Commitment

GrantRT is committed to making the Service usable by everyone, including people with visual, auditory, motor, speech, and cognitive disabilities. Our customer base includes nonprofit organizations, educational institutions, and governmental subrecipients whose own funding carries nondiscrimination and accessibility obligations. Accessibility is treated as a product requirement, not a remediation project.


2. Conformance Standard

GrantRT designs, builds, and tests the platform at grantrt.com and the GrantRT application to conform with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, published by the World Wide Web Consortium. We also design toward:

  • Section 508 of the Rehabilitation Act, 29 U.S.C. § 794d, and the Revised 508 Standards, which incorporate WCAG Level AA
  • Americans with Disabilities Act Titles II and III as applied to commercial web services
  • Section 504 of the Rehabilitation Act as it applies to recipients of federal financial assistance
  • EN 301 549 for customers subject to European public sector accessibility requirements
  • Colorado House Bill 21-1110 accessibility requirements applicable to state and local government entities, for public sector customers

Current conformance status: partially conformant with WCAG 2.1 Level AA. Partially conformant means most of the Service meets the standard, with known exceptions documented in Section 5.


3. Accessibility Measures in Practice

GrantRT applies the following measures across design, engineering, and operations:

  1. Semantic HTML structure with correct landmark regions and heading hierarchy
  2. Full keyboard operability for all interactive controls, including modals, menus, tables, and the document editor, with no keyboard traps
  3. Visible focus indicators meeting non-text contrast requirements
  4. Accessible names, roles, and states on custom components using ARIA only where native semantics are insufficient
  5. Text and interface contrast ratios of at least 4.5 to 1 for body text and 3 to 1 for large text, icons, and interface boundaries
  6. Text resizing to 200 percent and reflow at 320 CSS pixels without loss of content or function
  7. Form fields with programmatically associated labels, clear instructions, inline error identification, and error suggestions
  8. Status messages announced to assistive technology through live regions, including save, upload, validation, and submission states
  9. Text alternatives for meaningful images, and decorative images marked as such
  10. Captions and transcripts for tutorial and training video content
  11. Respect for reduced motion preferences and no content that flashes more than three times per second
  12. Session timeout warnings with the ability to extend, so that unsaved application work is not lost
  13. Automated accessibility testing integrated into the continuous integration pipeline
  14. Manual testing with keyboard-only navigation and screen readers
  15. Accessibility acceptance criteria included in design review and pull request review

4. Assistive Technology Compatibility

The Service is tested against current versions of:

Assistive Technology Platform Browser
NVDA Windows Chrome, Firefox
JAWS Windows Chrome, Edge
VoiceOver macOS Safari
VoiceOver iOS Safari
TalkBack Android Chrome
Dragon NaturallySpeaking Windows Chrome
Browser zoom and OS magnification All All supported

We support the current and prior major version of Chrome, Edge, Firefox, and Safari. Older browsers may not render accessibility features correctly.


5. Known Limitations

We disclose known limitations rather than claim full conformance. As of the Effective Date:

  1. Complex data tables and Gantt-style deadline views. Dense grid and timeline visualizations may be difficult to navigate with a screen reader. An accessible list view is available as an alternative for the same data.
  2. Third-party embedded content. Payment forms, support chat, and video players are supplied by third parties and may not fully conform. We monitor vendor conformance and raise defects with vendors.
  3. Customer-uploaded documents. PDFs, spreadsheets, and images uploaded by customers or downloaded from funders are outside our control and are frequently untagged or scanned. GrantRT does not remediate customer or funder documents.
  4. Generated PDF exports. Exported application packets are tagged for structure, but tagging fidelity varies with the source content supplied by the customer.
  5. Legacy interface areas. A small number of administrative screens predate the current design system and are scheduled for remediation.

Each known limitation has an assigned owner and a remediation target. Status is reviewed quarterly.


6. Grant Portals and Third-Party Systems

GrantRT automates interaction with third-party Grant Portals operated by federal, state, local, tribal, corporate, and private funders. GrantRT does not control the accessibility of those portals and makes no representation regarding their conformance. Where a customer must interact with a portal directly, accessibility questions should be raised with that portal operator. Where a portal barrier prevents a customer from completing work in GrantRT, contact us and we will look for an alternative path within our Service.


7. Alternative Access and Accommodations

If any part of the Service is not accessible to a user, GrantRT will provide the information or function through an alternative method at no additional cost. Alternatives may include:

  • Direct assistance from our support team to complete a task
  • Data provided in an alternative accessible format
  • An accessible list or text equivalent of a visual view
  • A scheduled working session with a support engineer

Request an accommodation by writing to info@grantrt.com with the subject line "Accessibility Request."


8. Feedback and Response Commitment

We want to hear about barriers. Include the page or feature, the assistive technology and version, the browser and operating system, and what you expected to happen.

Email: info@grantrt.com Subject line: Accessibility Request

Our commitments:

Stage Commitment
Acknowledgment Within 5 business days
Substantive response with assessment and plan Within 15 business days
Critical barrier blocking a submission deadline Prioritized immediately, with a manual workaround provided
High severity barrier Remediation targeted within 30 days
Medium and low severity barrier Scheduled into the product roadmap and reported quarterly

If a response does not resolve the issue, escalate by writing to info@grantrt.com with the subject line "Accessibility Escalation." Escalations are reviewed by product leadership within ten (10) business days.


9. Procurement and Documentation for Customers

Public sector and federally funded customers frequently require accessibility documentation as part of procurement. On request to info@grantrt.com with the subject line "Accessibility Request," GrantRT will provide:

  • A Voluntary Product Accessibility Template (VPAT) based on the current release
  • A summary of the most recent accessibility audit and remediation status
  • The current known limitations list with remediation targets

10. Governance and Review

  • Accessibility is owned by the product engineering function, with an accountable owner named internally.
  • Automated scans run on every build. Manual audits are performed at least annually and before any major release.
  • This Statement is reviewed at least annually and after any material interface change.
  • All product and design personnel receive accessibility training as part of onboarding and annually thereafter.
  • Accessibility defects are tracked in the same system as functional defects and are subject to the same severity and service level process.

11. Customers' Own Obligations

GrantRT's conformance does not satisfy a customer's own legal obligations. Customers that are recipients of federal financial assistance, public entities, or places of public accommodation remain responsible for the accessibility of their own websites, programs, communications, and grant deliverables. Nothing in this Statement constitutes legal advice or a warranty of a customer's compliance.


12. Changes to This Policy

Material changes take effect thirty (30) days after notice by email to account administrators and by in-product notice. Non-material changes take effect on posting with an updated Effective Date and Version. Prior versions are available on request.


13. Contact

dakdan LLC d/b/a GrantRT Colorado, United States of America Email: info@grantrt.com Subject line: Accessibility Request

This Statement is provided in the spirit of the W3C Web Accessibility Initiative guidance on accessibility statements and is updated as the Service changes.

Grant RTGrant RT

AI-powered grant management platform for nonprofits.

Product

FeaturesPricingHow It WorksHow We Use AI

Company

CareersInternshipsApply for InternshipGrant Readiness Checklist

Legal

Privacy PolicyTerms of ServiceCookie PolicyAccessibility

Get Started

Sign UpSign In

© 2026 Grant RT. All rights reserved. GrantRT.com