Alex Stine
@alexstine on WordPress.org and Slack
Interests
WordPress Origin Story
Contributions
- Member Since: July 30th, 2016
- Location: Plano, TX, United States
- Website: alexstine.com
- GitHub: alexstine
- Job Title: Sr. Accessibility Specialist
- Employer: JPMorgan Chase
Contribution History
Alex Stine’s badges:- Accessibility Team
- bbPress Contributor
- Core Contributor
- Meta Contributor
- Training Contributor
- WordCamp Organizer
- WordCamp Speaker
-
Mentioned in [59628] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59627] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59626] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59625] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59624] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59623] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59622] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59618] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59615] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59614] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59613] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59612] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59611] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59610] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59609] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59608] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Mentioned in [59601] on Core SVN:
Build/Test Tools: Use Git when fetching the WordPress Importer for use in tests. -
Closed issue #292 on the WordPress/playground-tools repository:
Playground block: A11Y: Remove duplicate main landmarks -
Closed issue #286 on the WordPress/playground-tools repository:
Playground block: A11Y: Unlabeled button in code editor -
Closed issue #288 on the WordPress/playground-tools repository:
Playground block: A11Y: Use better labels for buttons -
Closed issue #289 on the WordPress/playground-tools repository:
Playground block: A11Y: Use correct ARIA specification for autocomplete -
Mentioned in [58450] on Core SVN:
Editor: A11y: Set ARIA attributes for Classic Editor link inserter. -
Created issue #293 in the WordPress/playground-tools repository:
Playground block: A11Y: Add skip links for loaded preview/iFrame -
Created issue #292 in the WordPress/playground-tools repository:
Playground block: A11Y: Remove duplicate main landmarks -
Created issue #291 in the WordPress/playground-tools repository:
Playground block: A11Y: Powered by link needs spacing -
Created issue #290 in the WordPress/playground-tools repository:
Playground block: A11Y: Difference between "Run" and "Activate Live Preview"? -
Created issue #289 in the WordPress/playground-tools repository:
Playground block: A11Y: Use correct ARIA specification for autocomplete -
Created issue #288 in the WordPress/playground-tools repository:
Playground block: A11Y: Use better labels for buttons -
Created issue #286 in the WordPress/playground-tools repository:
Playground block: A11Y: Unlabeled button in code editor -
Created issue #61604 in the WordPress/gutenberg repository:
Inserter: After inserting a list block, options no longer read -
Merged pull request #61505 into WordPress/gutenberg:
Add link to VS Code Playwright Extension -
Submitted pull request #61374 to WordPress/gutenberg:
RichText: Do not focus the input unless user is in an editing... -
Closed issue #61177 on the WordPress/gutenberg repository:
Small Typo Change in class-gutenberg-rest-templates-controller-6-6.php file -
Closed pull request #59716 on WordPress/gutenberg:
Hide save panel button isntead of removing when save panel is open -
Merged pull request #59622 into WordPress/gutenberg:
Make save panel a dialog with proper labels, fix site editor focus... -
Submitted pull request #59622 to WordPress/gutenberg:
Make save panel a dialog with proper labels, fix site editor focus... -
Closed pull request #56560 on WordPress/gutenberg:
Add block toolbar as a navigable region -
Mentioned in [57713] on Core SVN:
Site icon: Polish up Site Icon on the general settings screen. -
Mentioned in [57708] on Core SVN:
Toolbar: Accessibility: Keyboard navigation for screen readers. -
Closed issue #56263 on the WordPress/gutenberg repository:
Details block: impossible to get out from block, using a keyboard -
Merged pull request #58903 into WordPress/gutenberg:
Details block: Try double enter to escape inner blocks -
Submitted pull request #58903 to WordPress/gutenberg:
Details block: Try double enter to escape inner blocks -
Created issue #58902 in the WordPress/gutenberg repository:
Too much memory usage on build -
Mentioned in [57346] on Core SVN:
Editor: update npm packages in trunk for 6.4.3. -
Mentioned in [57258] on Core SVN:
Editor: update npm packages in trunk for 6.4.3. -
Wrote a comment on the post Update on Matrix Migration: Pausing the Transition, on the site WordPress.org Project:
Thanks @akirk. Hopefully Element will grow to be a suitable replacement for Slack one of… -
Wrote a comment on the post Embracing Matrix for Enhanced Communication, on the site WordPress.org Project:
Not happy about this. “Toward the end of December, posting to Slack will become more… -
Merged pull request #56834 into WordPress/gutenberg:
copy/fix capitalization of WordPress -
Closed issue #56188 on the WordPress/gutenberg repository:
Site editor: Fix the document title announcement for screen readers