Accessibility

What we have done

• Semantic landmarks and a logical heading order on every page.
• A skip link to the main content as the first focusable element.
• Full keyboard operation, including the mobile menu, which traps focus while open, closes on Esc, and returns focus to the button that opened it.
• A visible focus outline on every interactive element. It is never removed.
• Interactive targets of at least 44 × 44 pixels.
• Colour contrast checked against the brand palette. The official Sympify purple (#806ABA) falls just below the AA threshold for normal-sized white text, so a darker purple (#60489D) is used wherever that combination appears.
• Accordions built on native <details> elements, so they work with screen readers and find-in-page and continue to work without JavaScript.
• Meaningful alternative text on photographs, and empty alt text on genuinely decorative images.
• Respect for prefers-reduced-motion: transitions collapse, and the impact counters render their final value immediately instead of animating.
• Text that reflows without horizontal scrolling down to a 320 pixel viewport.
• No information conveyed by colour alone.

What we know is not done

• This site has not yet been tested by people who use assistive technology daily. Automated checks and keyboard testing are not a substitute for that.
• It has not been tested end-to-end with JAWS, NVDA or VoiceOver.
• Several photographs still need alternative text written by someone who was present at the event and can describe it accurately.
• There is no video content yet. When there is, it will need captions and a transcript.
• This statement covers sympify.org only. The Sympify application at sympify.ai has not been audited to the same standard, and it should be.

Tell us about a barrier

If something here is difficult or impossible to use, we want to know — that is a bug, and we will treat it as one.

Email info@sympify.ai with "accessibility" in the subject line, or use the contact page. Tell us the page, what you were trying to do, and what got in the way — and, if you can, which browser and assistive technology you were using. You do not need to know why it is broken for us to fix it.