Accessibility
Built to be usable by everyone
Last updated: July 25, 2026
Conferences.Center is designed and tested against WCAG 2.1 Level AA as an engineering target. This statement is not an independent audit or certification. Accessibility is ongoing, and reported barriers are handled as product defects.
What we do
The practices below are part of how we design, build, and test the platform.
Keyboard navigation
Release checks exercise critical workflows with keyboard input, logical tab order, and visible focus states.
Screen-reader support
We use semantic HTML, meaningful labels, ARIA where appropriate, and descriptive alternative text, then scan critical routes for violations.
Semantic landmarks
Pages use proper landmarks and heading structure (header, nav, main, contentinfo) so users can orient and navigate quickly.
Focus management
Dialogs and menus are tested for focus entry, containment, and return. We treat a reported focus loss as a product defect.
Automated testing
We run axe scans across public and authenticated critical routes as a release gate. Automated testing does not replace assistive-technology review.
Color and contrast
Our design tokens target WCAG AA contrast, and we adjust colors used as text to meet contrast requirements.
Report an accessibility barrier
If you encounter a barrier or something that is hard to use with assistive technology, we want to fix it. Please tell us the page or feature, what you expected, what happened, and the browser and assistive technology you were using.
accessibility@conferences.centerRelated: Trust Center · Security · Privacy
Frequently asked questions
Which accessibility standard do you follow?
We use the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA as our engineering target. Conferences.Center has not received an independent accessibility certification.
How do you test for accessibility?
We run axe scans in development and release validation and review keyboard behavior on critical workflows. Automated testing complements, but does not replace, manual assistive-technology testing.
How do I report an accessibility barrier?
Email accessibility@conferences.center with the page or feature involved, what you expected, what happened, and the assistive technology or browser you were using. We will work with you to resolve it.