Update index.md to mention that govuk-frontend javascript will auto-focus

[edwardhorsford]

The guidance makes it clear that the errorSummary should be focused on page load, but doesn't mention that this should happen for free with the govuk-frontend javascript.

Hopefully this makes it clearer so teams don't spend time trying to re-impliment this.

See similar PR on the NHS Service manual

Fixes #3818

[netlify]

✅ You can preview this change here:

Built without sensitive environment variables

Name	Link
🔨 Latest commit	5a9b45e
🔍 Latest deploy log	https://app.netlify.com/sites/govuk-design-system-preview/deploys/665744426942d50009aa62bd
😎 Deploy Preview	https://deploy-preview-3819--govuk-design-system-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[owenatgov]

Thanks for this Ed. There are a few examples of this where we tell a user to do something when, if govuk is imported properly, it'll just happen. There's a bigger piece of work to remove all of these but for now I wonder if the solution is to just remove this line entirely. Maybe add something saying what the component will do. What do you reckon @edwardhorsford?

[edwardhorsford]

Thanks for this Ed. There are a few examples of this where we tell a user to do something when, if govuk is imported properly, it'll just happen. There's a bigger piece of work to remove all of these but for now I wonder if the solution is to just remove this line entirely. Maybe add something saying what the component will do. What do you reckon @edwardhorsford?

If you remove the line, I'd make sure to note somewhere that the element should be focused on page load - and that the js should do that for you. I think focusing is disabled in the examples, and if a team were reimplementing they might not know.

[owenatgov]

After forgetting about this PR for a while I've decided on revision to approve it for now. As mentioned, there's a bigger task to remove wording like this from our guidance but this solve the immediate issue.

Needs a 2nd approval and then we're good to go.