Alex Stine

Results 15 issues of Alex Stine

## What? Fixes #42285 Adds code to `TokenInput` to detect two things. 1. If it is the first render. This is determined by looking at the `value` variable. If one...

[Type] Bug
Accessibility (a11y)
[Package] Components
Needs Accessibility Feedback
[a11y] Keyboard & Focus

### Description When editing an existing post and you have at least 25 users to select from the post author combo box, focus is automatically placed on the combo box...

[Type] Bug
[Priority] High
Accessibility (a11y)
[Status] In Progress
Needs Dev
[Package] Components

**Describe the bug** This is an accessibility issue that happens when using the Audio Block in Gutenberg. Focus is not managed properly after the media library modal is closed or...

[Block] Audio

Fixes #6850 There is a label wrapped around the search input that contains `style="display:none;"`. This is useless and should be removed since this will not be read by screen readers...

Currently, the Open Search button is placed in a dedicated navigation landmark. One button does not need a dedicated landmark. This adds unnecessary clutter to the landmark structure and should...

Accessibility
[Block] Header & Footer

Please see the related thread in Slack: https://wordpress.slack.com/archives/C02QB8GMM/p1681178996567369 > Who maintains this page? > https://wordpress.org/five-for-the-future/ > There is a need for slightly more descriptive link text. Looks like this is...

[Status] Needs Design
Accessibility

### Description After inserting a list block, it appears that the DOM is modified leaving only one button. This makes all other block insert options unreadable to screen reader users...

[Type] Bug
[Priority] High
[Focus] Accessibility (a11y)
[Feature] Inserter

From: #245 Page: https://wordpress.org/blocks Heading 2: Build without limits 1. Can probably remove the ALT text on the block icons. They are decretive and do not add value to the...

[Status] Needs Design Feedback
Accessibility
[Component] Content
[Section] Blocks

## What? Fixes https://github.com/WordPress/gutenberg/issues/61315 This was a hard bug to unravel. Essentially, every time a user types into a `RichText` field, we're building some type of virtual tree in memory....

[Type] Bug
[Focus] Accessibility (a11y)
[Feature] Rich Text
[Package] Block library
Needs Accessibility Feedback
[Package] Rich text
[Package] Block editor
[Block] Navigation Link

Test page: https://learn.wordpress.org/test/wordpress-playground-block-plugin-test-page/ From the button labels alone, I cannot tell the difference between what these buttons will do. Let's start with answering that question and then I can guide...

Bug
Playground block
Accessibility