🔧 Page h1 focusability

[tesk9]

Context

Fixes A11-3182

🖼️ What does this change look like?

Component completion checklist

• I've gone through the relevant sections of the Development Accessibility guide with the changes I made to this component in mind
• Changes are clearly documented
  • Component docs include a changelog
  • Any new exposed functions or properties have docs
• Changes extend to the Component Catalog
  • The Component Catalog is updated to use the newest version, if appropriate
  • The Component Catalog example version number is updated, if appropriate
  • Any new customizations are available from the Component Catalog
  • The component example still has:
    • an accurate preview
    • valid sample code
    • correct keyboard behavior
    • correct and comprehensive guidance around how to use the component
• Changes to the component are tested/the new version of the component is tested
• Component API follows standard patterns in noredink-ui
  • e.g., as a dev, I can conveniently add an nriDescription
  • and adding a new feature to the component will not require major API changes to the component

[linear]

A11-3182 Update Nri.Ui.Page to add an ID and tabindex="-1" to the H1

https://noredink-ui.netlify.app/#/doodad/Page

Purpose: In case we use this in a SPA and someone needs to move focus to the heading, as we've instructed them to do in the ATNC guide

[github-actions]

🤖 root//:elm_format_diffs has suggestions for 1 file.

To fix, run script/buck2 run //:diff_to_comment -- --fix root//:elm_format_diffs in your local checkout or apply the attached suggestions!

Have a very stylish day!

Addressed