can u share me the repo for this task

Welcome @Shreyapedia! Please see https://www.mediawiki.org/wiki/New_Developers - thanks!
https://phabricator.wikimedia.org/project/profile/5563/

thanks, I have shared a PR please review it...
:)

@Charlie_WMDE I’d recommend keeping it as h1 as it’s the main title of the page, so semantically it should remain at the top of the heading hierarchy. HTML tags define the structure of the document, while the styling is handled by CSS. I believe this is important for things like accessibility, assistive technologies, and SEO?

If the title doesn't look correct, we can add classes such as text-h4 to the h1 tag so that it is styled correctly. I had a look on Figma but couldn't see a design for the contact page. Should we do the same as the Illegal content form, h4 style with a 16px bottom margin (text-h4 mb-4 classes)?

For reference, here are some useful links to Vuetify v2 classes that we can use to style elements:

• https://v2.vuetifyjs.com/en/styles/text-and-typography/
• https://v2.vuetifyjs.com/en/styles/spacing/

In T401820#11085279, @Shreyapedia wrote:

thanks, I have shared a PR please review it...
:)

@Shreyapedia please add Bug: <task number> (i.e. Bug: T401820 for this task) to your git commit footer so that changes are linked to Phabricator. Thanks

Shreya71703 opened https://github.com/wbstack/ui/pull/1029

Fix contact page heading alignment (Bug: T401820)

Shreya71703 closed https://github.com/wbstack/ui/pull/1029

Fix contact page heading alignment (Bug: T401820)

Some quotes from Mozilla's developer documentation to back up my previous comment that the title should remain a <h1> tag.

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/Heading_Elements#accessibility

Usage notes

• [...]
• Do not use heading elements to resize text. Instead, use the CSS font-size property.
• Do not skip heading levels: always start from <h1>, followed by <h2> and so on.

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/Heading_Elements#accessibility

Accessibility

Navigation

A common navigation technique for users of screen reading software is to quickly jump from heading to heading in order to determine the content of the page. Because of this, it is important to not skip one or more heading levels. Doing so may create confusion, as the person navigating this way may be left wondering where the missing heading is.