Showing posts with label accessibility. Show all posts
Showing posts with label accessibility. Show all posts

Digital Accessibility Training

Mike's Notes

I stole this content from all over the place. Sorry if I didn't credit you; I forgot where this came from. All useful stuff.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

04/08/2026

Digital Accessibility Training

By: Mike Peters
On a Sandy Beach: 04/06/2026

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Accessibility For Everyone (https://lnkd.in/dVvgMG29), a wonderful free book on web accessibility for designers, developers, content folks — pretty much everyone. Written 9 years ago, but still very much relevant today. With sections on disabilities, impairments, planning for accessibility, design and testing. Kindly released by Laura Kalbag.

Free Books on Accessibility

Giving A Damn About Accessibility, by Sheri Byrne-Haber (disabled)

PDF: https://lnkd.in/eqbz5Npw

  • Audio: https://lnkd.in/emYMbEDc

Web Accessibility In Plain Language, by Charlie Triplett

  • https://lnkd.in/e2AMAwyt

AccessAbility Playbook, by Government of Canada

  • https://lnkd.in/e2W3viJb

Appt Accessibility Handbook, by Jan Jaap de Groot, Paul van Workum CPACC

  • https://lnkd.in/e3V7eTU9

Accessibility Foundations (Free Guide), by Henny Swan

  • https://lnkd.in/erGd9vX7

WCAG 2.2 Card Deck (Updated!), by Johannes Lehner

  • https://lnkd.in/eQgDsY9j

Free Practical Books For Designers

  • https://lnkd.in/dsxAukXq

And a *HUGE* thanks yet again to wonderful Laura Kalbag and everyone sharing their insights, learnings, and experiences in wonderful resources like these — for everyone to learn from and build open. Your work doesn’t go unnoticed!

A roadmap for accelerators

Mike's Notes

It's getting busy, so I need a roadmap for accelerators now.

Resources

References

  • Reference

Repository

  • Home > Ajabbi Research > Library >
  • Home > Handbook > 

Last Updated

02/06/2026

A roadmap for accelerators

By: Mike Peters
On a Sandy Beach: 27/03/2026

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

Lots of opportunities are coming in.

This is a roadmap for using coaching, workshops, incubators and accelerators to develop, test and validate the Ajabbi Mission Business Model and the Pipi closed-core and Pipi open-source applications.

Ultimately, it's a record of what is learned, so it doesn't include missed opportunities or declined applications. There are a few missing items from some time back that are yet to be added.

Free is good (cloud credits, bro bono, software, training), but no funding or investment is being sought.

The roadmap is sorted by deadline, so that I remember to do them. The first row of the table is a key.


Date Roadmap

deadline

Start-End

Status

Title

Description

What

To come.

  • To come

Learned

  • To come

To do/done

  • To come

Resources


deadline

2017-2020

Completed

Steve Blank

"Steve Blank (born 1953) is an American entrepreneur, educator, author and speaker. He created the customer development method that launched the lean startup movement. His work has influenced modern entrepreneurship through the creation of tools and processes for new ventures, which differ from those used in large companies."

What

Learning from the very best.

  • Reading his books and blog
  • Watching videos
  • Using all the free courses and tools

Learned

  • How to use a Business Model Canvas
  • How to use a Mission Model Canvas
  • How to do customer discovery
  • How to run experiments to validate assumptions

Done

    • Read and tried everything
    • Build Pipi Experiment Engine

    Resources

    deadline

    2020-2023

    Completed

    KiwiSaaS

    "Our community is free to join, and it's where we can safely share our knowledge and experiences with each other. Paying it forward is what drives kiwiSaaS growth."

    What

    Online workshops and random monthly one-on-one meetings with other founders.

      Learned

      • To keep going and when to change course
      • It is OK to make mistakes
      • Will get lots of insights from being open
      • The importance of listening to others

      Done

      • Get stuck in

      Resources

      January 2024

      January - October 2024

      Completed

      Startup Aotearoa

      "Startup Aotearoa ignites New Zealand’s entrepreneurial spirit by providing personalised one-to-one coaching to early-stage startup founders. Delivered nationwide through local regional providers,"

      What

      Mentoring from Mr G led to testing the ICP at Waimumu Southern Field Days 2024 on

      • Developers at Agritech companies
      • Agricultural suppliers

      Learned

      • Developers are the ICP
      • There is a real problem to solve
      • Find a teaching customer

      Done

        • Pivot ajabbi.com to developers
        • Host a teaching customer requiring 3 languages

        Resources

        April 2024

        May - November 2024

        Completed

        Creative HQ's On the Business workshop series

        "This 'On the Business' workshop series gives you the dedicated time and resource to help you grow your business. We'll provide tools, frameworks and hands-on..."

        What

        Remote workshops using Miro canvas.

        Learned

        • To come

        Done

        • To come

        Resources

        February 2025

        February 2025 - March 2025

        Completed

        NZTE Export Essentials SaaS 4-part workshop.

        "Learn what best-practise exporting involves when you sell SaaS offshore."

        What

        Workshops with individual follow-up sessions.

        Learned

        • To use the tools available to test assumptions.

        Done

        • To come

        Resources

        February 2025

        February 2025 - March 2025

        Completed

        NZTE Position for Growth workshop.

        "Our Position for Growth workshops help you define what problem you solve for"

        What

        Workshops with individual follow-up sessions.

        Learned

        • To use the tools available to test assumptions.

        Done

          • To come

          Resources

          25/03/2026

          April 2026 - March 2028

          Application Withdrawn

          Google AI Accelerator

          "With this program, you can get access to startup experts, your Google Cloud and Firebase costs covered up to $200,000 USD (up to $350,000 USD for AI startups) over 2 years, technical training, business support, and Google-wide offers."

          What

          Collaborate with DeepMind to run wild ML integration experiments to go where no developer has gone before.

          • Pipi > IaC > GCP
          • Pipi > VM > BoxLang > Workspaces
          • Pipi > MCP > DeepMind Gemini
          • Pipi > Scientific Workflows > TPU

          Learned

          • Invited to apply by a Google chap who was assisting behind the scenes using an unlisted pathway. I then discovered that free credits begin on the day of application approval, so I will reapply when ready to start in July to make the most of the 24-month window of opportunity.

          To do

          • Increase Pipi DevOps speed (x1000) by completing work on automating the data centre (x10), workspace rendering (x10), and IaC to GCP free tier (x10). This will enable fast, multiple automated experiments.

          Resources

            26/05/2026

            July - November 2026

            Application underway

            Sprout Accelerator

            "The Sprout Accelerator takes a cohort of agrifood innovators on a 3-month adventure to discover, articulate and refine the foundations to grow global startups."

            What

            Test farm management workspace using HTML Mockups on

            • Dairy farmer-led catchment group
            • Agritech wait list from Waimumu

            Learned

            • To come

            To do

            • To come

            Resources

            June 2026

            July 2026 - June 2028

            To apply

            Google AI Accelerator

            "With this program, you can get access to startup experts, your Google Cloud and Firebase costs covered up to $200,000 USD (up to $350,000 USD for AI startups) over 2 years, technical training, business support, and Google-wide offers."

            What

            Collaborate with DeepMind to run wild ML integration experiments to go where no developer has gone before.

            • Pipi > IaC > GCP
            • Pipi > VM > BoxLang > Workspaces
            • Pipi > MCP > DeepMind Gemini
            • Pipi > Scientific Workflows > TPU

            Learned

            • To come

            To do

            • To come

            Resources


             


             

            How YouTube and Adhesive Tape Are Disrupting Assistive Technology

            Mike's Notes

            Very cool. Making stuff.

            Resources

            References

            • Reference

            Repository

            • Home > Ajabbi Research > Library > Subscriptions > IEEE Spectrum
            • Home > Handbook > 

            Last Updated

            24/03/2026

            How YouTube and Adhesive Tape Are Disrupting Assistive Technology

            By: Jason Hahr
            IEEE Spectrum: 31/01/2026

            Jason Hahr is a 2025 IEEE Spectrum Taenzer Fellow in disability rights and assistive technology journalism.

            The “MacGyver” approach lets disabled users reconfigure their tech

            One of maker Therese Willkomm's assistive tech hacks involved developing a control panel for GPS map apps—part of her mission to help disabled people find their way through a non-compliant tech world. Therese Willkomm

            Assistive technology is expensive, and many people with disabilities live on fixed incomes. Disabled assistive tech users also must contend with equipment that was often designed without any capacity to be repaired or modified. But assistive tech users ultimately need the functionality they need—a wheelchair that isn’t constantly needing to be charged, perhaps, or a hearing aid that doesn’t amplify all background noise equally. Assistive tech “makers,” who can hack and modify existing assistive tech, have always been in high demand.

            Therese Willkomm, emeritus professor of occupational therapy at the University of New Hampshire, has written three books cataloging her more than 2,000 assistive technology hacks. Willkomm says she aims to keep her assistive tech hacks costing less than five dollars.

            She’s come to be known internationally as the “MacGyver of Assistive Technology” and has presented more than 600 workshops and assistive tech maker days across 42 states and 14 countries.

            IEEE Spectrum sat down with Willkomm ahead of her latest assistive tech Maker Day workshop, on Saturday, 31 January, at the Assistive Technology Industry Association (ATIA) conference in Orlando, Florida. Over the course of the conversation, she discussed the evolution of assistive technology over 40 years, the urgent need for affordable communication devices, and why the DIY movement matters now more than ever.

            IEEE Spectrum: What got you started in assistive technology?

            Therese Willkomm: I grew up in Wisconsin, where my father had a machine shop and worked on dairy and hog farms. At age 10, I started building and making things. A cousin was in a farm accident and needed modifications to his tractor, which introduced me to welding. In college, I enrolled in vocational rehabilitation and learned about rehab engineering—assistive technology wasn’t coined until 1988 with the Technology-Related Assistance Act. In 1979, Gregg Vanderheiden came to the University of Wisconsin-Stout and demonstrated creative things with garage door openers and communication devices. I thought, “Wow, this would be an awesome career path—designing and fabricating devices and worksite adaptations for people with disabilities to go back to work and live independently.” I haven’t looked back.

            You’ve created over 2,000 assistive technology solutions. What’s your most memorable one?

            Willkomm: A device for castrating pigs with one hand. We figured out a way to design a device that fit on the end of the hog crate that was foot-operated to hold the hind legs of the pig back so the procedure could be done with one hand.

            Assistive Technology’s Changing Landscape

            How has assistive technology evolved over the decades?

            Willkomm: In the 1980s, we fabricated devices from wood and early electronics. I became a [Rehabilitation Engineering and Assistive Technology Society of North America, a.k.a. RESNA] member in 1985. The 1988 Technology-Related Assistance Act was transformational—all 50 states finally got funding to support assistive technology and needs in rural areas. Back in the ‘80s, we were soldering and making battery interrupters and momentary switches for toys, radios, and music. Gregg was doing some things with communication. There were Prentke Romich communication devices. Those were some of the first electronic assistive technologies.

            The early 1990s was all about mobile rehab engineering. Senator Bob Dole gave me a $50,000 grant to fund my first mobile unit. That mobile unit had all my welding equipment, all my fabrication equipment, and I could drive farm to farm, set up outside right in front of the tractor, and fabricate whatever needed to be fabricated. Then, around 1997, there were cuts in the school systems. Mobile units became really expensive to operate. We started to look at more efficient ways of providing assistive technology services. With the Tech Act, we had demonstration sites where people would come and try out different devices. But people had to get in a car, drive to a center, get out, find parking, come into the building—a lot of time was being lost.

            In the 2000s, more challenges with decreased funding. I discovered that with a Honda Accord and those crates you get from Staples, you could have your whole mobile unit in the trunk of your car because of advances in materials. We could make battery interrupters and momentary switches without ever having to solder. We can make switches in 28 seconds, battery interrupters in 18 seconds. When COVID happened, we had to pivot—do more virtual, ship stuff out to people. We were able to serve more individuals during COVID than prior to COVID because nobody had to travel.

            How do you keep costs under five dollars?

            Willkomm: I aim for five dollars or less. I get tons of corrugated plastic donated for free, so we spend no money on that. Then there’s Scapa Tape—a very aggressive double-sided foam tape that costs five cents a foot. If you fabricate something and it doesn’t work out, and you have to reposition, you’re out a nickel’s worth of material. Buying Velcro in bulk helps too. Then Instamorph—it is non-toxic, biodegradable. You can reheat it, reform it, in five minutes or less up to six times. I’ve created about 132 different devices just using Instamorph. A lot of things I make out of Instamorph don’t necessarily work. I have a bucket, and I reuse that Instamorph. We can get six, seven devices out of reusable Instamorph. That’s how we keep it under five dollars.

            What key legislation impacts assistive technology?

            Willkomm: Definitely the Technology-Related Assistance Act. In the school system, however, it only says “Did you consider assistive technology?” So that legislation really needs to be beefed up. The third piece of legislation I worked on was the AgrAbility legislation to fund assistive technology consultations and technical assistance for farmers and ranchers. The latest Technology-Related Assistance Act was reauthorized in 2022. Not a whole lot of changes—it’s still assistive technology device demonstrations and loans, device reuse, training, technical assistance, information and awareness. The other thing is NIDILRR—National Institute on Independent Living and Rehabilitation Research, funded under [the U.S. Department of Health and Human Services, a.k.a. HHS]. Funding the rehab engineering centers was pretty significant in advancing the field because these were huge, multimillion-dollar centers dedicated to core areas like communication and employment. Now there’s a new one out on artificial intelligence.

            With over 2,000 hacks to improve usability of assistive technologies, veteran DIY maker Therese Willkomm has earned the moniker “the MacGyver of assistive tech.” Therese Willkomm

            A Vision for a Better Assistive Tech Future

            What deserves more focus in your field?

            Willkomm: The supply-and-demand problem. It all comes down to time and money. We have an elderly population that continues to grow, and a disability population that continues to grow—high demand, high need for assistive technology, yet the resources available to meet that need are limited. A few years back, the Christopher & Dana Reeve Foundation had a competition. I submitted a proposal similar to the Blue Apron approach. People don’t have supplies at their house. They can’t buy two inches of tape—they have to buy a whole roll. They can’t buy one foot of corrugated plastic—they’ve got to buy an 18-by-24 sheet or wait till it gets donated.

            With my third book, I created solutions with QR codes showing videos on how to make them. I used Christopher Reeve Foundation funding to purchase supplies. With Blue Apron, somebody wants to make dinner and a box arrives with a chicken breast, potato, vegetables, and recipe. I thought, what if we could apply that to assistive technology? Somebody needs something, there’s a solution out there, but they don’t have the money or the time—how can we quickly put it in a box and send it to them? People who attended my workshops didn’t have to spend money on materials or waste time at the store. They’d watch the video and assemble it.

            But then there were people who said, “I do not have even five minutes in the school day to stop what I’m doing to make something.” So we found volunteers who said, “Hey, I can make slant boards. I can make switches. I can adapt toys.” You have people who want to build stuff and people who need stuff. If you can deal with the time and money issue, anything’s possible to serve more people and provide more devices.

            What’s your biggest vision for the future?

            Willkomm: I’m very passionate about communication. December 15 was the passage in 1791 of our First Amendment, freedom of speech. Yet people with communication impairments are denied their basic right of freedom of speech because they don’t have an affordable communication device, or it takes too long to program or learn. I just wish we could get better at designing and fabricating affordable communication devices, so everybody is awarded their First Amendment right. It shouldn’t be something that’s nice to have—it’s something that’s needed to have. When you lose your leg, you’re fitted with a prosthetic device, and insurance covers that. Insurance should also cover communication devices and all the support services needed. With voice recognition and computer-generated voices, there are tremendous opportunities in assistive technology for communication impairments that need to be addressed.

            What should IEEE Spectrum readers take away from this conversation?

            Willkomm: There’s tremendous need for this skill set—working in conjunction with AI and material sciences and the field of assistive technology and rehab engineering. I’d like people to look at opportunities to volunteer their time and also to pursue careers in the field of specialized rehab engineering.

            How are DIY approaches evolving with new technologies?

            Willkomm: What we’re seeing at maker fairs is more people doing 3D printing, switch-access controls, and these five-minute approaches. There has to be a healthy balance between what we can do with or without electronics. If we need something programmed with electronics, absolutely—but is there a faster way?

            The other thing that’s interesting is skill development. You used to have to go to college for four, six, eight years. With YouTube, you can learn so much on the internet. You can develop skills in things you never thought were possible without a four-year degree. There’s basic electronic stuff you can absolutely learn without taking a course. I think we’re going to have more people out there doing hacks, asking “What if I change it this way?” We don’t need to have a switch.

            We need to look at the person’s body and how that body interacts with the electronic device interface so it requires minimal effort—whether it be eye control or motion control. Having devices that predict what you’re going to want next, that are constantly listening, knowing the way you talk. I love the fact that AI looks at all my emails and creates this whole thing like “Here’s how I’d respond.” I’m like, yeah, that’s exactly it. I just hit select, and I don’t have to type it all out. It speeds up communication. We’re living in exciting times right now.

            This article was supported by the IEEE Foundation and a John C. Taenzer fellowship grant.

            The Accessibility Issue

            Mike's Notes

            This is a copy of the February issue of Ajabbi Research.

            It is about the history of the effort to create a fully accessible User Interface (UI) for Pipi.

            Ajabbi Research is published on SubStack on the first Friday of each month, and subscriptions are free.

            Each issue is a broad historical overview of a research topic, serving as an index to dozens of previously posted related articles. There are now 647 articles/posts.

            This copy of the issue will be updated with additional information as it becomes available. Check the Last Updated date given below.

            Eventually, each issue will be reused on the separate Ajabbi Research website as an introduction to a research area comprising multiple research projects.

            Resources

            References

            • Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA) 1.2, W3C, 6 June 2023.
            • Web Content Accessibility Guidelines (WCAG) 2.2, W3C, 12 December 2024.
            • GOV.UK Design System.

            Repository

            • Home > Ajabbi Research > Library >
            • Home > Handbook > 

            Last Updated

            6/03/2026

            The Accessibility Issue

            By: Mike Peters
            Ajabbi Research: 6/02/2026

            Mike is the inventor and architect of Pipi and the founder of Ajabbi.

            This is the story of the effort to make Pipi fully accessible to all who need it. The steps taken have been part of Pipi's development since 2005, spanning 5 versions.

            The NZERN Pipi 2003-2005 Development Plan started it all.

            Pipi 4 (2005-2008)

            The story starts with Pipi 4. It was a big, successful system that supported community-driven Ecological Restoration in NZ. Here is a history of that Pipi version.

            During that time, New Zealand (NZ) had dial-up modems. Many NZERN members were working farmers in rural areas, with very slow internet. Many were older with low computer literacy. This was a major factor determining what was possible. Web page sizes had to be kept under 16kb.

            Recently, an archive of Pipi 4 help documentation was discovered and is now available for viewing. It is incomplete, but it gives an idea of how it worked.

            Here is the description taken from the Pipi 4 Help archive. The Screen Reader Edition was designed for the blind members of NZERN by their family members.

            PIPI4 is available in four editions to meet the needs of different groups of NZERN members.

            Basic Edition

              • Designed for the novice computer user who wants a simple cut-down system, with instructions built into every step.
              • Skill level required: Capable of using a simple program like Outlook Express
              • Availability: All members of NZERN

            Standard Edition

              • Designed for the confident computer user who wants a system with help available with one click. The user can ask questions and report bugs to the help desk.
              • Skill level required: Capable of using a program like Microsoft Word
              • Availability: All members of NZERN

            Screen Reader Edition

              • Designed for the confident computer user who uses a screen reader and wants help available with one click. The user can ask questions and report bugs to the help desk.
              • Skill level required: Capable of using a program like Microsoft Word
              • Availability: All members of NZERN

            Professional Edition

              • Designed for the expert computer user capable of self-learning, who wants a fast system with detailed technical documentation available with one click. The user will provide support to other members as a member of the help desk.
              • Skill level required: Capable of using an advanced program like Adobe Photoshop
              • Availability: All members of the help desk

              Pipi 6 (2017-2019)

              When Pipi was rebuilt from memory, some work was done to prepare for a more modular, standardised model-driven User Interface (UI) approach. Metadata was added to every database table to enable future personalisation and meet accessibility requirements.

              Pipi 7 (2020)

              Small, simple, static HTML mockups of workspaces were created as experiments.

              Pipi 8 (2021-2022)

              System-wide namespaces were implemented to enable future complex automated interactions.

              Pipi 9 (2023-2026)

              In 2023, a year-long investigation into model-driven interfaces led to the reuse and hacking of several abandoned EU research efforts in Human-Computer Interaction (HCI).

              Putting a User Interface (UI) on the front end of Pipi 9 was challenging. It had to be

              • Model-driven
              • Adaptive to the users' devices
              • Automated
              • Meet the individual needs of each logged-on user

              Resources used

              1. OMG Interaction Flow Modelling Language (IFML)
              2. The CAMELEON References Framework (CRF)
              3. User Interface Description Language (UIDL)
              4. W3C Model-based UI Incubator

                Model-driven UI

                The User Interface Description Language (UIDL) was an EU-funded project that was abandoned in 2010 after 10 years of excellent work. It was to enable accessibility on different screens and devices. The research results were reverse-engineered to build a User Interface Engine (usi) that would run in reverse to generate accessibility solutions for Pipi. The CSS Engine (css) replaced some redundant components of the UIDL project. Additional engines for localisation and personalisation were created.


                UK Design System

                The UK Government has created a design system for building accessible websites. It includes many templates, components, tools, code, and guidance on achieving this. An excellent resource.

                These templates are being used for the Pipi-generated workspace User Interface (UI)

                Example


                A teaching customer

                Mr G, my coach from Startup Aotearoa, suggested finding a first customer who could be a teaching customer. What a good idea.

                As it happens, a new disability rights organisation emerged in response to funding cuts by the NZ government. The group led a national campaign that resulted in the Minister responsible for the cuts losing her job and the scale of the cuts being reduced. The group had no money and needed a large campaign website that was highly accessible for deaf and blind people. Helping lead this campaign and building the website were deep learning experiences for me.

                Pipi CMS Engine (cms)

                A decision was made early on to autogenerate a separate website for each language (English, Māori, NZ Sign Language, and AAC picture language). This was the simplest solution for the CMS and the users.

                Creating UI for each natural language, including sign languages (i18n), requires user requests and volunteer testers.

                The CMS uses a template engine that builds web pages from reusable components. This means that getting CCS correct only needs to be done once for each component, and so on.

                Sign Language

                The scheme was dreamed up to embed NZ Relay Video Interpreting onto any webpage. This is an ongoing experiment, driven by deaf people.

                Blind and Low Vision

                This didn't get far because blind people in NZ were needed to volunteer to help with testing. However, there are volunteers in other countries. This job depends on ongoing work on the CSS Engine (css). A particular challenge is catering for braille machines.

                Picture Language

                Professor Stephen Hawking used AAC via a computer-generated voice. There are many forms of AAC, including picture language. Providing this as a UI is being explored, with other AAC to follow. Important for the millions of people with Cerebral Palsy and Motor Neurone Disease.

                Workspace personalisation

                The workspace settings will offer complete personalisation of the UI. Similar in purpose to the wonderful AccessWidget from Accessibe.com. Instead of a pop-up, it will use a personalisation form in account settings.

                Keeping it simple

                On paper, WAI-ARIA looks great. However, the reality is that the growing interactive complexity of websites and differences in how browsers work mean that web pages break for people using assistive technology.

                Modern websites present a large attack surface, making them vulnerable. Pipi's solution is to focus on functionality, usability, and maximum simplicity. Small page sizes (Kb), semantic structure, and minimising JavaScript use.

                Standards

                The W3C Web Content Accessibility Guidelines (WCAG) sets the international standard for providing full accessibility. Pipi will endeavour to meet WAIG 2.2 as a new conformance target for all languages.

                Whats next

                Designing the workspaces has made accessibility through personalisation a top requirement. The ongoing 2026 workspace rollout will include further accessibility testing.

                The most useful and inspiring resource has been Smashing Magazine's weekly newsletter, which often covers accessible UI design in great depth.

                Dedication

                Those who have fought all their lives for a world where people with disabilities have equal rights and can fully participate without barriers to the extent they are capable.

                How Intel Gave Stephen Hawking a Voice

                Mike's Notes

                I hope that Pipi CMS can provide an AAC (picture language) interface as one of its accessibility options.

                …we have a moral duty to remove the barriers to participation, and to invest sufficient funding and expertise to unlock the vast potential of people with disabilities. - Stephen Hawking

                Resources

                References

                • Reference

                Repository

                • Home > Ajabbi Research > Library > Subject > Accessibility
                • Home > Handbook > 

                Last Updated

                05/02/2026

                How Intel Gave Stephen Hawking a Voice

                By: João Medeiros
                Wired: 13/01/2015

                João Medeiros is Features Director for Wired magazine. He was born in Portugal, and came to the UK at eighteen. He has a PhD in theoretical physics at Imperial College. He has written widely for publications including The Economist, GQ and Nature.

                Stephen Hawking first met Gordon Moore, the cofounder of Intel, at a conference in 1997. Moore noticed that Hawking’s computer, which he used to communicate, had an AMD processor and asked him if he preferred instead a “real computer” with an Intel micro-processor. Intel has been providing Hawking with customized PCs and technical support since then, replacing his computer every two years.

                Stephen Hawking

                Wired January 2015, Relates to special feature on Stephen Hawking, Hawking sits in his personalised special electric wheelchair, text in foreground from him screenMarco Grob/WIRED UK

                Interview

                There is a 17-minute interview behind the paywall.


                Other Notes

                The "Equalizer" is a 1980s computer program developed by Words Plus CEO Walter Woltosz to help his mother-in-law, who had ALS. It enabled Professor Stephen Hawking to communicate by selecting letters, words, and phrases on an Apple II computer via a hand switch, later upgraded to a cheek-switch sensor. 

                Key Details of the Equalizer:

                • Purpose: Developed to assist patients with ALS who lost the ability to speak and write.
                • Usage: Hawking utilized this software, later integrated onto his wheelchair, to produce up to 15 words per minute.
                • Operation: The user interface allowed for selecting words from a database or spelling them out, which were then converted to speech using a Speech Plus CallText 5010 synthesizer.
                • Development: Walter Woltosz co-founded Words Plus in 1981 and created the software to provide a voice for those with communication disabilities. 

                Stephen Hawking and the Technology that allowed him to continue his research18/03/2018

                Stephen Hawking, who sought to explain the origins of the universe, the mysteries of black holes and the prospect of time travel, died today aged 76. Hawkings body was ravaged by the wasting motor neurone disease (ALS) he developed age 21 and spent most of his life confined to his wheelchair.

                Hawking’s incredible mind probed the very limits of human understanding both in the vastness of space and in the sub-molecular world of quantum theory, which he claimed could predict what happens at the beginning and end of time.

                In his 2013 memoir “My Brief History” he explained how at first he “felt it was very unfair” and often questioned “why should this happen to me.” With time and technology, he went from concern that his life was over and his potential never realised to now, 50 years later, feeling quietly satisfied with his life and achievements.

                How Intel gave Hawking his voice.

                In 1986, aged 44, Hawking lost his voice to save his life after an attack of pneumonia. For a while, he used a spelling card to communicate, patiently indicating letters and forming words by raising his eyebrows. Although this gave Hawkings the ability to communicate the process was slow. From then on, he spoke through a computer synthesiser on the arm of his wheelchair.

                A chance encounter with Gordon Moore, the co-founder of Intel, at a conference in 1997 led to a relationship that would see Intel providing Hawking with customised PCs and technical support, replacing his computer every 2 years.

                Martin King, a physicist who had been working with Hawking on a new communication system, contacted a California-based company called Words Plus, whose computer program Equalizer allowed the user to select words and commands on a computer using a hand clicker. Words Plus CEO Walter Woltosz had created a earlier version of the speech equalizer to her help his mother-in-law who also suffered from ALS.

                Equalizer first ran on an Apple II computer linked to a speech synthesizer made by a company called Speech Plus. This system was then adapted by David Mason, the engineer husband of one of Hawking’s nurses, to a portable system that could be mounted on one of the arms of a wheelchair. With this new system, Hawking was able to communicate at a rate of 15 words per minute.

                However, the nerve that allowed him to move his thumbs kept degrading. By 2008, Hawking’s hand was too weak to use the clicker. His graduate assistant at the time then devised a switching device called the “cheek switch.” Attached to his glasses, it could detect, via a low infrared beam, when Hawking tensed his cheek muscle. Since then, Hawking has achieved the feat of writing emails, browsing the internet, writing books and speaking using only one muscle. Although this system worked it was still slow… enter SwiftKey. With SwiftKey integrated, the system could learn from Hawking and predict the characters and words he planned to type next based on historical patterns, with this data funnelled through to his speech synthesiser. SwiftKey has also tapped Hawking’s historical works to help it more accurately predict his next words in this bespoke version of the software.

                The technology that enabled Stephen Hawking to speak.

                As you might expect, it is not just one piece of equipment that is involved here. Many technologies combined to allow Hawking to communicate.

                • Lenovo Yoga 260 provided by Lenovo and Intel, Intel® Core™ i7-6600U CPU
                • 512GB Solid-State Drive
                • Windows 10
                • ACAT interface software provided by Intel

                Speech Synthesisers (3 copies):

                • Manufacturer – Speech Plus (Incorporated 1988, Mountain View, CA)
                • Model – CallText 5010
                • Speaker and amplifier provided by Sound Research
                • Permobil F3 wheelchair provided by Permobil

                It is undoubtedly the incredible technology that enabled Hawking to speak again that gave him the hope and drive to continue with his work. Hawking was an Ambassador of Science and showed us what determination looks like.

                What happened to Stephen Hawking?

                Stephen Hawking died on March 14, 2018, aged 76. In itself, an incredible achievement, but Stephen did much more than simply survive for 76 years. His life was an inspiration to so many people. Interestingly, he didn’t believe in God or the afterlife. He called heaven “a fairy story.”

                In his final, posthumous book “Brief Answers to the Big Questions.” he wrote “there is no God”. and “no one directs the universe.” He had disputed the existence of God for many years before his death.

                he wrote, “The question is: Is the way the universe began chosen by God for reasons we can’t understand, or was it determined by a law of science? I believe the second,”

                Hawking believed that “spontaneous creation” was the reason for existence, writing “it is not necessary to invoke God to light the blue touch paper and set the universe going.”

                He will be remembered for many years.

                Workspace Menu

                Mike's Notes

                Working draft for the outline of the workspace menu. Testing now, all subject to change.

                Update 11/12/2025

                The successful tests have led to changes to the engine, creating the tab menus.

                Resources

                References

                • Reference

                Repository

                • Home > Ajabbi Research > Library >
                • Home > Handbook > 

                Last Updated

                11/12/2025

                Workspace Menu

                By: Mike Peters
                On a Sandy Beach: 30/10/2025

                Mike is the inventor and architect of Pipi and the founder of Ajabbi.

                Every Workspace comes with several types of menus (explained here for left-to-right writing systems)

                • Every workspace has 3 Standard 1 menus to the left.
                • Each workspace has some unique Workspace-specific menus.
                • Some workspaces have one or more Context menus.
                • Every workspace has 3 Standard 2 menus to the right.

                Menu types

                • Standard 1
                  • Home
                  • File
                  • Edit
                • Workspace-specific
                  • Arrange
                  • Bookmarks
                  • Design
                  • Layout
                  • Presentation
                  • Network
                  • Translate
                  • etc
                • Context
                  • Data Model 
                  • Import Data
                  • Schema
                  • Freight Consignment
                  • etc
                • Standard 2
                  • View
                  • Window
                  • Help

                Menu hierarchy example

                • Home (Standard 1)
                  • Dashboard
                  • Preferences
                  • Workspaces

                • File (Standard 1)
                  • New
                  • Open
                  • ---------------
                  • Close
                  • Save
                  • Save As
                  • Revert
                  • Delete
                  • ---------------
                  • Page setup
                  • Print
                  • ---------------
                  • Info
                    • Versions
                  • Import
                  • Export
                  • ---------------
                  • Exit
                • Edit (Standard 1)
                  • Cut
                  • Copy
                  • Paste
                  • Clear
                  • Select All
                  • ---------------
                  • Show Clipboard
                • --------------------------------------------------------
                • Design (Workspace-specific)
                  • Font
                    • Font Type
                    • Font Size
                  • Paragraph
                  • Style
                  • Editing
                • Bookmarks (Workspace-specific)

                • Arrange (Workspace-specific)
                  •  
                • --------------------------------------------------------
                • Context 1 (Context)

                • Context 2 (Context)

                • Context 3 (Context)

                • --------------------------------------------------------
                • View (Standard 2)
                  • Show
                  • Zoom
                • Window (Standard 2)
                  • Dashboard
                    • Arrange
                  • Workspace
                  • Settings
                    • Language
                    • Acessibility
                    • Time Zone
                  • Updates
                • Help (Standard 2)
                  • Help
                  • Feedback
                    • Roadmap
                    • Vote
                    • Feature Request
                  • Support
                    • Forum
                    • Chat
                    • Office Hours
                    • Contact
                  • Training
                    • Docs
                    • How-to-guide
                    • Tutorials
                    • Reference
                  • About Pipi

                Menu Config Database

                Already built and tested. Stores all tab and tool definitions.

                Layout options

                The workspace menu UI will come in several layout options, mirroring popular platforms. People will be able to choose whatever they prefer in settings. DevOps account developers will be able to create more options for users to choose from. A quick survey of layout looks includes;

                • "Ribbon"
                • "Like Google Workspace"
                • Pipi 4
                • "Like Adobe"
                • "Like Service Now"
                • "Like Zoho"
                • "Like Odoo"
                • "Like Netsuite"
                • Accordions for mobile
                I personally prefer minimalist.

                Accessibility

                There will be menu UI options for screen readers, braille, and other accessibility features.

                Ribbon layout

                I'm working on the static ribbon version of the workspace menu. The CSS and working versions will use MetroUI CSS and HTMX.

                The workspace "ribbon-like" menu and tabs roughly follow standard conventions used by other software, so people don't get lost. With 3 context tabs reserved for any situation. The first draft will be used for running experiments.

                What's next

                Replace all 3,800 HTML Workspace files with the changes.

                Lots of trial-and-error experimenting follows. You can watch by visiting the workspace mockup.

                The design system docs will need to be updated.