We will also have to localise our route too. I believe this task is just o st it up right?

@Collins this ticket was resolved, and I do not understand why another patch was created for it. Please, I would appreciate some clarity as to what I am not doing right when making a patch

@Collins created the ticket here

I just finished documenting the controllers using JS Docs. I would love to work on it.

@Collins @Collins, I checked the patch and even downloaded it. All that was trashed is
Met requirement

• Heading Hierarchy: You have excellent structure (h1 -> h2 -> h3) across all pages.
• Alt Text: All img tags utilise dynamic alt text (e.g., alt={actor.name ?? "actor image"}).
• Search Component Accessibility: This is the strongest part of the code, implemented role="combobox", aria-expanded, aria-activedescendant patterns, and sr-only labels correctly.
• Semantic HTML: Good use of <main>, <nav>, <header>, and <footer>.

@Collins was going through the codebase and realised this ticket has not been completed.
I have reviewed the codebase against the ticket requirements. While the semantic HTML structure and ARIA implementation in the Search component are excellent, several acceptance criteria listed in the Description and Setup Steps are not fully met.

@Collins I would love to pick up this task. I started something like this when I was working on the query builder.

I would love to work on this

@Pppery, I am sorry for reopening this. I do not have your user name on the channel. Please, I have my team mates who have not had access yet. Please, can I provide you with a list of their names so you can authenticate

@Pppery I still have not been granted access

I am currently working on this