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

FontSizePicker accessibility issues #28411

Closed
talldan opened this issue Jan 22, 2021 · 3 comments
Closed

FontSizePicker accessibility issues #28411

talldan opened this issue Jan 22, 2021 · 3 comments
Labels
[Feature] Component System WordPress component system [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Regression Related to a regression in the latest release

Comments

@talldan
Copy link
Contributor

talldan commented Jan 22, 2021

Description

#27594 was recently merged. The new components are behind a flag and won't ship to core, but I noticed a few accessibility issues that will need to be resolved.

  • The font size select doesn’t announce whether it’s collapsed or not when focused
  • When opened, the font size picker relays the incorrect amount of items
  • The reset button is skipped in tab order when typing in a custom font size for the first time, as it only becomes enabled when focus leaves the input

I haven't tested using NVDA, would be good to get someone with good experience of accessibility testing to do a more thorough test.

Step-by-step reproduction instructions

With Voiceover active

  1. Add a paragraph block
  2. Navigate to the Block Inspector
  3. Tab to the Font Size Picker dropdown
  4. Note that the collapsed/expanded state wasn't read by VO
  5. Open the Font Size Picker dropdown
  6. Note that the number of items read by VO is incorrect, and the first focused item seems to have an index of 2
  7. Press escape to dismiss the dropdown and tab to the Custom Font Size input
  8. Enter a value, tab to the reset button
  9. Note that the reset button was bypassed in the tab order.

WordPress information

  • WordPress version: 5.6
  • Gutenberg version: 9.8
  • Are all plugins except Gutenberg deactivated? Y
  • Are you using a default theme (e.g. Twenty Twenty-One)? Y (2021)

Device information

  • Device: Desktop
  • Operating system: Mac OS
  • Browser: Safari with Voiceover
@talldan talldan added [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Regression Related to a regression in the latest release [Feature] Component System WordPress component system labels Jan 22, 2021
@ItsJonQ
Copy link

ItsJonQ commented Jan 22, 2021

@talldan Haiii! I created a PR for this earlier today :)

Would you be able to see if this helps?
#28408

@diegohaz
Copy link
Member

Tested with NVDA and JAWS. I could reproduce the same behaviors, except that they announce the correct number of items (1 of 7).

@talldan
Copy link
Contributor Author

talldan commented Jul 26, 2024

Outdated, the component is quite different today.

@talldan talldan closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Feature] Component System WordPress component system [Focus] Accessibility (a11y) Changes that impact accessibility and need corresponding review (e.g. markup changes). [Type] Regression Related to a regression in the latest release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants