Waking up your workspace
Accessibility means people who use a keyboard, a screen reader, bigger text or reduced motion can use PostHub just like anyone else. Here is what that looks like in the product today — in plain language, gaps included.
About one in four adults lives with a disability — temporary (a broken wrist), situational (holding a baby, bright sunlight) or permanent (blindness, motor impairment). An accessible product simply does not lock anyone out: you can operate it without a mouse, read it with a screen reader, understand it without relying on colour alone, and turn down the motion when your device asks for calm. It is the same product — just less stubborn about how you reach it.
Each bar is labelled in words — Strong, In progress, or Not yet. The width is a picture of where we are, not a measured percentage.
Every action reachable with the keyboard alone.
A clear focus ring on every interactive element.
Real header/nav/main/footer with one h1 per page.
Dense tables and charts are not fully tested yet.
Reasoned per surface, not measured on every screen.
Tooling is installed, but not wired into the pipeline.
Open any row to see exactly what we do, in plain language. The last one — known limitations — is the one we are proudest of keeping honest.
We follow the Web Content Accessibility Guidelines (WCAG) 2.1 at the AA level — the international standard for accessible websites. In plain terms that means content is perceivable (people can sense it), operable (people can drive it), understandable (it behaves predictably) and robust (it works with assistive tools).
What we will not do is claim a conformance level we have not tested with an auditor. This page describes the standard we build toward and the practices we ship today — not a badge.
Every action on the marketing pages and in the dashboard can be reached with the keyboard. Desktop menus open on focus as well as hover and close with Escape, the mobile menu is a real button that announces whether it is open or closed, and footer sections expand the same way. Interactive elements carry a visible focus ring — a two-pixel brand-coloured outline on links, buttons, form fields and menu items — so keyboard users always know exactly where they are. Focus is never removed without a replacement.
Pages are built from real landmarks — header, navigation, main, footer — with one h1 per page and headings in order, so the document outline makes sense without a single pixel of styling. Icon-only buttons carry spoken names like "Toggle menu" or "Close", disclosure controls announce whether they are expanded, and status is always spelled out in words — the status page says "Operational" or "Degraded", never a colour alone. Alt text for uploaded media depends on what the author writes; we cannot invent it for you, but decorative images are hidden from assistive technology.
Light and dark themes are built from the same colour tokens, with body text kept deliberately high-contrast in both. The type scale is consistent, body copy never drops below 14px, and text is never baked into images. Honest caveat: contrast has been reasoned about per surface rather than measured across every screen with an analyser — a full dark-mode contrast audit is still outstanding, and we would rather say that than pretend it is done.
Structure comes first. Pages use semantic HTML with landmarks (header, nav, main, footer), one h1 per page, and heading levels that never skip — so the page still reads in a sensible order on a screen reader, in reader mode, or when stylesheets fail to load. Forms have real labels tied to their fields, errors are announced, and animations across the site check the system reduced-motion preference before running — when your device asks for less motion, entrance animations and looping effects settle or stop instead of playing regardless.
Listing these is the point: a gap you know about is one you can plan around, and a gap we admit is one we can prioritise.
Email support@posthub.shorix.io and tell us which page, what you were trying to do, what you expected, and what happened instead — the browser and assistive technology you use help us reproduce it quickly. Every report gets a human reply, and accessibility problems that block someone from using the product are treated as bugs, not feedback.
Open a support ticket