Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The advice from jsx-a11y/accessible-emoji appears to lead to a degraded experience with assistive technologies #627

Closed
luke-john opened this issue Aug 1, 2019 · 2 comments · Fixed by #713
Assignees

Comments

@luke-john
Copy link

luke-john commented Aug 1, 2019

From some testing on os x with VoiceOver, it seems the guidance provided in the rule jsx-a11y/accessible-emoji leads to a degraded experience with the label not being announced to the user.

I've setup a codepen which demonstrates this at the following link.

https://codepen.io/anon/pen/ymoBgb

The rule seemed to have been created based on the advice in a blog post from a few years ago now, so perhaps browsers and assistive technologies have advanced since then.

https://github.com/evcohen/eslint-plugin-jsx-a11y/pull/136

@jessebeach
Copy link
Collaborator

@luke-john great suggestion. You're totally right. Emojis have evolved since this rule was created and it no longer makes sense. I'm going to deprecate this rule in the current version and we'll remove it in the next version.

@beefancohen
Copy link
Contributor

Thank you!!!!

trezy added a commit to trezy/trezy.com that referenced this issue Dec 1, 2020
It's currently breaking Markdown rendering, and my not be necessary at
all (ref: jsx-eslint/eslint-plugin-jsx-a11y#627)
backwardok added a commit to backwardok/eslint-plugin-jsx-a11y that referenced this issue Mar 25, 2021
The [accessible-emoji rule got marked as deprecated](jsx-eslint#713) to address jsx-eslint#627, but was never removed from the rule set.

This removes the rule from the strict and recommended lists and also updates the readme to reflect it being deprecated.
backwardok added a commit to backwardok/eslint-plugin-jsx-a11y that referenced this issue Mar 25, 2021
The [accessible-emoji rule got marked as deprecated](jsx-eslint#713) to address jsx-eslint#627, but was never removed from the rule set.

This removes the rule from the strict and recommended lists and also updates the readme to reflect it being deprecated.
ljharb pushed a commit to backwardok/eslint-plugin-jsx-a11y that referenced this issue Apr 6, 2021
The [accessible-emoji rule got marked as deprecated](jsx-eslint#713) to address jsx-eslint#627, but was never removed from the rule set.

This removes the rule from the strict and recommended lists and also updates the readme to reflect it being deprecated.
tbergquist-godaddy added a commit to adeira/universe that referenced this issue Sep 7, 2021
From some testing on os x with VoiceOver, it seems the guidance
provided in the rule jsx-a11y/accessible-emoji leads to a degraded
experience with the label not being announced to the user.

See [issue here](jsx-eslint/eslint-plugin-jsx-a11y#627)
tbergquist-godaddy added a commit to adeira/universe that referenced this issue Sep 7, 2021
From some testing on os x with VoiceOver, it seems the guidance
provided in the rule jsx-a11y/accessible-emoji leads to a degraded
experience with the label not being announced to the user.

See [issue here](jsx-eslint/eslint-plugin-jsx-a11y#627)
adeira-github-bot pushed a commit to adeira/eslint-config-adeira that referenced this issue Sep 7, 2021
From some testing on os x with VoiceOver, it seems the guidance
provided in the rule jsx-a11y/accessible-emoji leads to a degraded
experience with the label not being announced to the user.

See [issue here](jsx-eslint/eslint-plugin-jsx-a11y#627)

adeira-source-id: 62caa5f8212b2e108dbe5d57a44e0ad4aaae55f1
ditsuke added a commit to ditsuke/prep-project-jan-2022 that referenced this issue Jan 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants