Accessibility
Built to be usable by everyone
Conferences.Center is committed to meeting the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. Conferences should be open to every attendee, reviewer, and organizer — and so should the software that runs them. Accessibility is an ongoing commitment, and we keep improving as the product grows.
What we do
The practices below are part of how we design, build, and test the platform.
Keyboard navigation
Interactive elements are reachable and operable with a keyboard alone, with a logical tab order and visible focus states.
Screen-reader support
We use meaningful labels, ARIA where appropriate, and descriptive alt text so assistive technologies can convey the interface.
Semantic landmarks
Pages use proper landmarks and heading structure (header, nav, main, contentinfo) so users can orient and navigate quickly.
Focus management
Focus is managed thoughtfully around menus, dialogs, and route changes so keyboard and screen-reader users are never lost.
Automated testing
We run automated accessibility scans with axe as part of our workflow and remediate the issues they surface.
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 target the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across the Conferences.Center web application. Accessibility is an ongoing effort, and we continue to improve as we ship new features.
How do you test for accessibility?
We run automated accessibility scans using axe as part of our development and CI workflow, and we remediate the violations they report. Automated testing complements, but does not fully replace, manual review.
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.