-
Notifications
You must be signed in to change notification settings - Fork 33
Same size for <h1> elements and <h2> elements #3958
Copy link
Copy link
Open
Labels
area/accessibilityrelated to WCAG and accessibilityrelated to WCAG and accessibilitykind/questionQuestions raised should be labeled with this.Questions raised should be labeled with this.squad/utformingIssues that belongs to the named squad.Issues that belongs to the named squad.status/for-considerationIssues that will be considered for future deliveriesIssues that will be considered for future deliveriesstatus/triage
Description
Metadata
Metadata
Assignees
Labels
area/accessibilityrelated to WCAG and accessibilityrelated to WCAG and accessibilitykind/questionQuestions raised should be labeled with this.Questions raised should be labeled with this.squad/utformingIssues that belongs to the named squad.Issues that belongs to the named squad.status/for-considerationIssues that will be considered for future deliveriesIssues that will be considered for future deliveriesstatus/triage
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
No status
Question
We have created an application using Altinn Studio and set the
appNamefield to reflect the application's name.When we reviewed the accessibility requirements for our clients using standard WCAG tools, we noted that the sizing of the
<h1>tag produced for theappNameand our subsequent<h2>elements had the same size.Looking into the code, the element Header.tsx that
<h1>is coded to themdsize, and that the largest header size for a header provided by theHeaderComponentis<h2>that is sized tomd. HeaderComponent.tsxIs this by design?
Note: Sizing down to
<h3>is not optimal as tools such as WAVE will complain that the headers are skipped.Additional Information
No response