Accessibility statement

We want everyone to be able to read and use aibio.space, including people who use a screen reader, a keyboard instead of a mouse, screen magnification, voice control or a reduced-motion setting.

Our target

We build aibio.space to the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. That level includes every Level A and AA requirement of WCAG 2.0 and 2.1. We consider the site partially conformant. The pages we tested passed the checks listed below, but we have not yet done every test that a claim of full conformance needs, and the items under known limitations do not fully meet the target.

What we tested and how

We last tested on October 25, 2026. The tests covered the front page, news stories, the section pages, company desks and desk views, company profile pages, the company directory, the membership, privacy, terms and accessibility pages, and the forms. We tested on a desktop screen (1360 by 900 pixels) and on a phone-sized screen (iPhone 13), both as a visitor and as a subscriber, and with the subscribe form and the menu open. The site is built from a small set of page templates, so these pages stand for the rest of the site, but we have not checked each of its thousands of pages one by one.

• Automated checks with axe-core 4.14, using its rules for WCAG 2.0, 2.1 and 2.2 at Levels A and AA.
• A keyboard-only pass through each page, forward with Tab and back with Shift+Tab. We checked the skip link, the order of the stops, a visible focus outline on every link and control, that nothing with focus is hidden behind the fixed header or the desk menu, that focus never gets stuck, and that Escape closes the menu and the subscribe form and returns focus to the button that opened them.
• Color contrast of text, buttons, ticker chips, the green and red share lists on the front page and the focus outline.
• Pages at 320 pixels wide, which is what a 1280-pixel screen shows at 400% zoom, with no sideways scrolling of the page, and with the wider line, letter, word and paragraph spacing of the WCAG text-spacing test.
• Target sizes of links and buttons, form labels and error messages, headings, landmarks, page titles, the page language, link text, text alternatives for images and titles for embedded frames.
• The site with the reduced-motion setting turned on.

We have not yet tested with screen readers such as NVDA, JAWS, VoiceOver and TalkBack, or with people who have disabilities. We will publish the date of that review here. The automated and keyboard checks are scripted, so we run them again before releases.

Moving content

The headline strip in the page header and the green and red lists of shares on the front page move on their own. Each has a small pause button: the strip's button is at its left end, and one button in the top right corner of the two share lists stops both. The site remembers your choice in this browser. The strip and the share lists also stop while one of their links has keyboard focus, and on a computer while the pointer is over them. On a touch screen, the share lists stop for 10 seconds after you touch them. The photographs at the top of company desks change every few seconds and have their own Pause button. If your device is set to reduce motion, nothing moves and the pause buttons are not shown.

Known limitations

• The stock chart on company pages comes from TradingView and loads only if you choose to show it. We give the chart frame a title, but we do not control what is inside it, and it may not meet WCAG. A text link under the chart opens the same symbol on TradingView's own site, and nothing else on the page depends on the chart.
• Data tables, such as the pipeline tables on company desks, scroll sideways on narrow screens. You can scroll a table with the arrow keys after moving focus to it.
• On phones, the front page shows the two lead stories above the Top news list. The keyboard and screen reader order follows the desktop layout, where the Top news list comes first.

No overlay

We do not use an accessibility overlay or widget. We fix problems in the pages themselves.

Tell us about a barrier

If something on aibio.space does not work for you, email contact@aibio.space. Tell us the page address, what you were trying to do and, if you like, the browser and any assistive technology you use. We aim to reply within 5 business days. If a page does not work for you, we can also email you its text.