Re:Chromebook accessibility: Changing the order of mouse but...
by eganist on Thursday January 03, 2019 @09:36AM
(#18815342)
> The absence of a desired feature is not a bug
Considering the adoption of Chromebooks in government and public education spaces, Section 508 might disagree.
I'm not a 508 expert, though. I pulled up the spec and though there isn't anything specific about remapping buttons on mice, I did find this:
> 502.3.13 Modification of Focus Cursor. Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.
It would seem, then, that the actual buttons mapped for accomplishing the above MUST be modifiable or remappable for 508 compliance.
Considering the adoption of Chromebooks in government and public education spaces, Section 508 might disagree.
I'm not a 508 expert, though. I pulled up the spec and though there isn't anything specific about remapping buttons on mice, I did find this:
> 502.3.13 Modification of Focus Cursor. Focus, text insertion point, and selection attributes that can be set by the user shall be capable of being set programmatically, including through the use of assistive technology.
It would seem, then, that the actual buttons mapped for accomplishing the above MUST be modifiable or remappable for 508 compliance.
But I'm probably wrong. Someone check me on it:
https://www.access-board.gov/guidelines-and-standards/commun...
---
Edit: commented directly on the feature thread. https://bugs.chromium.org/p/chromium/issues/detail?id=221914...