# Landmark tagging for screen reader accessibility

**URL:** <https://community.evolveauthoring.com/t/landmark-tagging-for-screen-reader-accessibility/2133>\
**Category:** General Help\
**Created:** [February 6, 2023, 10:37am UTC](https://community.evolveauthoring.com/t/landmark-tagging-for-screen-reader-accessibility/2133 "2023-02-06T10:37:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![LaurynS](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/lauryns/32/1967_2.png) [@LaurynS](https://community.evolveauthoring.com/u/LaurynS)\
**Post date:** [February 6, 2023, 10:37am UTC](https://community.evolveauthoring.com/t/landmark-tagging-for-screen-reader-accessibility/2133/1 "2023-02-06T10:37:13Z")

</div>

I’ve recently had a course put through an accessibility test and it flagged that components like open input and links have a “complementary” tag rather than a “main” landmark tag. This isn’t ideal when a link is being used as a main navigation button to go to another page.

I was totally ignorant to the existence of these tags until this test, so I did some research. Since this is controlled in the html of the website itself, and I dont see any obvious settings in evolve, is this something that I can edit/control?

---

<div class="post-metadata">

**Author:** ![BarryBPS](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/barrybps/32/540_2.png) [@BarryBPS](https://community.evolveauthoring.com/u/BarryBPS)\
**Post date:** [February 6, 2023, 11:54am UTC](https://community.evolveauthoring.com/t/landmark-tagging-for-screen-reader-accessibility/2133/2 "2023-02-06T11:54:31Z")

</div>

Hi Lauryn, I’m going to follow this conversation.

Many thanks,

Barry

---

<div class="post-metadata">

**Author:** ![LaurynS](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/lauryns/32/1967_2.png) [@LaurynS](https://community.evolveauthoring.com/u/LaurynS)\
**Post date:** [February 6, 2023, 12:06pm UTC](https://community.evolveauthoring.com/t/landmark-tagging-for-screen-reader-accessibility/2133/3 "2023-02-06T12:06:13Z")

</div>

After further looking it seems this might’ve been fixed in a recent update for links component, but its still present in the open input component

---

<div class="post-metadata">

**Author:** ![Matt\_Leathes](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/matt_leathes/32/586_2.png) [@Matt\_Leathes](https://community.evolveauthoring.com/u/Matt_Leathes)\
**Post date:** [February 7, 2023, 2:20pm UTC](https://community.evolveauthoring.com/t/landmark-tagging-for-screen-reader-accessibility/2133/4 "2023-02-07T14:20:41Z")

</div>

Hi @LaurynS the only time I can see a ‘complementary’ role being added to anything in Evolve is on a Block when it has an ARIA label set.

This does seem an odd use of that particular role - I will investigate and remove if it’s not there for a good reason.

---

<div class="post-metadata">

**Author:** ![LaurynS](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/lauryns/32/1967_2.png) [@LaurynS](https://community.evolveauthoring.com/u/LaurynS)\
**Post date:** [February 7, 2023, 2:42pm UTC](https://community.evolveauthoring.com/t/landmark-tagging-for-screen-reader-accessibility/2133/5 "2023-02-07T14:42:31Z")

</div>

Thank you so much! That has resolved the issue, I didn’t realise there was an aria label sitting in the block. Good to know how evolve implements those tags.

---

<div class="post-metadata">

**Author:** ![Matt\_Leathes](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/matt_leathes/32/586_2.png) [@Matt\_Leathes](https://community.evolveauthoring.com/u/Matt_Leathes)\
**Post date:** [February 7, 2023, 3:29pm UTC](https://community.evolveauthoring.com/t/landmark-tagging-for-screen-reader-accessibility/2133/6 "2023-02-07T15:29:25Z")

</div>

No problem!

Digging into the code it looks like it will apply ‘article’ to an Article with an aria-label, ‘complementary’ to a Block with an aria-label and ‘region’ to a component with an aria-label.

It was already on my list to review the use of ‘region’ next time I do some more work on accessibility, I’ll make a note to check the other two as well.
