Callouts and Text with Optional Headers | Voters

Callouts and Text with Optional Headers

complete

Christina Goodland

When our contributors use these components, they don't understand that the headers are coded as heading 2s or heading 4s, etc., so they do not use headings in the correct semantic order, which is an accessibility issue.

November 19, 2020

Dimitri Tadege

marked this post as

complete

Dimitri Tadege

marked this post as

in progress

Sara Froehlich

marked this post as

under review

Sara Froehlich

Thanks, Christina for submitting this as an issue. We will discuss it with the Folwell team to determine any next steps.

Jacqueline Quintanilla

Sara Froehlich: Regardless of where Folwell lands in regards to solving this, I'm interested in the reasoning behind it. We have many custom components and layouts with optional headers and we do not currently have a good way to handle this either.