Molecular Access is a project which facilitates dynamic communication
between processes in order to allow end-users to modify abstract data
exposed to them by processes, and to allow processes to call abstract
methods declared by other processes.
All of this is accomplished in a non-invasive way, which prioritises
developers, and follows an opt-in approach to features. Projects can
expose as much or as little data or functionality towards one another
as they like.
The end goal here is to allow users, particularly users in need of
additional customisation to ensure accessibility, to be able to easily
manage the data and resources of other processes. That's customisation
which might include changing an image texture, changing a colour
value, disabling or enabling visual effects, etc.
Such functionality can already be provided to users through bespoke,
custom implementations, without the need of Molecular - however, it
comes at the expense of standardisation, and at the expense of
possible integration between other processes. This solution is
scalable, dynamic, and made to cultivate ecosystems. In contrast,
opening up features to users without such a project leaves such
features isolated, especially when the idea of inter-process
communication is neglected or outright rejected.
In practice, Molecular Access is a project aiming to make software
more transparent, at the discretion of developers, in hopes of
improving accessibility.