Accessibility Statement

Effective Date: November 5, 2026
Policy Owner: TLRDev
Website: https://tlrdev.com
Accessibility Contact: support@tlrdev.com

1. Our Commitment to Accessibility

TLRDev believes that technology should be accessible, inclusive, and usable by as many individuals as reasonably possible, including people with disabilities.

Accessibility is an important consideration in the design, development, operation, and improvement of digital products and services.

TLRDev is committed to identifying accessibility barriers, considering inclusive design practices, and making reasonable improvements to the digital experiences under its control.

We recognize that accessibility is an ongoing process requiring continued evaluation as technology, user needs, and accessibility standards evolve.

This Accessibility Statement establishes the general accessibility principles and objectives applicable to TLRDev and its Covered Projects.

2. Scope of This Statement

This statement is intended to apply to existing and future digital projects developed, designed, created, published, operated, maintained, distributed, licensed, sold, or otherwise made available by TLRDev, to the extent TLRDev controls the relevant product or has authority to address its accessibility.

Covered Projects may include:

Websites and Online Services

  • Websites and online platforms.

  • Web applications.

  • Software as a Service (SaaS) platforms.

  • Online communities.

  • Customer portals and dashboards.

  • Digital marketplaces.

  • Online tools and utilities.

  • Subscription based services.

  • Web based games.

  • Application programming interfaces and related documentation.

Mobile Applications

  • Android applications.

  • iOS applications.

  • Mobile games.

  • Cross platform applications.

  • Progressive Web Applications.

  • Mobile productivity and utility software.

  • Other mobile digital products.

Desktop Software

  • Windows applications.

  • Linux applications.

  • macOS applications.

  • Desktop games.

  • Software utilities.

  • Productivity applications.

  • Other independently developed desktop software.

Digital Products and Content

  • Software packages.

  • Plugins and extensions.

  • Digital documents.

  • Electronic publications.

  • Original multimedia content.

  • Interactive digital experiences.

  • Other products and materials made available electronically.

This statement is not limited to projects specifically displayed on TLRDev.com.

It is intended to provide a general accessibility framework for current and future Covered Projects.

3. Definition of Covered Projects

For purposes of this statement, a Covered Project is a website, application, game, digital product, or service for which TLRDev is responsible for the relevant user experience or has authority to implement accessibility improvements.

A Covered Project may operate under an independent brand name, domain, application store listing, or product identity.

Projects owned or independently operated by clients, business partners, or separate legal entities are not automatically covered merely because TLRDev contributed to their development.

Separate organizations remain responsible for accessibility obligations applicable to their own products and services unless otherwise established by agreement or law.

4. Accessibility Standards and Guidelines

TLRDev uses recognized accessibility principles and technical guidance when evaluating accessibility improvements.

For websites and web applications, the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, serve as a general accessibility objective.

For native mobile applications, desktop software, and other digital technologies, relevant WCAG principles and applicable platform accessibility guidance may inform development decisions.

These standards and resources include:

  • Web Content Accessibility Guidelines (WCAG).

  • W3C Web Accessibility Initiative (WAI) resources.

  • Applicable mobile accessibility guidance.

  • Relevant operating system accessibility recommendations.

  • Other technical standards applicable to specific products.

References to these standards describe development objectives and evaluation criteria.

They do not constitute a representation that every Covered Project fully conforms to every accessibility requirement.

Actual accessibility support may vary by product, version, technology, and platform.

5. Accessibility Design Principles

TLRDev recognizes four fundamental accessibility principles:

Perceivable

Information and interface components should be presented in ways that users can perceive.

Examples include readable text, meaningful image descriptions, appropriate visual contrast, and alternatives for certain nontext content.

Operable

Interfaces should support practical methods of navigation and interaction.

Depending on the product, these may include keyboard operation, assistive technology compatibility, accessible controls, and appropriate interaction methods.

Understandable

Information and interface behavior should be reasonably clear and predictable.

Examples include understandable instructions, consistent navigation, descriptive labels, and useful error messages.

Robust

Digital content should be developed with consideration for compatibility across appropriate technologies, including assistive technologies.

Implementation methods will vary according to the capabilities and requirements of individual products.

6. Website Accessibility

For websites and web applications under its control, TLRDev seeks to consider accessibility features such as:

  • Logical heading structures.

  • Keyboard navigation.

  • Visible focus indicators.

  • Appropriate color contrast.

  • Readable typography.

  • Responsive layouts.

  • Descriptive links.

  • Accessible form labels.

  • Meaningful alternative text.

  • Understandable error messages.

  • Appropriate semantic markup.

  • Compatibility with commonly used assistive technologies.

These considerations may be incorporated during initial development, maintenance, redesigns, and accessibility improvements.

Some existing pages or features may require additional work.

7. Mobile Application Accessibility

TLRDev recognizes the importance of accessibility in mobile applications.

Depending on the application and its underlying framework, accessibility considerations may include:

  • Screen reader support.

  • Compatibility with Android TalkBack and Apple VoiceOver.

  • Descriptive interface controls.

  • Appropriate touch target sizes.

  • Support for operating system text scaling.

  • Adequate color contrast.

  • Clear navigation and instructions.

  • Alternatives to interactions that rely exclusively on color.

  • Compatibility with applicable device accessibility settings.

Some mobile application interfaces may have limitations caused by the underlying framework, device capabilities, third party components, or product design.

Accessibility support may vary between platforms and application versions.

8. Desktop Software Accessibility

Desktop software developed by TLRDev may incorporate accessibility considerations appropriate to the operating system and application technology.

These may include:

  • Keyboard navigation and shortcuts.

  • Logical focus order.

  • Accessible interface controls.

  • Appropriate text and contrast settings.

  • Compatibility with operating system accessibility features.

  • Clear labels and instructions.

  • Support for practical alternative interaction methods.

Certain advanced tools or specialized interfaces may require additional accessibility improvements.

9. Game Accessibility

TLRDev recognizes that accessibility in video games involves considerations that may differ from those of traditional websites and productivity applications.

Where appropriate and technically practical, game accessibility considerations may include:

  • Adjustable audio and visual settings.

  • Readable interface text.

  • Adjustable control sensitivity.

  • Alternative input methods.

  • Color distinction beyond color alone.

  • Clearly communicated objectives.

  • Accessible menu navigation.

  • Subtitles or captions where supported.

  • Customizable controls where available.

  • Other features appropriate to the game.

Real time gameplay, complex visual interactions, multiplayer mechanics, and specialized controls may create accessibility challenges.

Not every game or gameplay mechanic will be fully accessible to every user.

Game specific accessibility features and limitations may be documented separately when appropriate.

10. Digital Documents and Media

Where TLRDev publishes digital documents, videos, audio, or other multimedia content, accessibility considerations may include:

  • Readable document structures.

  • Appropriate heading organization.

  • Descriptive document titles.

  • Text alternatives for meaningful visual content.

  • Captions or transcripts where applicable and practical.

  • Accessible formatting.

  • Compatibility with commonly used document readers.

The availability of accessibility features may vary depending on the content, format, and delivery platform.

11. Third Party Services and Components

Covered Projects may use or integrate independently developed technologies, including:

  • Application store services.

  • Payment processing systems.

  • Authentication providers.

  • Advertising networks.

  • Analytics platforms.

  • Embedded media.

  • External APIs.

  • Software libraries and frameworks.

  • Other independent services.

TLRDev does not control every accessibility feature or limitation associated with these technologies.

Certain accessibility barriers may originate from third party services or components.

Where reasonably possible, TLRDev may evaluate alternative approaches or communicate accessibility concerns to relevant providers.

Independent third parties remain responsible for accessibility matters within their own control.

12. Known and Potential Accessibility Limitations

Despite accessibility efforts, some Covered Projects may contain barriers or features that do not function equally well for all users.

Potential limitations may include:

  • Legacy software components.

  • Older application interfaces.

  • Complex interactive elements.

  • Third party integrations.

  • Certain multimedia content.

  • Specialized game controls.

  • Device specific compatibility issues.

  • Limited support for some assistive technologies.

  • Features still undergoing development.

This statement does not represent a certification of complete accessibility conformity.

TLRDev encourages users to report accessibility problems so they can be reviewed and prioritized.

13. Accessibility Testing and Evaluation

Accessibility concerns may be identified through:

  • Development reviews.

  • Automated accessibility testing.

  • Manual interface testing.

  • Keyboard navigation checks.

  • Compatibility testing.

  • User feedback.

  • Product updates and maintenance.

  • Other appropriate evaluation methods.

The testing methods used may differ by product and available resources.

Automated tools alone cannot establish complete accessibility conformity.

Where formal accessibility assessments are conducted, results may inform future improvements.

14. Accessibility Feedback and Assistance

TLRDev welcomes feedback concerning accessibility barriers affecting Covered Projects.

If you experience difficulty accessing or using a website, application, game, digital document, or other Covered Project, please contact us.

Accessibility Contact: support@tlrdev.com

To help identify the issue, you may provide:

  1. The name of the affected website, application, game, or product.

  2. The website address or application version, if available.

  3. A description of the accessibility problem.

  4. The device and operating system being used.

  5. The browser or assistive technology involved, if relevant.

  6. The feature or information you were attempting to access.

You are not required to disclose a medical diagnosis or sensitive health information to report an accessibility concern.

15. Alternative Access and Communication

When a user cannot access information or complete a necessary interaction because of an accessibility barrier, TLRDev will make reasonable efforts to evaluate the issue and identify an appropriate alternative when feasible.

Depending on the circumstances, assistance may include:

  • Providing information through email.

  • Explaining alternative navigation methods.

  • Supplying information in another available format.

  • Identifying a workaround.

  • Evaluating a correction for a future update.

  • Referring the issue to the appropriate product support channel.

The availability of alternatives depends on the product, technical limitations, and applicable requirements.

16. Reporting and Resolution

Accessibility reports will be reviewed based on available information.

When evaluating a reported issue, relevant considerations may include:

  • The severity of the barrier.

  • The affected functionality.

  • The impact on users.

  • Applicable legal requirements.

  • Technical feasibility.

  • Available alternatives.

  • The scope of required development.

  • Relevant product maintenance schedules.

TLRDev may prioritize issues that substantially prevent users from accessing important information or functionality.

No specific resolution timeframe is guaranteed by this statement unless required by applicable law or an express agreement.

17. Accessibility of Future Projects

TLRDev intends to consider accessibility requirements and inclusive design principles when planning and developing future Covered Projects.

The technologies, intended audiences, capabilities, and accessibility needs of different products may vary.

Accessibility objectives may be evaluated during design, development, testing, and subsequent updates.

This statement does not guarantee that all future products will provide identical accessibility features.

18. Product Specific Accessibility Information

Individual Covered Projects may maintain additional accessibility information, documentation, or statements.

Such documentation may describe:

  • Supported assistive technologies.

  • Available accessibility settings.

  • Known product limitations.

  • Accessibility features.

  • Alternative access methods.

  • Product specific support procedures.

Where product specific accessibility information exists, it should be reviewed alongside this master statement.

19. Legal Compliance

TLRDev recognizes that accessibility requirements may arise under applicable laws and regulations, including the Americans with Disabilities Act and other relevant accessibility laws.

The applicability of particular requirements depends on the nature of the product, service, organization, and jurisdiction.

Nothing in this statement limits rights or obligations established by applicable law.

This statement is intended to communicate accessibility objectives, available assistance, and procedures for reporting barriers.

20. Continuous Improvement

TLRDev recognizes that accessibility is not a one time development task.

New technologies, software updates, evolving design practices, and changes in accessibility standards may introduce new opportunities or challenges.

Accessibility improvements may be incorporated into future development and maintenance activities.

Feedback from individuals with disabilities and users of assistive technologies is welcomed.

21. Policy Application Across Projects

This statement is intended to serve as the general accessibility statement for Covered Projects operated or controlled by TLRDev.

Covered Projects may reference this statement from their websites, application settings, help sections, legal information pages, or other appropriate locations.

Separate product accessibility statements may supplement this document.

This master statement does not replace product specific disclosures or compliance measures where they are independently required.

22. Changes to This Statement

TLRDev may update this Accessibility Statement to reflect changes in:

  • Accessibility standards.

  • Software development practices.

  • Available technologies.

  • Product functionality.

  • Applicable legal requirements.

  • Accessibility procedures.

The current version will remain available at:

https://tlrdev.com/accessibility/

The effective date will be updated when revisions are published.

23. Contact Information

For accessibility questions, assistance, feedback, or reports involving Covered Projects:

TLRDev
Arkansas, United States
Email: support@tlrdev.com
Website: https://tlrdev.com
Contact Form: https://tlrdev.com/contact/

Please identify the relevant product or service when submitting an accessibility request.