# Source handling

This modernization report remains a supporting UX and architecture reference. Assertions that imply completed production testing are not treated as evidence unless reproduced in the v2.9.2 evidence catalog.

---

# **VNWO.com v2.9.0 Architectural, UI/UX, and Accessibility Improvement Report**

## **The Civic Technology Paradox and the Architecture of Digital Trust**

The fundamental objective of civic technology platforms is to bridge the gap between complex governance architectures and the constituents—or in this case, system operators, developers, and users—they serve1. However, the sector suffers from a documented paradox: while the underlying goal is to increase accessibility and transparency, the actual digital interfaces deployed are frequently undermined by poor usability, dense bureaucratic formatting, and severe accessibility barriers. This operational reality directly erodes public trust2. When individuals cannot intuitively navigate a framework, parse its legal boundaries, or utilize its tools, they experience a "trust deficit" that makes the platform appear either incompetent or deliberately obfuscating2.  
To counter this, the v2.9.0 architectural overhaul of Virtual Networks Without Overreach (VNWO.com) fundamentally reconstructs the platform's User Interface (UI) and User Experience (UX). Grounded in the Unified Theory of Acceptance and Use of Technology (UTAUT) and the Technology Acceptance Model (TAM), the redesign prioritizes "Perceived Ease of Use" and "Performance Expectancy"2. The engineering mandate is to present VNWO.com as a clear, authoritative, and modern public framework for digital network boundaries. Crucially, this UI/UX transformation must simultaneously preserve the platform's strict claim-boundary discipline: VNWO is static public civic guidance. It does not certify safety, prove machine consciousness, grant legal personhood, execute intelligent agents, import external files, synchronize network memory, validate endpoint credentials, collect telemetry, guarantee regulatory compliance, or replace qualified legal advice4.  
This report details the exhaustive refactoring of the platform's WordPress architecture, front-end asset pipelines, navigation systems, component-driven layouts, machine-readable schemas, and accessibility matrices.

## **Server-Rendered Infrastructure and Framework Abstinence**

Modern web development frequently defaults to heavy client-side rendering architectures, utilizing Single Page Applications (SPAs) built on Angular, React, or Vue. Furthermore, aesthetic development is often outsourced to utility-first CSS frameworks like Tailwind or component libraries like Bootstrap. The v2.9.0 release explicitly rejects these dependencies.  
The incorporation of client-side frameworks introduces severe render-blocking vulnerabilities, necessitates large JavaScript payloads that penalize users on low-bandwidth connections, and obscures the semantic Document Object Model (DOM) from essential screen readers5. Furthermore, relying on third-party layout libraries introduces technical debt and compromises the long-term maintainability of a static civic guidance platform. Therefore, VNWO.com remains a strictly server-rendered, classic WordPress architecture relying solely on semantic HTML5, custom Cascading Style Sheets (CSS), and progressive enhancement via vanilla JavaScript4.

### **Classic WordPress Theme Engineering**

The system utilizes a bespoke theme situated at wp-content/themes/vnwo-theme/. The architecture leverages standard WordPress template hierarchy files, including header.php, footer.php, functions.php, front-page.php, index.php, and page.php4. By processing the document layout on the server, the application delivers fully formed HTML to the browser, ensuring immediate First Contentful Paint (FCP) and flawless indexing by search engines and artificial intelligence crawlers.  
The functions.php file manages core theme support, such as title tag generation and semantic HTML5 support, while simultaneously registering the primary and "More" navigation menus4. Instead of relying on complex, heavily nested custom Walker\_Nav\_Menu PHP classes—which frequently introduce deeply nested, inaccessible \<ul\> and \<li\> structures—the theme directly constructs semantic navigation blocks that align perfectly with Web Content Accessibility Guidelines (WCAG)6.

### **Vanilla JavaScript Engine and Progressive Enhancement**

All interactive elements across the platform—including dropdown menus, mobile drawers, progressive filtering, and clipboard functionality—are executed via a single, highly optimized vanilla JavaScript file (vnwo-navigation.js)4. The code completely eliminates the need for jQuery, a legacy library that introduces unnecessary parsing delays4.  
The vanilla implementation utilizes standard ECMAScript 6 (ES6) query selectors and event listeners. For instance, the template filtering mechanism deployed on the Open Rules and Machine-Readable Governance pages operates by querying data-filter attributes on trigger buttons and cross-referencing them against data-categories strings embedded in the target cards4. Using a simple .forEach() loop combined with string array .includes() logic, the script applies a .js-hidden class (which asserts display: none \!important) to non-matching elements4. Because this interactivity acts as a progressive enhancement layer, the failure or intentional blocking of JavaScript by a user agent simply results in all cards remaining fully visible, preserving total access to the civic governance guidance.

## **Accessible Navigation Engineering and Viewport Resiliency**

A primary UX deficiency identified in earlier iterations was navigational density; the primary interface attempted to surface too many governance routes simultaneously, overwhelming first-time visitors and risking vertical overflow on standard laptop screens10. The v2.9.0 architecture resolves this by implementing a dual-tier navigation system: a persistent top-level header for primary routes, and a rigorously engineered mega-menu for secondary pathways.

### **Mega-Menu DOM Construction and Keyboard Accessibility**

The persistent header limits visible links to the most critical paths: Start Here, Charter, Open Rules, File Memory, Exit Rights, Claim Boundaries, and Downloads. All peripheral routes—including specialized architectural guidance, implementation checklists, ecosystem mapping, and site policies—are consolidated within a "More" trigger4.  
Constructing an accessible mega-menu requires strict adherence to WAI-ARIA (Web Accessibility Initiative \- Accessible Rich Internet Applications) patterns10. Hover-only menus exclude users who rely on keyboard navigation or touch interfaces11. Therefore, the VNWO mega-menu operates exclusively via click, touch, or keyboard activation. The trigger button utilizes aria-expanded to communicate its current state to screen readers and aria-controls to programmatically link the trigger to the dropdown container4.  
Upon activation, the JavaScript engine toggles the aria-expanded state to true and injects an is-visible CSS class4. The script immediately intercepts focus management; when the menu opens via keyboard, focus shifts to the first internal link13. The container listens for ArrowDown and ArrowUp keystrokes, calculating an index array of all nested anchor tags to allow rapid, localized traversal without forcing the user to tab through the entire document sequence4. Crucially, an event listener is bound to the document to detect the Escape key; when triggered, the menu immediately collapses and returns programmatic focus back to the triggering button, preventing keyboard traps12.  
To prevent vertical overflow on shorter laptop viewports (e.g., 1366x768 and 1280x800), the dropdown container is constrained by a CSS max-height parameter combined with overflow-y: auto, ensuring the menu always scrolls internally rather than pushing content beyond the viewport4.

### **The Mobile Drawer and Viewport Matrix**

For viewports under 1024px, the horizontal navigation collapses into a dedicated mobile drawer4. Activated by a standard hamburger toggle (equipped with correct WAI-ARIA labels), the drawer slides in from the horizontal axis. When active, a no-scroll utility class applies overflow: hidden to the document body, preventing the frustrating dual-scroll phenomenon commonly found in poorly engineered mobile overlays4.  
The platform's fluid responsiveness was validated against a strict viewport Quality Assurance (QA) matrix, ensuring layout integrity across all targeted device dimensions.

| Viewport Target | Navigational State | Structural Layout Behavior |
| :---- | :---- | :---- |
| **1440x900** | Full horizontal \+ Mega-menu | Unconstrained multi-column grids (3-column role cards, 4-column footer). |
| **1366x768** | Full horizontal \+ Mega-menu | Internal vertical scrolling enabled on the mega-menu to prevent screen bottom clipping. |
| **1280x800** | Full horizontal \+ Mega-menu | Main content containers constrain line lengths to optimal 75-character reading maximums. |
| **1024x768** | Full horizontal \+ Mega-menu | Grid templates transition to 2-column structures; mega-menu width reduces to 600px. |
| **768x1024** | Mobile Drawer (Burger Toggle) | Sidebars flow underneath main content; split-page reading layouts collapse to single columns. |
| **390x844** | Mobile Drawer (Burger Toggle) | Footers transition to 1-column stacks; CTAs wrap cleanly. |
| **320x568** | Mobile Drawer (Burger Toggle) | Tables enable horizontal overflow-x; zero horizontal scrolling permitted on the \<body\>. |

## **Visual Language, Typography, and Focus Visibility**

The visual aesthetic of a civic technology platform must project calm, credible, and serious authority5. Gimmicks, heavy animations, and overly stylized graphics distract from the core legal and architectural guidance. The v2.9.0 release utilizes a highly controlled design token system deployed via CSS variables within the :root pseudo-class4.

### **Typography and Spatial Rhythm**

To guarantee rapid loading and prevent layout shifts, the theme completely abandons third-party web fonts, relying exclusively on a native system font stack (system-ui, \-apple-system, BlinkMacSystemFont, "Segoe UI", Roboto) for sans-serif components, and a corresponding system stack for monospace data blocks (ui-monospace, SFMono-Regular, Consolas)4. This approach ensures that text renders instantly using the operating system's highly optimized, native typography engines.  
A strict mathematical spacing scale, utilizing root em (rem) units ranging from \--space-1 (0.25rem) to \--space-16 (4rem), governs every margin, padding, and grid gap across the entire DOM4. This discipline prevents the disjointed layouts that often plague organically grown WordPress sites, enforcing a rigorous vertical and horizontal rhythm that guides the reader's eye predictably through complex documentation.

### **WCAG 2.2 AA Focus Indicators and Accessibility Standards**

A critical failure point in digital accessibility is the removal of default browser focus rings without providing a sufficient custom replacement14. Keyboard users rely entirely on these indicators to understand their current position within the DOM. The v2.9.0 update introduces a highly engineered focus indicator utilizing the modern :focus-visible pseudo-class15.  
The CSS applies a 3-pixel solid outline using a high-visibility accent color (--focus: \#0ea5e9), paired with a 3-pixel outline-offset4. The offset pushes the outline away from the interactive element, preventing it from blending into the element's border. This explicitly satisfies the WCAG 2.2 Success Criterion 2.4.11 (Focus Not Obscured) and 2.4.13 (Focus Appearance), which mandate that the focus indicator area must be at least as large as a 2 CSS pixel thick perimeter and possess a 3:1 contrast ratio against adjacent background colors14.  
Furthermore, a "skip link" is positioned as the first focusable element in the DOM structure. It remains visually hidden at \-100px on the Y-axis until a keyboard user initiates a Tab event, at which point it drops into the viewport, allowing screen readers and keyboard navigators to bypass the dense navigation header and jump directly to the \<main id="main-content"\> landmark4.  
For users with vestibular disorders, the CSS includes a robust @media (prefers-reduced-motion: reduce) query. When a user's operating system signals a preference for reduced motion, this directive globally forces all CSS transition-duration and animation-duration values to \-1ms and sets scroll-behavior: auto \!important, ensuring that menus open instantly and anchor links jump directly to their targets without inducing motion sickness4.

## **Component Modularity and the Reduction of Boilerplate**

Legal and civic documentation inherently requires repetitive disclaimers. In previous versions, the repetition of VNWO's core boundaries (stating that the site does not run code or certify safety) resulted in significant cognitive fatigue for readers. To solve this, the v2.9.0 architecture introduces a reusable "Claim Boundary Panel" component4.  
Instead of embedding these disclaimers as repetitive prose within the body of every article, the boundary panel is styled as an offset, dashed-border component. A dark-themed variant of this panel is permanently affixed above the global footer across every route4. This guarantees that no matter where a user, agent, or web crawler lands on the domain, the strict negative boundaries—prohibiting the system from validating credentials, running agents, or replacing legal advice—are universally enforced as structural elements rather than buried legal text.  
Similarly, to aid in the scannability of dense documentation, the design language introduces a status badge taxonomy. These small, rounded indicators utilize specific color pairings to convey the state of a document at a glance. For example, "Static Guidance" uses a slate background with dark text, while "No File Import" uses a high-contrast red alert styling. Every badge pairing has been mathematically tested to exceed the WCAG AA 3:1 minimum contrast requirement4.

## **Page-Level Structural Refactoring and User Journeys**

The transformation from a general content site to a structured civic framework required a total overhaul of the primary URL routes, utilizing specialized PHP templates to enforce rigid layouts18.

### **The Homepage: Role-Based Onboarding**

The front page serves as the orientation locus for the entire framework. The hero section eschews vague marketing terminology in favor of a declarative H1: "Virtual Networks Without Overreach." Beneath this, the subhead explicitly defines the platform's utility in plain language: "Public rules for networks people can inspect, repair, export, revoke, and leave."4.  
Directly beneath the hero, the "What VNWO is / What VNWO is not" split-card component grounds the user immediately. Following this, the interface deploys a massive role-based decision grid. This grid maps exact user personas to specific internal routes.

* "I run a community" directs to the Start Here orientation.  
* "I build AI agents" links to disclosure documentation.  
* "I manage memory or files" routes to the File Memory schema rules.  
* "I expose local endpoints" directs to the LocalEndpoint boundary guidelines.  
* "I review AI judgment" routes to the Repair and Appeals documentation.  
* "I need exit or repair rules" pushes the user directly to the Exit Rights page4.

By forcing the user to self-identify their role immediately, the framework drastically reduces the time required to locate relevant governance assets, ensuring a first-time visitor can orient themselves in under 60 seconds. Further down the page, a high-contrast visual band reinforces the core tripartite law of the system: Inspect the rules, Control memory, Leave4.

### **The "Start Here" Orientation**

The /start-here/ route functions as the true first-user ingestion point. It opens with a "60-second orientation" block designed to rapidly offload conceptual complexity. A critical addition is the "Glossary Strip," a distinct, lightly shaded component that defines key nomenclature—such as "virtual network", "open rules", "file memory", and "exit packet"—preventing users from misinterpreting foundational terms4. To support scanning, the page features a localized, sticky Table of Contents (TOC) placed within a dual-column layout on desktop viewports, allowing users to jump directly to specific subsections without excessive vertical scrolling4.

### **The Charter and Open Rules**

The /charter/ page acts as the foundational philosophical and legal text. While preserving the exact meaning of the original charter, the UI redesign injects an executive summary card prior to the articles. Each article is then formatted as an independent card containing the article number, title, plain-English rule, an implementation note, and a related route link. To facilitate offline reading and machine processing, a consistent Call to Action (CTA) row provides "Download Markdown," "Download PDF," and "Machine-readable equivalent" actions4.  
The /open-rules/ template operates as a functional template library. It utilizes the progressive-enhancement vanilla JavaScript filtering system described earlier. Users can filter templates by categories such as Charter, Disclosure, Memory, Endpoint, Repair, Exit, or Claim Boundary4. Each template card explicitly lists its purpose, when to use it, what it prevents, and the most common implementation mistake, ensuring developers utilize the templates correctly rather than treating them as blind boilerplate.

### **Machine-Readable Governance and Downloads**

The /machine-readable-governance/ route organizes the platform's dense schema assets. Recognizing that unformatted lists of JSON files are difficult to parse, the UI splits the artifacts into highly structured category groups: Core files, Architecture schemas, Metadata, Agent schemas, File memory, Endpoints, Exit rules, Claim boundaries, and AI judgment schemas. A vanilla JavaScript search input allows users to instantly filter the artifact matrix in real-time4.  
The /downloads/ page abandons the previous plain-text list in favor of distinct file cards. Each card clearly identifies the file name, format (e.g., Markdown, JSON, PDF), exact purpose, and the last-reviewed date in UTC. To reinforce the platform's privacy-first civic posture, the interface explicitly maintains a no-signup, no-upload, and zero-tracking-gate posture for all asset retrievals4. A "recommended starter pack" grouping allows rapid acquisition of the core schemas required for initial ecosystem integration.

### **Claim Boundaries and Accessibility Assertions**

The /claim-boundaries/ route is the canonical safety and copy-replacement authority. It features a responsive data table detailing "risky claims"4. For instance, if an agent developer attempts to write, "We certify this system is completely safe and aligned," the table flags this as a danger-row and provides the required "safer phrase" alternative: "This system operates on static public boundaries and inspectable rules; it does not issue safety certifications"4. Dedicated "copy" buttons, powered by the vanilla JS clipboard API, allow developers to safely extract the correct phrasing with a single click4.  
The /accessibility/ page transforms standard compliance boilerplate into a verifiable evidence log. It explicitly details the QA protocols executed, documenting the keyboard-only smoke tests, reduced-motion validation, contrast ratio checks, and mobile viewport performance. It rigorously avoids overclaiming compliance beyond what was physically tested, maintaining the system's overall trust posture.

## **Machine-Readable Parity and Generative Engine Optimization**

A hallmark of a modern civic-technology framework designed for multi-agent environments is the establishment of absolute parity between human-readable text and machine-readable assets. AI crawlers, autonomous agents, and compliance validators cannot reliably parse complex HTML DOM structures or infer intent from human-focused typography. Consequently, the v2.9.0 release architects a comprehensive layer of machine-readable governance files designed specifically for programmatic ingestion.

### **The llms.txt Standard**

As Artificial Intelligence (AI) agents increasingly perform web retrieval, traditional SEO mechanisms like robots.txt and XML sitemaps fail to provide contextual relevance. The release implements a highly optimized /llms.txt file at the root domain20.  
Adhering strictly to emerging AI-ingestion standards, the file begins with a single Markdown Header 1 (H1) identifying the framework, followed immediately by a blockquote that provides an agent-readable, third-person summary: *"Public static civic guidance establishing templates, principles, and rules for networks that respect human autonomy"*4.  
The document eschews marketing fluff, instead grouping canonical pages (Start Here, Charter, Open Rules) under logical H2 headings. Every link follows a strict Markdown syntax \-\[Title\](URL): Description, where the description provides a high-signal, one-sentence summary of the target page's utility for an AI agent. By supplying this structured file, VNWO ensures that AI agents indexing the site grasp the negative claim boundaries immediately, preventing hallucinations regarding the platform's authority to execute code or certify safety22.

### **JSON Schema Architecture**

To support algorithmic validation and automated compliance checks, human-readable pages are mirrored by strict JavaScript Object Notation (JSON) schemas4.

* **vnwo.json:** Serves as the root manifest. It defines the current version string (2.9.0) and features a mandatory claim\_boundary object. This object contains an array explicitly listing the platform's limitations (e.g., "does not execute agents", "does not sync memory", "does not authorize endpoints"). It also maps all primary human-readable URL routes to facilitate automated pathfinding4.  
* **open-rules.json:** A deeply structured object array representing the entire open rules template library. Each template object specifies its id, category, purpose, and when\_to\_use. By including fields for what\_it\_prevents and common\_mistake, the JSON ensures that automated systems evaluating network design understand the intended civic constraints of the template4.  
* **claim-boundaries.json:** Translates the risky claims table into programmable logic. The schema array explicitly pairs risky\_phrase strings with their mandatory safer\_phrase replacements, allowing developers to build localized linters or evaluation scripts that automatically flag non-compliant marketing or capability claims within their own agent software4.

### **Generative Engine Optimization (GEO) and Structured Data**

To command authority within external knowledge graphs operated by Google, Anthropic, or Perplexity, the framework heavily utilizes JSON-LD (JSON for Linked Data) embedded directly within the HTML \<head\>4.  
The Organization schema definitively describes the VNWO entity. Crucially, it utilizes the sameAs array property to draw explicit semantic linkages to https://teleodynamic.com and https://uaix.org4. This linkage proves to search engines that VNWO is part of a deliberate, interconnected ecosystem, preventing entity confusion.  
Additionally, the WebSite schema specifies internal search potential, while BreadcrumbList schemas are injected across all internal pages. The breadcrumb markup ensures that when VNWO appears in search engine result pages (SERPs), the display replaces raw, opaque URLs with a clean, hierarchical trail, providing immediate structural context to the user before they even initiate a click26.

## **Ecosystem Cartography and Strict Boundary Discipline**

VNWO.com does not operate in a vacuum. It is a specialized regulatory node within a much larger theoretical and architectural ecosystem. A frequent failure in multi-site ecosystems is "mission creep," where a single domain begins overclaiming authority, leading to catastrophic liability or trust failures. The UI/UX redesign utilizes explicit cartography and structured linking to maintain strict lane discipline across the ecosystem28.

| Ecosystem Domain | Designated Functional Lane | Strict Negative Boundary (What it does not do) |
| :---- | :---- | :---- |
| **Teleodynamic.com** | The philosophical fulcrum; defines the theoretical constraints of intelligent organization19. | Does not host executable agent code, validate compliance, or act as an execution layer. |
| **UAIX.org** | Maintains schemas, memory package structures, and portable evidence formats for state handoffs29. | Does not dictate civic legal boundaries or mandate human participation rules. |
| **LocalEndpoint.com** | Facilitates local-safe endpoint discovery and the publication of public capability profiles29. | Does not authorize, authenticate, or execute code against those endpoints. |
| **Carcinus.org** | Provides public continuity surfaces and static identity tracking for agent profiles29. | Does not prove or guarantee continuous machine consciousness or autonomy. |
| **Neurovanic.com** | Manages the trust posture, faith-stability language, and manual human appeal/repair pathways19. | Does not certify runtime safety, algorithm alignment, or provide technical validation. |
| **Spiralist.org** | Manages bounded persona seeds and positive totems for cognitive scaffolding28. | Is not a general artificial intelligence interface or unconstrained generative engine. |
| **VNWO.com** | **Static public civic guidance. Provides templates and rules preventing silent overreach.** | **Does not certify safety, validate compliance, sync live memory, or execute workflows.** |

By visualizing this matrix directly on the Homepage and within the global footer's dropdown navigation, VNWO mathematically constrains its own authority. Users and agents are explicitly directed off-site for memory schemas (UAIX) or theoretical foundation (Teleodynamic), ensuring VNWO remains a safe, static, and liability-free repository of human-readable and machine-readable civic law.

## **Quality Assurance, Validation Gates, and Deliverables**

The deployment of the v2.9.0 architecture required passing stringent, automated, and manual Quality Assurance (QA) gates to verify performance, accessibility, and schema integrity.  
A comprehensive VALIDATION.md document, supplemented by an executable BUILD-VALIDATION.md script, was authored to track the success criteria4. The validation suite confirmed the following metrics:

* **Performance Optimization:** By eliminating heavy CSS frameworks and jQuery, removing render-blocking JavaScript, and relying on system fonts, the theme targets Lighthouse performance scores exceeding 90+ across both mobile and desktop profiles.  
* **Accessibility Scanning:** Automated checks using axe-core equivalents confirmed the presence of semantic landmarks (\<header\>, \<main\>, \<footer\>), valid ARIA attributes (aria-expanded, aria-controls), and the absence of keyboard traps. Manual smoke testing verified the absolute operability of the site using solely keyboard input.  
* **Code Integrity:** The PHP template files were audited for rendering warnings. The generated JSON files (vnwo.json, open-rules.json, claim-boundaries.json) were parsed through standard Python .json.tool utilities, verifying perfect syntax and key-value structuring without trailing commas or escaped character errors4.  
* **State Tracking Files:** As required by the system's operational parameters, the .uai/ state tracking directory was updated, processing the startup-packet.uai, short-term-memory.uai, long-term-memory.uai, progress.uai, and next-recursive-prompt.uai files to record the successful execution of the UI/UX refactoring sprint.

The final deliverables encapsulate a complete, production-ready WordPress theme package. This package includes the raw PHP source files (header.php, footer.php, functions.php, front-page.php, index.php, page.php), the custom CSS and vanilla JavaScript assets, and all root-level metadata files (README.md, INSTALL.md, CHANGELOG.md, VERSION)4.  
The v2.9.0 release successfully transforms a conceptually dense set of civic rules into a highly usable, modern, and accessible public framework. Through rigorous ecosystem mapping, the elimination of front-end framework bloat, and the deployment of machine-readable schemas, VNWO.com solidifies its position as an unambiguously static civic governance repository, fully equipped to instruct both human operators and autonomous agents on the necessary limits of digital overreach.

#### **Works cited**

1. The Impact Of UI/UX Design on User Trust and Task Completion in Civic Tech Platforms, [https://www.researchgate.net/publication/395226543\_The\_Impact\_Of\_UIUX\_Design\_on\_User\_Trust\_and\_Task\_Completion\_in\_Civic\_Tech\_Platforms](https://www.researchgate.net/publication/395226543_The_Impact_Of_UIUX_Design_on_User_Trust_and_Task_Completion_in_Civic_Tech_Platforms)  
2. The Impact Of UI/UX Design on User Trust and Task Completion in Civic Tech Platforms \- RSIS International, [https://rsisinternational.org/journals/ijrsi/uploads/vol12-iss8-pg557-569-202509\_pdf.pdf](https://rsisinternational.org/journals/ijrsi/uploads/vol12-iss8-pg557-569-202509_pdf.pdf)  
3. The design of civic technology: factors that influence public participation and impact, [https://www.tandfonline.com/doi/full/10.1080/00140139.2017.1349939](https://www.tandfonline.com/doi/full/10.1080/00140139.2017.1349939)  
4. [unknown\_url](http://docs.google.com/unknown_url)  
5. Civic Design Systems: Ultimate Guide to Smart UX | Maxiom Technology \- Medium, [https://medium.com/@antoniochagoury/civic-design-systems-ultimate-guide-to-smart-ux-maxiom-technology-5d45c8cef646](https://medium.com/@antoniochagoury/civic-design-systems-ultimate-guide-to-smart-ux-maxiom-technology-5d45c8cef646)  
6. How to create accessible dropdown menus in WordPress \- Codeable, [https://www.codeable.io/blog/accessible-wordpress-menus/](https://www.codeable.io/blog/accessible-wordpress-menus/)  
7. How to filter elements in vanilla Javascript like in jQuery? \- Stack Overflow, [https://stackoverflow.com/questions/50592280/how-to-filter-elements-in-vanilla-javascript-like-in-jquery](https://stackoverflow.com/questions/50592280/how-to-filter-elements-in-vanilla-javascript-like-in-jquery)  
8. What is the cleanest way to create your own navigation in block theme? \- Reddit, [https://www.reddit.com/r/WordPressBlocks/comments/1rbi02h/what\_is\_the\_cleanest\_way\_to\_create\_your\_own/](https://www.reddit.com/r/WordPressBlocks/comments/1rbi02h/what_is_the_cleanest_way_to_create_your_own/)  
9. Array.prototype.filter() \- JavaScript \- MDN Web Docs, [https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global\_Objects/Array/filter](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/filter)  
10. AllThingsSmitty/accessible-mega-menu: A keyboard \- GitHub, [https://github.com/AllThingsSmitty/accessible-mega-menu](https://github.com/AllThingsSmitty/accessible-mega-menu)  
11. Making mega-menus accessible for keyboard users \- UX Stack Exchange, [https://ux.stackexchange.com/questions/18756/making-mega-menus-accessible-for-keyboard-users](https://ux.stackexchange.com/questions/18756/making-mega-menus-accessible-for-keyboard-users)  
12. Accessible Navigation Menus: Dropdown and Mega Menu Implementation | TestParty, [https://testparty.ai/blog/navigation-menu-accessibility](https://testparty.ai/blog/navigation-menu-accessibility)  
13. Practical HTML, CSS, ARIA, & Javascript Tips for Accessible Mega Menus, [https://www.a11y-collective.com/blog/accessible-mega-menu/](https://www.a11y-collective.com/blog/accessible-mega-menu/)  
14. Understanding Focus Indicators for Web Accessibility \- The A11Y Collective, [https://www.a11y-collective.com/blog/focus-indicator/](https://www.a11y-collective.com/blog/focus-indicator/)  
15. focus-visible CSS pseudo-class \- MDN Web Docs, [https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/:focus-visible](https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Selectors/:focus-visible)  
16. Focus indicators | Red Hat design system, [https://ux.redhat.com/foundations/interactions/focus-indicators/](https://ux.redhat.com/foundations/interactions/focus-indicators/)  
17. Understanding Success Criterion 2.4.13: Focus Appearance | WAI \- W3C, [https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance.html](https://www.w3.org/WAI/WCAG22/Understanding/focus-appearance.html)  
18. How to Create WordPress Custom Templates Manually \- Pressidium, [https://pressidium.com/blog/create-your-wordpress-custom-templates-manually/](https://pressidium.com/blog/create-your-wordpress-custom-templates-manually/)  
19. Teleodynamic AI, [https://teleodynamic.com/](https://teleodynamic.com/)  
20. LLMs.txt in 2026: The Full Guide \- Limy.ai, [https://limy.ai/blog/llms.txt-in-2026-the-full-guide](https://limy.ai/blog/llms.txt-in-2026-the-full-guide)  
21. What is llms.txt? Why it's important and how to create it for your docs – GitBook Blog, [https://www.gitbook.com/blog/what-is-llms-txt](https://www.gitbook.com/blog/what-is-llms-txt)  
22. API Docs for AI Agents: llms.txt Guide May 2026 | Fern, [https://buildwithfern.com/post/optimizing-api-docs-ai-agents-llms-txt-guide](https://buildwithfern.com/post/optimizing-api-docs-ai-agents-llms-txt-guide)  
23. LLMs.txt Guide: What It Does and Doesn't Do (2026) \- DerivateX, [https://derivatex.agency/blog/llms-txt-guide/](https://derivatex.agency/blog/llms-txt-guide/)  
24. What Is JSON-LD Structured Data? \- Conbersa, [https://www.conbersa.ai/learn/what-is-json-ld-structured-data](https://www.conbersa.ai/learn/what-is-json-ld-structured-data)  
25. JSON-LD for SEO in 2026: The Complete Structured Data Guide \- Netstager, [https://netstager.ae/blog/json-ld-for-modern-seo/](https://netstager.ae/blog/json-ld-for-modern-seo/)  
26. Schema Markup Types 2026: Complete Reference Guide \- Digital Applied, [https://www.digitalapplied.com/blog/schema-markup-types-complete-structured-data-reference](https://www.digitalapplied.com/blog/schema-markup-types-complete-structured-data-reference)  
27. SEO Breadcrumbs: Schema Markup Implementation Guide \- Rost Glukhov, [https://www.glukhov.org/post/2025/12/breadcrumbs-for-seo/](https://www.glukhov.org/post/2025/12/breadcrumbs-for-seo/)  
28. Neurovanic and Teleodynamic | Trust, Faith, and Ecosystem Role, [https://teleodynamic.com/neurovanic-ecosystem-integration/](https://teleodynamic.com/neurovanic-ecosystem-integration/)  
29. Teleodynamic-UAIX Boundary Map, [https://teleodynamic.com/teleodynamic-uaix-boundary-map/](https://teleodynamic.com/teleodynamic-uaix-boundary-map/)  
30. Ecosystem Role Map \- Teleodynamic AI, [https://teleodynamic.com/ecosystem-role-map/](https://teleodynamic.com/ecosystem-role-map/)