Accessibility

MyProtocol is committed to improving digital accessibility for people of all abilities. We continuously work to improve the user experience and align our product decisions with recognized accessibility best practices.

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, including visual, auditory, motor, and cognitive impairments.

Conformance is an ongoing effort, and some areas of the Platform may not yet fully meet these standards at all times.

We have implemented the following features to support accessibility:

• Keyboard navigation. Interactive elements are intended to be accessible and operable using a keyboard.
• Semantic HTML. Proper heading hierarchy, landmarks, and ARIA labels to support screen readers.
• Color contrast. Text and interactive elements are designed to support readable contrast in line with WCAG guidance.
• Responsive design. The Platform adapts to different screen sizes, zoom levels, and orientations.
• Focus indicators. Visible focus styles for keyboard users navigating the interface.
• Alt text. Descriptive alternative text for meaningful images.

While we strive for full accessibility, some areas may still be in progress. User-generated content (such as protocol descriptions and forum posts) may not always meet accessibility standards, as we do not control the content contributed by our community.

We are actively working to address any gaps and welcome feedback from our users.

MyProtocol is developed and tested with common assistive technologies, including:

• Screen readers (NVDA, JAWS, VoiceOver).
• Screen magnification software.
• Speech recognition software.
• Browser zoom and text resizing.

We welcome your feedback on the accessibility of MyProtocol. If you encounter accessibility barriers or have suggestions for improvement, please let us know through the contact page.

We review accessibility feedback and prioritize remediation based on severity, user impact, and implementation complexity. Response and resolution timelines may vary.