Difference between revisions of "PinePhone Accessibility"
(fixes) |
|||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
Although most accessibility support is implemented in software, the underlying hardware is still relevant. | Although most accessibility support for the [[PinePhone]] and [[PinePhone Pro]] is implemented in software, the underlying hardware is still relevant. This page discusses some issues and options. | ||
This page discusses some issues and options. | |||
= Input = | == Input == | ||
== Braille == | === Braille === | ||
Various portable devices, such as Apple's iPhone, support braille input. | Various portable devices, such as Apple's iPhone, support braille input. | ||
| Line 16: | Line 15: | ||
Indeed, there is a bit of space left over for control functions, etc. | Indeed, there is a bit of space left over for control functions, etc. | ||
== Keyboard == | === Keyboard === | ||
The PinePhone can support either Bluetooth or USB keyboards. | The PinePhone can support either Bluetooth or USB keyboards. | ||
| Line 23: | Line 22: | ||
might be a reasonable input device. | might be a reasonable input device. | ||
== Speech == | === Speech === | ||
The PinePhone should be able to accept speech input using either Bluetooth or its built-in microphone. | The PinePhone should be able to accept speech input using either Bluetooth or its built-in microphone. | ||
| Line 30: | Line 29: | ||
Mozilla's DeepSpeech ASR (automatic speech recognition) engine works pretty well on a Raspberry Pi 4, | Mozilla's DeepSpeech ASR (automatic speech recognition) engine works pretty well on a Raspberry Pi 4, | ||
using only a single core. | using only a single core. | ||
Assuming that the PinePhone's limited (3 GB) RAM isn't a constraint, | Assuming that the PinePhone's more limited (2 or 3 GB) RAM isn't a constraint, | ||
the phone should be able to produce similar results. | |||
= Output = | == Output == | ||
== Speech == | === Speech === | ||
The PinePhone's processor should have plenty of capacity to generate clear speech. | The PinePhone's processor should have plenty of capacity to generate clear speech. | ||
This can be output using either the 3.5 mm audio jack or a Bluetooth connection. | This can be output using either the 3.5 mm audio jack or a Bluetooth connection. | ||
== See also == | |||
* [https://wiki.postmarketos.org/wiki/Accessibility postmarketOS wiki: Accessibility] | |||
[[Category:PinePhone]] | |||
Latest revision as of 00:35, 16 March 2023
Although most accessibility support for the PinePhone and PinePhone Pro is implemented in software, the underlying hardware is still relevant. This page discusses some issues and options.
Input
Braille
Various portable devices, such as Apple's iPhone, support braille input. This uses multi-touch capability on the device's capacitative touch screen. The gating factors for this input mode are the dimensions of the screen and the number of contact points that can be distinguished.
The PinePhone screen has 1440 × 720 pixel resolution and measures 5.95" diagonally. Assuming that the pixels are square, the screen dimensions should be about 2.68" by 5.37". This should provide plenty of room for four fingertips on each of the long sides. Indeed, there is a bit of space left over for control functions, etc.
Keyboard
The PinePhone can support either Bluetooth or USB keyboards. So, a device such as the Jelly Comb Foldable Bluetooth Keyboard B003 might be a reasonable input device.
Speech
The PinePhone should be able to accept speech input using either Bluetooth or its built-in microphone. According to this page, Mozilla's DeepSpeech ASR (automatic speech recognition) engine works pretty well on a Raspberry Pi 4, using only a single core. Assuming that the PinePhone's more limited (2 or 3 GB) RAM isn't a constraint, the phone should be able to produce similar results.
Output
Speech
The PinePhone's processor should have plenty of capacity to generate clear speech. This can be output using either the 3.5 mm audio jack or a Bluetooth connection.