Accessibility#

Balospe.com is committed to being accessible to all visitors, regardless of how they are differently abled. Every human being navigates the world with a unique set of abilities, even if many so-called neurotypical people do not yet think of themselves that way. This page describes what we are doing and where we need help.

Accessing abstract mathematical content#

One area where this site strives hardest to help visitors succeed is accessing the essence of abstract mathematical content where it matters most. This is particularly important for readers who suffer from math anxiety or even math phobia due to prior traumatic experiences with how they were introduced to mathematics.

Math phobia is not yet recognized by the Diagnostic and Statistical Manual of Mental Disorders (DSM-5-TR) as a specific clinical disorder. This says more about the medical experts who compile the DSM than it says about the devastating reality that math anxiety is playing in the fate of Life on Earth. When citizens cannot assess existential risk because they fear the mathematics that describes it, the consequences are civilizational.

LLoL’s vision for Balospe.com includes translating abstract formal content into accessible explanations at multiple levels — for beginners, for producers, and for experts — so that mathematical literacy becomes achievable regardless of a visitor’s starting point. The site’s naming system already provides beginner-friendly entry points alongside expert-level formal definitions.

The translation challenge#

Unfortunately, this translation task is enormous. Covering all the abstract content on this site in ways that are genuinely accessible to diverse audiences requires sustained, skilled effort from many contributors.

This is a core reason for the ResearchCity vision and the call for global support. A dedicated ResearchCity would employ accessibility experts, educational designers, and translators to systematically make every key insight on this site reachable by those who need it most.

Currently, the scaling up is at Stage 0 — one person (LLoL) doing what he can on a shoestring budget. If you wish to support this work and help make abstract mathematical content accessible to everyone, here is how you can buy in.

Accessing content in different languages#

Being differently abled also extends to language. Not everyone reads English, and the ideas on this site are intended for all of humanity. The site supports 10 languages (English, German, Spanish, French, Portuguese, Russian, Arabic, Hebrew, Hindi, Chinese), but translation coverage is currently minimal.

The translation effort needs volunteers and eventually professional translators funded through ResearchCity. If you can help translate content into your language, that is one of the most impactful contributions you can make to accessibility.

Technical accessibility#

What is currently in place:

  • Keyboard navigation — all interactive elements are keyboard-accessible.

  • Screen reader compatibility — the site generates semantic HTML via Sphinx.

  • Responsive design — content adapts to mobile, tablet, and desktop.

  • Light and dark themes — reduces eye strain for different visual preferences.

  • Right-to-left support — Arabic and Hebrew content renders correctly.

  • Alt text on images — descriptive text for visual content.

  • Decorative elements marked aria-hidden="true" (e.g., separator SVGs).

What we are working toward:

  • WCAG 2.1 Level AA conformance.

  • Improved accessibility of mathematical notation for screen readers.

  • Captioned or transcribed audio/video content.

  • Improved color contrast across all page elements.

Known limitations#

  • Some mathematical content (MathJax-rendered formulas) may not be fully accessible via screen readers.

  • PDF versions of pages may have limited accessibility features.

  • Translation coverage is currently minimal beyond English.

  • The site is under active development — accessibility improvements are ongoing.

Report an accessibility barrier#

If you encounter an accessibility barrier on this site, please let us know. Your feedback helps us prioritize improvements.

Send accessibility feedback via FeedbackFlow

Note: accessibility reports are pre-classified as k3 s3 (higher priority, shorter-term) because removing barriers to access is urgent.

Notes

Content stability — Content is variant dv_Auto_MMv1_2026m03d31 (see StayVS). Rebuilt 2026-05-18.

See also on Balospe.com
How you can improve this page: Send your FeedbackFlow

For the full guide on providing feedback — including how it is handled, licensing, and what to expect — see How to use FeedbackFlow.

Please check if See also on Balospe.com above already addresses your idea. Feedback works best when it targets the most specific page. If none of those pages help, you may have a good case for sending FF here.

To submit your FeedbackFlow:

  1. Click anywhere on the email preview below to open a pre-filled email.

  2. Replace the placeholder text with your feedback.

  3. Send.

To submit your FeedbackFlow, click anywhere on the email preview below:

To: [email protected] CC: [email protected] Subject: FF k2 s2 AIMS for [accessibility] Replace_by_OneLineSummary Body: To make this page [accessibility] more gentle kind reasonable for beginners, producers, andOr experts with a background in xyz: Please consider improving this:

Adjusting importance and urgency in the AIMS Plotter

The email subject encodes two independent AIMS variables: k (impact, y-axis) and s (seasoning time, x-axis). Default k2 s2 = moderate impact, mid-term. Increase both to k3 s3 for higher priority, decrease to k1 s1 for lower. See AIMS details.