UAIE announced to browsers
Fiza Pathan announced UAIE™, a learner‑controlled accessibility engine that supports text‑to‑speech, Braille, sign language and other modes and said it has been submitted to major browsers. The post positions UAIE as an engine meant to be integrated into learning platforms and browser accessibility stacks. (x.com)
A web page can become speech, Braille, or simpler text if its content is exposed in machine-readable form. Fiza Pathan said she has built a browser-based layer for that and submitted it to major browsers. (x.com) Pathan’s public documentation calls the project the Universal Adaptive Interface Engine, or UAIE, and describes it as a “learner-controlled” system rather than a fixed accessibility preset. Her site says users can switch modes themselves through a browser panel. (fizapathansteachingportfolioforpgcite.com) The guide says the panel includes text to speech, “Live Braille,” plain-language rewriting, voice navigation, reading masks, contrast controls, and support pages for sign language and captions. A separate page says the current version is UAIE v2.1 and appears across her teaching portfolio without a login. (fizapathansteachingportfolioforpgcite.com) Modern web accessibility usually works in layers: authors mark up a page, browsers pass that structure into operating-system accessibility interfaces, and assistive tools such as screen readers turn it into speech or Braille. The World Wide Web Consortium’s standards say text alternatives are what let content be transformed into Braille, speech, symbols, or simpler language. (w3.org) Those standards already cover a wide range of disability needs, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. The same standards body says browsers and assistive technologies share the job of carrying that information to users. (w3.org, w3.org) That is where Pathan is placing UAIE: not as a new web standard, but as an extra control layer that sits in the browser and lets a learner choose how a page is presented. Her “Accessibility Innovation” page says the engine was built for educational use and maps six profiles to disability categories recognized in the United Kingdom’s Equality Act 2010. (fizapathansteachingportfolioforpgcite.com) Pathan says she began the accessibility overhaul of her teaching portfolio on March 31, 2026 and finished that day with “zero errors” on the WAVE checker and a 21:1 contrast ratio. Her résumé page says she is an educator with 14 years of teaching experience, and her portfolio says it was developed for a Postgraduate Certificate in International Teacher Education. (fizapathansteachingportfolioforpgcite.com, fizapathansteachingportfolioforpgcite.com, fizapathansteachingportfolioforpgcite.com) Her privacy policy also shows the project is still at an early product stage. It says the extension stores settings locally, and says Anthropic application programming interface calls use a user’s own key rather than being routed through Pathan’s servers. (fizapathansteachingportfolioforpgcite.com) Pathan’s post did not name the browsers, publish submission receipts, or say whether any browser maker had accepted or reviewed the engine. For now, the clearest public record is a working demonstration on her own site and her claim that she wants UAIE integrated into learning platforms and browser accessibility stacks. (x.com, fizapathansteachingportfolioforpgcite.com)
