Open source contribution · Astro · TypeScript · a11y · i18n
akitaonrails/
Official website and documentation for ai-memory, featuring internationalization (i18n), right-to-left (RTL) support, and strict compliance with W3C/WAI-ARIA accessibility standards.
- 3 merged PRs
- 4 commits to the project
- +78 lines added
- 9 GitHub stars
The project
ai-memory-web is the official portal and documentation hub for the ai-memory ecosystem. Built with Astro, TypeScript, and Tailwind CSS, the site serves developers worldwide with native multi-language support, including right-to-left (RTL) scripts like Hebrew.
As the public front of a key AI agent infrastructure project, the site demands a flawless experience across all screen sizes and strict adherence to accessibility standards for users relying on screen readers and keyboard navigation. The contributions below eliminated horizontal layout shifts, aligned tab controls with RTL reading order, and brought markup into full WAI-ARIA compliance.
Highlights
The PRs with the largest effect for people who rely on the project every day.
-
#1merged Sep 23, 2026
Zero horizontal overflow and background scroll lock on mobile navigation
Browsing the ai-memory site became rock-solid across all screen sizes and mobile phones, ensuring visitors never experience broken layout shifts or displaced navigation menus.
-
#3merged Sep 29, 2026
W3C ARIA conformance on text scroll effects and screen reader marquee
Ensures visitors using screen readers or assistive tech hear every phrase and value proposition clearly, with zero regression in visual appeal, animations, or responsiveness.
How each PR was made
-
One problem per PR
Each PR fixes a single thing with the smallest possible change. That keeps reviews simple, lowers the risk of side effects and lets one change be reverted without taking others with it.
-
The problem becomes a test
Fixes come with automated tests that cover the case that used to fail, so the problem cannot come back unnoticed.
-
The project's own bar
Formatting, static analysis and the full test suite run in the project's continuous integration, and a change only lands after the maintainer's review.
-
Written for the reviewer
Each PR description explains the problem, the change and how it was tested, so the maintainer can decide with confidence.
Every PR, in business terms
Click a PR to see the problem, what was done and the value delivered. The link at the end of each one leads to the full technical discussion on GitHub.
-
#3merged Sep 29, 2026 W3C ARIA conformance on text scroll effects and screen reader marquee Text scroll effects and the agent marquee placed ARIA labels forbidden by W3C specs on paragraphs and divs, risking that screen readers skip the text; the PR exposes the content in the accessibility tree while preserving visual design.
- The problem
- Sentences that illuminate on scroll and the marquee showing compatible AI agents used aria-label attributes directly on standard paragraphs and <div> tags, which violates W3C/WAI-ARIA specifications. Because many screen readers ignore such attributes on those roles and child words were marked aria-hidden, visually impaired visitors could have key headings and statements skipped entirely across six languages.
- What was done
- Removed the prohibited attributes, restored the words to the accessibility tree as plain readable text while preserving visual opacity animation, and embedded the marquee statement as a visually-hidden, screen-reader-accessible paragraph (sr-only). Verified with axe-core 4.10.2 across 22 pages and six languages, eliminating violations across the entire site.
- Value delivered
- Ensures visitors using screen readers or assistive tech hear every phrase and value proposition clearly, with zero regression in visual appeal, animations, or responsiveness.
-
#2merged Sep 24, 2026 Keyboard navigation for right-to-left tabs and valid semantic markup for metrics On right-to-left pages (Hebrew), keyboard arrow keys moved in the opposite direction of reading; the PR flips the arrows to match reading direction, adds Home/End keys, and refactors stats cards into valid semantic HTML.
- The problem
- In the Hebrew edition of the site (read right to left), pressing the right arrow on tabs moved in reverse relative to the reader's gaze. Furthermore, the GitHub stats list used definition-list markup forbidden by HTML specifications, triggering accessibility audit failures in axe and Lighthouse.
- What was done
- Tab keyboard navigation now dynamically checks computed reading direction (direction) before advancing, adds Home and End keys to jump to the first and last tabs, and refactors stats into a clean semantic list (<ul>) of links with preserved responsive layout and focus indicators.
- Value delivered
- Right-to-left readers and keyboard-only users get a natural, intuitive interface, while the site eliminates markup violations across accessibility and compliance audits.
-
#1merged Sep 23, 2026 Zero horizontal overflow and background scroll lock on mobile navigation On medium viewports (1024px to 1300px), animations caused the site to overflow horizontally; the PR clips container overflow, locks background scrolling with the mobile drawer open, and adds a clipboard fallback.
- The problem
- On mobile devices and medium desktop windows (between 1024px and 1300px), animated elements pushed beyond the viewport width, creating an unwanted horizontal scrollbar that broke visual alignment and touch browsing. In addition, opening the mobile navigation menu allowed touches to scroll the background page underneath, and restricted browser environments failed with unhandled errors when copying install commands.
- What was done
- Applied horizontal overflow clipping (overflow-x: clip) that preserves GSAP scroll triggers, locked background scrolling when the mobile dialog is open using native :has(dialog[open]), and implemented a reliable textarea fallback for clipboard copying. Tested across 11 viewport widths from 320px to 1920px.
- Value delivered
- Browsing the ai-memory site became rock-solid across all screen sizes and mobile phones, ensuring visitors never experience broken layout shifts or displaced navigation menus.
Figures updated on Oct 11, 2026.
The same care in your system
The habits behind these PRs carry over to backends that move money: reproduce the problem before fixing it, prove the fix with a test and keep sensitive data from leaking.