Accessibility

Current approach

Accessibility is part of publication QA

The site aims to support WCAG 2.2 Level AA practices where they apply. That goal is not a claim that every page or third-party integration has been formally certified. New pages are reviewed for keyboard use, heading order, labels, readable contrast, descriptive alternatives, and responsive layout.

Supported features

Navigation and content access

• A skip link moves keyboard users to the main content.
• Pages use semantic headings, landmarks, links, and form labels.
• Images that carry information should include descriptive alternative text.
• The layout adapts to smaller screens and browser zoom.
• Controls should expose a visible focus state and an accessible name.

Known limits

Third-party and historical material

Embedded booking, newsletter, video, analytics preference, and chat interfaces depend in part on third-party code. Some historical articles, complex visualizations, captions, or generated media may need further remediation. A barrier reported by a reader receives priority over a cosmetic improvement.

Feedback

Report a barrier or request another format

Email [email protected] with the page URL, the task you were trying to complete, and the browser or assistive technology involved. You can also call +1 647 493 0660.

When possible, SEOFrancisco will provide the same information in an accessible alternative format while the page is reviewed. The response may require coordination with a third-party service.