Breaking down the accessibility requirements of this project felt like one of the more hard exercises of the whole research process, because we are used to think everything would have been “easy and smooth” since it’s a niche digital research product. But there was much more behind.
What the user should be capable of
On a physical and personal level, sight would be the most relevant sense, since the experience is largely text-based, but it can be made compatible with screen readers and text-to-speech tools from the start. Hearing is not a requirement at all. Movement needs are minimal too, limited to basic typing, clicking, or scrolling, with voice dictation and keyboard-only navigation as fallbacks.
On the cognitive level is where it gets more demanding. Following an iterative loop of prompting, reviewing, and editing requires sustained mental focus and a willingness to sit with a process that is genuinely not instantaneous. As well as the need for a strong digital literacy to navigate AI tools or terminology, and enough language confidence to work in what are predominantly English environments. Though nowadays everything can be translated in real time.
Financially, the core methodology is designed to be of course a free to access tool, to be used as a starting point or guideline to use AI tools. Infrastructure needs are also few: a device and internet connection.
Who is it meant for and where does this happen
The methodology will be designed for anyone engaging with storytelling on a professional or exploratory level, from researchers and creatives to students and private users. It lives entirely in digital space, which means it can happen in any place and environment.
What it does require is probably the mindset: willingness and awareness to co-create with a machine, and enough critical thinking to question what the machine gives back.
The barriers
Two barriers kept coming up in the entire thinking process. The first was language, since AI tools lean heavily on English, nuance is often the first casualty of translation. The solution here could be to develop a simplified and even more visual version of the methodology that relies on basic English, diagrams, and examples rather than dense theoretical language.
The second barrier was knowledge. The informatics specific terminology involved is genuinely intimidating and not of common knowledge (it was for me too). The solution I thought for this issue was to add a vocabulary directly into the framework itself, so all the basic knowledge can be in the same place as the product.
To conclude, cognitive overload is also worth a mention. When the prompting loop feels endless and the output feels overwhelming, the step-by-step structure of the methodology becomes less of a nice-to-have and more of a way to escape.
