Skip to content

SEO: Improve dashboard keyboard and screen reader access - #55278

Draft
chrisbliss18 wants to merge 1 commit into
trunkfrom
fix/seo-2035-accessibility
Draft

chrisbliss18 wants to merge 1 commit into
trunkfrom
fix/seo-2035-accessibility

Conversation

@chrisbliss18

Copy link
Copy Markdown
Contributor

This is a work in progress. Safari and VoiceOver verification is still needed.

Proposed changes

  • Give each SEO tab an associated panel and keep keyboard focus on the selected tab when navigation changes the route.
  • Include the visible metric and action in the Overview coverage ring's accessible name. Add headings for Content and the inspector preview, and hide decorative card icons from assistive technology.
  • Name each Content edit button by post title. Move focus into the inspector on open and return it to the row on close. Preserve the current filter and return focus to Content if a save removes the edited row from the table.
  • Keep focused rows clear of the sticky headers and pagination. Add a focus outline to the inspector's Schema type select.
  • Make the GEO enhancer switch easier to target and keep the explanations for locked Settings and GEO controls visible alongside the controls.

The populated Content table still has a dangling description reference in the shared DataViews table implementation. That needs a fix in Gutenberg.

Related product discussion/links

Does this pull request change what data or activity we track or use?

No.

Testing instructions

  1. Open the SEO dashboard on a site with SEO tools enabled. Use the keyboard to move between Overview, Content, GEO, and Settings. Check that focus lands on the selected tab after activation and that the next Tab moves into its panel.
  2. On Overview, focus a coverage ring for a field that some posts are missing. Verify its focus indicator and tooltip, then activate it and check that Content opens with the matching filter.
  3. On a Content table with enough posts to paginate, Tab and Shift+Tab through post links and edit buttons. Check that the focused row stays visible and pagination still works. Repeat with a narrow viewport.
  4. Open Edit SEO for a row. Check that focus moves into the inspector and that the Schema type select has a visible outline. Close the inspector and check that focus returns to the same row with the filter intact. Save a change that removes a row from the current filter and check that focus returns to the Content tab.
  5. On GEO, use the keyboard to expand a crawler group. On a site with the AI SEO Enhancer available, verify that its switch has a visible focus indicator and responds to Space. In Settings and GEO, check that explanations are available when privacy settings lock controls.
  6. In Safari with VoiceOver, repeat the tab, coverage ring, and inspector flows. Check the headings rotor, the selected tab and panel, the post-specific Edit SEO names, and what is announced when the inspector opens and closes.

@github-actions

github-actions Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the fix/seo-2035-accessibility branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack fix/seo-2035-accessibility

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@github-actions github-actions Bot added [Package] Seo [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] In Progress [Tests] Includes Tests labels Nov 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • 🔴 Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖


Follow this PR Review Process:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

@github-actions github-actions Bot added the [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. label Nov 19, 2026
@jp-launch-control

Copy link
Copy Markdown

Code Coverage Summary

Coverage changed in 1 file.

File Coverage Δ% Δ Uncovered
projects/packages/seo/routes/content/inspector.tsx 8/10 (80.00%) -8.89% 1 ❤️‍🩹

Full summary · PHP report · JS report

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Package] Seo [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Status] In Progress [Status] Needs Author Reply We need more details from you. This label will be auto-added until the PR meets all requirements. [Tests] Includes Tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant