Accessibilty Policy

The Access Technology Trainers Forum is built and maintained by an access technology trainer, for access technology trainers. Accessibility is not an add-on or a compliance checkbox. It is foundational to how this site is designed, developed, and maintained.

Design Philosophy

Accessibility guides decisions at every level of this platform. Features are built deliberately, tested with assistive technology, and refined based on real use by blind and low-vision professionals.

Function and clarity take priority over visual effects, animation, or decorative design. Tools are created to be usable, predictable, and efficient with keyboards and screen readers.

Standards and Practices

The site aims to follow established accessibility best practices, including:

  • Keyboard-only navigation
  • Logical heading structure and page flow
  • Clear labels and instructions for forms
  • Consistent navigation and predictable interactions
  • Accessible color contrast and text sizing
  • Compatibility with common screen readers and browsers

Accessibility is evaluated continuously rather than treated as a one-time task.

Trainer Toolkit Accessibility

The Trainer Toolkit is designed with accessibility as a primary requirement. Forms, views, and workflows are structured to support screen reader efficiency, reduce cognitive load, and minimize unnecessary steps.

Because the toolkit is developed in-house, accessibility issues can be addressed directly without waiting on third-party vendors.

Forum and Community Features

The discussion forum, Discord integration, and training materials are selected and configured with accessibility in mind. When limitations exist due to third-party platforms, workarounds or alternatives are considered.

Members are encouraged to report accessibility barriers encountered in forum features, training materials, or site navigation.

Ongoing Improvement

Accessibility is iterative. As tools evolve and new features are added, accessibility is reassessed and refined.

Member feedback plays a critical role in identifying friction points and improving usability across different assistive technology setups.

Known Limitations

Some third-party tools or integrations may have accessibility limitations outside of our direct control. When these are identified, they are documented and addressed where possible.

Reporting Accessibility Issues

Members who encounter accessibility barriers are encouraged to report them through the forum or site contact process. Reports should include:

  • The page or tool involved
  • The assistive technology and browser in use
  • A brief description of the issue

Accessibility issues are treated as high-priority maintenance items.

Commitment

This forum exists to support blind and low-vision professionals. Accessibility is not optional, negotiable, or secondary. It is part of the forum’s purpose and identity.