Skip to content

fix(examples/with-elasticsearch): improve page metadata and accessibi… - #96710

Open
niketchandivade wants to merge 1 commit into
vercel:canaryfrom
niketchandivade:fix/with-elasticsearch-page-metadata
Open

fix(examples/with-elasticsearch): improve page metadata and accessibi…#96710
niketchandivade wants to merge 1 commit into
vercel:canaryfrom
niketchandivade:fix/with-elasticsearch-page-metadata

Conversation

@niketchandivade

Copy link
Copy Markdown
Contributor

What?

This PR improves the with-elasticsearch example by updating its page metadata and making the connection status more accessible.

Changes

  • Update the page title from Create Next App to Next.js with Elasticsearch.
  • Update the meta description to describe the Elasticsearch example instead of the default Create Next App text.
  • Add aria-live="polite" to the connection status container so status updates are announced by assistive technologies.

Why?

The example was still using the default metadata generated by Create Next App, which doesn't accurately describe the project.

Additionally, marking the connection status as a polite live region improves accessibility by allowing screen readers to announce status changes without interrupting the current interaction.

Testing

  • Verified the updated page title appears in the browser tab.
  • Verified the updated meta description is rendered in the page source.
  • Verified the connection status container includes aria-live="polite" and the page behavior remains unchanged.

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 this pull request may close these issues.

1 participant