Accessibility Statement
Last updated: June 5, 2026
Operator:Tribal House LLC, a limited liability company registered in Ghana (“Tribal House”, “we”, “us”). Accessibility questions or feedback: hello@portbay.app.
Scope
This statement covers two products operated by Tribal House LLC:
- portbay.app — this marketing website and checkout flow.
- PortBay desktop app — the macOS local development environment available at github.com/portbay-app/portbay.
Conformance status
We aim for conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. The portbay.app website is partially conformant: most of the site meets WCAG 2.1 Level AA, but some areas described under “Known limitations” below do not yet fully conform. The PortBay desktop app is partially conformant with WCAG 2.1 Level A in its current release; we are actively remediating.
Measures we have taken
- Semantic HTML. We use correct heading hierarchy, landmark regions (
<main>,<nav>,<footer>), and descriptive link text throughout the site. - Keyboard-accessible controls. Interactive elements (buttons, links, form fields) are reachable and operable with a keyboard. A skip-to-content link appears at the top of every page for keyboard users.
- Visible focus indicators. All focusable elements display a visible focus ring (violet outline, 2 px) when navigated to by keyboard.
- Reduced-motion support. CSS animations and Framer Motion transitions respect the OS
prefers-reduced-motion: reducesetting. Animations are disabled or reduced to simple fades under this preference. - No autoplaying media. The site contains no autoplay video or audio.
- Self-hosted fonts. The Inter typeface is served from our own infrastructure; no external font CDN tracking occurs.
- Colour contrast. Primary text on the dark background meets the WCAG 4.5:1 minimum contrast ratio for normal text.
Known limitations
We are aware of the following areas that do not yet fully meet WCAG 2.1 Level AA. We are actively working to resolve them:
- Data grids in the desktop app. The in-app project table and database client grids have incomplete keyboard navigation and screen-reader labelling. Remediation is in progress.
- Integrated terminal. The embedded terminal (xterm.js) provides limited screen-reader feedback. This is a known upstream limitation; we track improvements in the xterm.js project.
- Complex modal flows. Some multi-step modal dialogs in the app do not yet fully manage focus or announce state changes to assistive technologies.
Feedback and contact
We welcome feedback on the accessibility of PortBay. If you experience a barrier not listed here, or if a page or feature is not accessible to you, please contact us:
- Email: hello@portbay.app
- GitHub issues: github.com/portbay-app/portbay/issues
We aim to respond to accessibility feedback within 5 business days.
Enforcement — EU users
PortBay is subject to the European Accessibility Act(Directive (EU) 2019/882) for users in the European Union. If you are not satisfied with our response to your accessibility feedback, you have the right to escalate your complaint to the national market-surveillance or enforcement authority in your EU member state. Contact details for national authorities are available from the European Commission’s market surveillance network.
Date of this statement
This accessibility statement was prepared on 5 June 2026 and will be reviewed at least annually. Last reviewed: June 2026.
