Accessibility statement
Everyone belongs here — including members who use assistive technology. Here's where we stand and how to tell us when something's in your way.
Our commitment
Gays, Not Queers is built to be usable by every lesbian, gay man, and bisexual person who wants to be part of this community — including people who are blind or have low vision, who navigate by keyboard, who use screen readers or voice control, or who have cognitive, motor, or hearing disabilities. Accessibility isn't a feature we bolt on; a community site that some of our own people can't use isn't finished.
The standard we work toward
We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We haven't yet completed a formal third-party audit, so we describe the site as partially conformant: most content meets the standard, and we're actively working through what doesn't.
What we've built in
Measures already in place across the site include:
— Semantic HTML with a logical heading structure, so screen readers can navigate by landmarks and headings.
— Every form field has a visible, programmatically associated label, and required fields are marked.
— Interactive controls — the menu toggle, FAQ accordions, tabs, and buttons — are real buttons and links, operable by keyboard.
— Icon-only controls carry text alternatives for assistive technology.
— Text colors are chosen for contrast against their backgrounds, and information is never conveyed by color alone.
— The layout is responsive and supports browser zoom up to 200% without loss of content or function.
— Motion is minimal, and nothing on the site flashes, autoplays, or imposes time limits.
Known limitations
We're honest about what isn't perfect yet. Member-submitted content — blog posts and newsletter articles — is reviewed before publishing, but may occasionally lack image descriptions or use formatting that reads awkwardly with a screen reader; we fix these as we find them. Some decorative emoji icons may be announced by older screen readers. And some interactive features depend on JavaScript being enabled.
Tell us when something's in your way
If you hit a barrier anywhere on this site — a page you can't navigate, a form you can't complete, content you can't perceive — we genuinely want to know. Send us a note through the contact form (choose "Site feedback or correction") and describe what happened, what browser or assistive technology you were using, and the page it happened on. A real person reads every message, and we aim to respond within a few days and to fix confirmed barriers as a priority.
This statement was first published in July 2026 and is reviewed as the site evolves.