Product practice
Accessibility belongs in the product system
As the public site becomes richer, the same standards need to apply to navigation, forms, product mocks, documentation links, and account flows.
Keyboard access
Interactive controls should remain reachable and usable without a mouse.
Readable content
Pages should use semantic structure, clear headings, and contrast that supports readable product information.
Clear interactions
Buttons, links, forms, and navigation should be understandable before a user commits an action.
What we do
Practical checks for public and product pages
Accessibility is not only a checklist item. It makes the product easier to understand, easier to evaluate, and easier to operate for teams with different working environments.
Use semantic HTML so pages are easier to navigate with assistive technologies.
Keep form fields, buttons, and links labeled with meaningful text.
Avoid relying on color alone to communicate important state.
Check responsive layouts so content remains readable on smaller screens.
Treat accessibility feedback as product feedback, not as an afterthought.
Tell us where the experience breaks
Include the page URL, browser or device, assistive technology if relevant, and what you were trying to accomplish.