Accessibility Statement for TDNet Discover

This is an accessibility statement from TDNet.

Measures to Support Accessibility

TDNet takes the following measures to ensure accessibility of TDNet Discover:

  • Include accessibility throughout our internal policies.
  • Appoint an accessibility officer and/or ombudsperson.
  • Provide continual accessibility training for our staff.
  • Assign clear accessibility goals and responsibilities.
  • Employ formal accessibility quality assurance methods.
  • Accessibility bugs are prioritized alongside functional bugs.
  • All interactive components follow an internal accessibility checklist before deployment.
Conformance Status

All end-user-facing pages of TDNet Discover fully conform to WCAG 2.2 Level AAA.

Additional Accessibility Considerations
  1. Beyond standards: We aim to go beyond the minimum requirements by implementing key elements of WCAG 2.2 Level AAA, along with real-world best practices, to support a wider range of user needs.
  2. Accessibility built into our process: Accessibility is a core part of our design and development workflow, not an afterthought. From the start of each project, we focus on making features usable and inclusive for everyone.
  3. Consistent, predictable user experience: We ensure accessibility features work consistently across the platform—whether you're using a screen reader, keyboard, or other assistive tools—so interactions feel natural and intuitive.
  4. Tested for real-world use: We regularly test with screen readers, keyboard-only navigation, and simulated impairments to catch issues that automated tools may miss, helping us refine the experience for actual users.
  5. Ongoing audits and tools: Automated accessibility checks are integrated into our development process, and we conduct regular audits to ensure the platform continues to meet high accessibility standards.
  6. Full keyboard and screen reader access: All features are fully operable without a mouse or touchscreen. Keyboard and screen reader users can access all functionality without missing out on any features.
  7. Mobile-friendly accessibility: We support accessible interaction on mobile devices, ensuring all touch targets meet sizing guidelines and all content works smoothly with screen readers and gestures.
  8. Easy and logical navigation: The platform supports intuitive keyboard navigation, allowing users to move easily between elements, sections, and interactive components without losing context.
  9. Smart focus management: We carefully manage focus throughout the platform—especially in modals, overlays, and dynamic content—so users always know where they are and what to expect next.
  10. Skip links and headings: Pages include structured skip links and clear headings to help screen reader users jump directly to main content and important features.
  11. Live updates for assistive tech: Important changes—like form errors or confirmations—are announced in real time for screen reader users, so they stay in sync with what's happening on screen.
  12. Accessible third-party tools: We evaluate and improve third-party components (like calendars or widgets) to maintain accessibility across the full experience.
Feedback

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

Compatibility with browsers and assistive technology

TDNet Discover is designed to be compatible with the following assistive technologies:

  • Latest version of Chrome, Edge, or other Chromium-based browsers with NVDA or JAWS on Windows 10 and 11.
  • Latest version of Firefox with NVDA or JAWS on Windows 10 and 11.
  • Safari with VoiceOver on macOS (latest version).
  • Safari with VoiceOver on iOS (latest version of iPhone).
  • Chrome or Edge on Android with TalkBack (latest OS version).
  • ZoomText, screen magnifier tools, and high contrast mode on Windows 10 and 11 using Chrome or Edge.
  • Keyboard-only navigation on all major browsers (Chrome, Edge, Firefox, Safari) across desktop operating systems.

TDNet Discover is not compatible with:

  • Outdated desktop browsers (e.g. Chrome 98 when current is 113+).
  • All versions of Internet Explorer (no longer maintained or supported).
  • Older mobile OS versions (like Android < 7 or iOS < 11).
  • Abandoned or outdated assistive tools that may not follow modern accessibility APIs.
Technical Specifications

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

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

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

Limitations and Alternatives

Despite our best efforts to ensure accessibility of TDNet Discover, there are some known limitations. These fall into two categories: limitations within our platform, and limitations that might arise from user-generated content. Below is a description of each limitation, along with available solutions. Please contact us if you observe an issue not listed here.

Platform Limitations
  1. Some administrative sections of the platform are not yet fully accessible to screen reader or keyboard-only users. Accessibility improvements are actively underway. These areas are typically accessed by a small number of staff at each organization.
  2. If you need assistance or would like to request an accessible alternative, please contact us at support@tdnet.com.
User-Generated or External Limitations
  1. Custom content authored by administrators: Some content created via rich text editors, custom HTML, widgets, CSS, or JavaScript may not fully meet accessibility standards, depending on how it's implemented. These items may bypass automated accessibility checks. We provide guidance within the editing interface and encourage adherence to best practices. For help addressing specific issues, please contact us at support@tdnet.com.
  2. Embedded third-party content: Administrators can embed content from third-party sources (e.g., videos, maps, or surveys). While we can't control the accessibility of these external tools, we’re happy to help evaluate them and suggest alternatives where needed. Please reach out to support@tdnet.com for assistance.
  3. Custom theming and styles: Applying custom CSS can unintentionally affect accessibility—for example, by reducing contrast or hiding focus indicators. The base design system is built for accessibility, but overrides may introduce issues. If you notice problems, we can help identify and resolve them. Contact support@tdnet.com.
  4. Uploaded documents and files: Files uploaded to the platform (like PDFs, Word documents, or presentations) may not be accessible if not properly formatted. We recommend using accessible templates and authoring tools. If you encounter an inaccessible document, alternative formats can be provided on request by contacting support@tdnet.com.
Assessment Approach

TDNet assessed the accessibility of TDNet Discover by the following approaches:

  • Self-evaluation.
  • A structured internal accessibility assurance process is embedded throughout the design and development lifecycle. This includes manual and automated testing using tools like AxeCore and WAVE, screen reader + keyboard testing, impairment simulations, and hands-on review by a dedicated senior accessibility engineer.
Formal Complaints

We welcome accessibility-related feedback and are committed to resolving any issues promptly. If you encounter a problem, please contact us at support@tdnet.com. We aim to respond within 2 business days and, if necessary, provide a resolution or action plan within 10 business days. All issues are reviewed internally by staff with accessibility expertise, including senior accessibility personnel, to ensure a fair and timely resolution.

Formal Approval of This Accessibility Statement

This Accessibility Statement is approved by:

TDNet
Customer Support Team