Education tools should be easier to access.

Our Accessibility Commitment

RTI Scheduler aims to make its public education tools, resources, navigation, and supporting information usable by as broad a range of people as reasonably possible.

Accessibility is treated as an ongoing design and development responsibility rather than a one-time page or feature.

As the platform grows, accessibility considerations should continue to be incorporated into new pages, tools, workflows, and future authenticated functionality.

Accessibility Standards and Guidance

RTI Scheduler may use recognized web accessibility principles and guidance as references when evaluating and improving website experiences.

These principles commonly address areas such as keyboard accessibility, semantic structure, text alternatives, readable contrast, understandable labels, focus behavior, responsive presentation, and compatibility with assistive technology.

Page Structure and Interface Design

RTI Scheduler aims to organize pages so users can identify important content and actions without unnecessary complexity.

Design considerations can include:

• descriptive page headings;
• logical heading hierarchy;
• clear sections and content grouping;
• recognizable buttons and controls;
• consistent spacing and visual hierarchy;
• meaningful labels;
• responsive layouts; and
• avoiding unnecessary interface clutter.

Visual presentation should support understanding rather than become the only way important meaning is communicated.

Keyboard Navigation and Focus

Important interactive controls should be designed so that users who navigate with a keyboard can identify and operate them where the underlying technology permits.

Relevant considerations include:

• logical focus order;
• visible keyboard focus indicators;
• buttons that can be activated through standard controls;
• avoiding unnecessary keyboard traps;
• accessible form navigation; and
• reasonable navigation through interactive tool interfaces.

Visual Accessibility

RTI Scheduler aims to use readable typography, spacing, interface states, and color combinations that support clear visual interpretation.

Color

Important information should not rely unnecessarily on color alone. Text, labels, icons, positioning, or other cues can provide additional meaning.

Text and spacing

Pages are designed with responsive text sizes, spacing, and content widths intended to support comfortable reading across common screen sizes.

Focus visibility

Interactive controls should provide a visible state where practical so users can understand which element is active.

Clear Content and Understandable Language

Accessibility also includes cognitive usability. Instructions that are technically available but difficult to understand can still create a barrier.

RTI Scheduler therefore aims to:

• use descriptive headings;
• keep tool instructions task-focused;
• label inputs according to their purpose;
• explain important assumptions;
• show understandable results;
• provide useful error information; and
• avoid unnecessary technical language where simpler wording works.

Forms, Inputs, and Error Messages

Education tools frequently depend on forms and numeric inputs, making form accessibility especially important.

Where practical, form design should provide:

• clear labels;
• understandable input expectations;
• reasonable keyboard operation;
• visible focus states;
• validation that explains what needs correction;
• results associated clearly with the action performed; and
• reset or correction options where useful.

Placeholder text alone should not be relied upon when a persistent label is necessary to understand an input.

Accessibility of Education Tools

RTI Scheduler includes interactive tools rather than only static reading content. That creates additional accessibility considerations around inputs, controls, timers, dynamically generated results, and changing interface states.

Motion, Animation, and Interaction

Motion can improve visual feedback but may create difficulty for some users when it is excessive or unnecessary.

RTI Scheduler should avoid making essential functionality depend on decorative animation.

Where practical, interfaces should respect reduced-motion preferences and keep important interactions understandable even when animations are reduced.

Responsive Design, Zoom, and Different Devices

RTI Scheduler pages are intended to adapt across common desktop, tablet, and mobile screen sizes.

Responsive design can help users who require larger text, narrower layouts, touch interaction, or different viewing environments.

Users may also use browser zoom or operating-system display settings. Interfaces should be reviewed over time to reduce unnecessary loss of functionality when content is enlarged.

Assistive Technology Compatibility

Users may access websites through screen readers, keyboard navigation, magnification software, speech input, browser accessibility features, or other assistive technologies.

Semantic HTML, meaningful labels, native controls, sensible heading structure, and accessible interaction patterns can improve compatibility with these technologies.

Third-Party Content and Technology

RTI Scheduler may use or link to technologies, plugins, embedded resources, hosting services, or external websites that are operated by third parties.

Accessibility of an external service can depend on that provider's design and implementation and may be outside RTI Scheduler's direct control.

Where a third-party component creates a significant barrier, RTI Scheduler can evaluate whether an alternative implementation is reasonably available.

Known and Potential Accessibility Limitations

RTI Scheduler is an evolving platform. Some current or future components may require additional accessibility testing or improvement.

Potential areas requiring continued review can include:

• complex interactive calculators;
• dynamically updated results;
• timers and time-sensitive interfaces;
• custom controls;
• third-party plugins;
• embedded content;
• older pages created before newer accessibility improvements; and
• future authenticated dashboard functionality.

Identifying a potential limitation here does not mean every instance is inaccessible; it identifies areas that deserve continued attention as the platform develops.

Testing and Continuous Improvement

Accessibility should be reviewed throughout development rather than only after a website is considered finished.

Appropriate review can include combinations of:

• keyboard-only navigation checks;
• responsive layout testing;
• heading and document-structure review;
• form-label and validation review;
• focus-state checks;
• color and contrast review;
• zoom and text-enlargement checks;
• automated accessibility testing tools; and
• manual testing of important user workflows.

Reporting an Accessibility Barrier

If you encounter an accessibility problem on RTI Scheduler, useful feedback can help identify the exact barrier and improve the affected experience.

When reporting an accessibility issue, it is helpful to include:

• the page or tool where the problem occurred;
• the action you were trying to complete;
• what prevented or complicated the task;
• your browser or device if relevant;
• the assistive technology involved, if you choose to share it; and
• the result you expected.

Accessibility questions or reports can be directed through the RTI Scheduler Contact Us page once its message-delivery system is operational.

Updates to This Accessibility Page

This page may be updated as RTI Scheduler's design, accessibility practices, technology stack, tools, testing processes, or available functionality change.

The "Last Updated" date should be revised when meaningful changes are made.

Future account systems, dashboards, advanced scheduling interfaces, or other major product additions should receive their own accessibility review as part of development.