ErrorSummary: Remove aria-attributes

[HalvorHaugan]

Description

Closes https://github.com/navikt/team-aksel/issues/637

Component Checklist 📝

• JSDoc
• Examples
• Documentation
• Storybook
• Style mappings (@navikt/core/css/config/_mappings.js)
• Component tokens (@navikt/core/css/tokens.json)
• CSS class deprecations (@navikt/aksel-stylelint/src/deprecations.ts)
• Exports (@navikt/core/react/src/index.ts and @navikt/core/react/package.json)
• New component? CSS import (@navikt/core/css/index.css)
• Breaking change? Update migration guide. Consider codemod.
• Changeset (Format: <Component>: <gitmoji?> <Text>. E.g. "Button: ✨ Add feature xyz.")

[changeset-bot]

🦋 Changeset detected

Latest commit: 73214f0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages

Name	Type
@navikt/ds-react	Patch
@navikt/ds-css	Patch
@navikt/ds-tokens	Patch
@navikt/ds-tailwind	Patch
@navikt/aksel-icons	Patch
@navikt/aksel	Patch
@navikt/aksel-stylelint	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Storybook demo

986456f8a | 90 komponenter | 141 stories

[KenAJoh]

Do we gain anything by removing section + removing aria-labelledby connection? Do we consider the section/region semantics redundant for screen-readers since the heading is the same?

[HalvorHaugan]

Do we gain anything by removing section + removing aria-labelledby connection? Do we consider the section/region semantics redundant for screen-readers since the heading is the same?

We avoid that some screen readers reads the heading twice (once as the section name, and once as the heading). @mortentollefsen and @it-vegard discussed this on Monday, and as I remember it, there wasn't really any strong arguments on either side.

[it-vegard]

Do we gain anything by removing section + removing aria-labelledby connection? Do we consider the section/region semantics redundant for screen-readers since the heading is the same?

We avoid that some screen readers reads the heading twice (once as the section name, and once as the heading). @mortentollefsen and @it-vegard discussed this on Monday, and as I remember it, there wasn't really any strong arguments on either side.

Most users will navigate by heading, so we don't give up a lot to avoid the double announcement. I would have liked having the section there if we continued to focus the section. When moving focus to the heading instead, the value of having the named section is almost gone. Only when navigating with reading mode would it still be useful, but even then the value is low.

Less aria is also <3