Skip to content

Accessibility issue for some key identifier names #63

@swar-mukh

Description

@swar-mukh

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[X] Documentation issue or request
[X] Support request
[ ] Other... Please describe:

Current behavior

All current examples demonstrate key bindings (including screenshots) relative to MacOS key-bindings.

Expected behavior

Make README.md/documentation more accessible by providing examples from other platforms as well. The README.md although mentions:

Hotkeys take care of transforming keys from macOS to Linux and Windows and vice-versa.

it is not immediately clear (at least to me), that should one be using exclusive Mac key-bindings that internally translate that to the host platform, or that providing strings like super, alt works equally well. If it is so, then I believe the API should not transform internally to ease code maintainability, but rather be explicit via API documentation and implement the same platform specific bindings via the API thereby easing the cognitive load on the end-developer.

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Not many developers have knowledge about Mac, let alone use it. A sizeable portion of the developer community still prefer using Windows. If dual-boot isn't affordable to use a Linux distro, then Windows Subsystem for Linux (WSL2) is preferred by attaching an X-Windows environment via Remote Desktop Protocol.

Alternatively, there exists Linux/BSD users, who neither know what meta nor Windows key is. They are comfortable using the term super key.

Environment


Angular version: 14.1.2


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
- [X] Immaterial to this context
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions