Our Accessibility Goal

We want CostToCollege to be usable by as many visitors as possible, including people who use assistive technologies, keyboard navigation, screen readers, magnification tools, or alternative browsing methods.

Our goal is to present college cost information in a structure that is readable, predictable, and easy to navigate. Because the site includes data tables, calculators, filters, and comparison features, we continue to review the experience for clarity and accessibility.

Measures We Aim to Support

• Readable text with clear contrast between foreground and background colors.
• Logical heading structure without relying only on visual styling.
• Keyboard-friendly navigation where practical.
• Descriptive labels for form fields, filters, and calculator inputs.
• Responsive layouts for desktop, tablet, and mobile screens.
• Plain-language explanations for cost, tuition, net price, value, and related education metrics.

Known Limitations

Some parts of CostToCollege may include large tables, third-party browser behavior, embedded scripts, or data-heavy layouts that can be challenging for certain assistive technologies. We aim to improve these areas over time as the site grows.

College data can also be complex. When possible, we try to explain terms such as total cost, net price, graduation rate, median earnings, student debt, and admission rate in a practical way.

Ongoing Improvements

Accessibility is an ongoing effort rather than a one-time task. We may update page structure, table formatting, form labels, color contrast, and mobile layouts to make the site easier to use.

We also try to avoid unnecessary design effects that make reading or navigation harder. The main purpose of CostToCollege is to help users understand college affordability, not to create a distracting browsing experience.

Feedback

If you experience difficulty using any part of CostToCollege, you may reach us through the contact information provided on our Contact page. When sending accessibility feedback, please describe the page, the issue, the device or browser used, and the assistive technology involved if applicable.