Keyboard access
Primary navigation, buttons, forms and documentation controls should be reachable without a mouse.
Accessibility
Build interfaces people can operate, read and understand.
Accessibility is treated as an ongoing product and website quality requirement. This statement explains the current approach and how to report a problem without claiming certification that has not been independently verified.
Our approach
Accessibility principles
The website and browser documentation should be usable with keyboard navigation, readable contrast, semantic structure and reduced visual friction.
Readable structure
Pages use headings, landmarks, labels and descriptive links so content can be scanned and interpreted by assistive technology.
Contrast and focus
Interactive elements should retain visible focus and sufficient contrast against the dark interface.
Responsive layouts
Public pages should remain usable at narrow viewport sizes and with browser zoom.
Motion
Decorative animation should not be required to understand or operate the page.
Images
Meaningful images should have useful alternative text; decorative images should not add noise.
Transparency
Known limitations
Accessibility is an ongoing engineering requirement, not a one-time certification claim.
Current status: Social Browser does not claim conformance to a specific WCAG level unless that conformance has been independently verified. If you encounter a keyboard, contrast, labeling or screen-reader problem, report the exact page and interaction to Support Center.
Feedback
Report an accessibility issue
Include the page URL, browser version, assistive technology if applicable, expected behavior and what actually happened.