Accessibility optimization for search form in customer portal

[t3it-development]

• The search form (Ticket, FAQ) in the customer portal must include a role attribute and an appropriate aria-label to ensure accessibility.
• The search form (Ticket, FAQ) in the customer portal must be fully accessible via keyboard navigation.

Current Code:
<form action="/otobo/customer.pl" method="post" name="compose"> <input type="hidden" name="ChallengeToken" value="t0tGBmolm7dPQLhwKiMLvJdC7ejS6Hck"> <input type="hidden" name="Action" value="CustomerTicketOverview"> <input type="hidden" name="Subaction" value="Search"> <h3 class="ooog"> <i class="ooofo ooofo-search"></i> <input type="text" name="Fulltext" id="oooSearch" title="Ticketsuche" class=""> <span id="oooSearchLabel">Ticketsuche</span> </h3> </form>

[t3it-development]

Additional PR for FAQ Package: RotherOSS/FAQ#53

[stefanhaerter]

Hi @t3it-development,

thanks for this report and the provided PRs as well. we will look into this.

Kind regards,
Stefan

[stefanhaerter]

Regarding the change of input type, it might be interesting to know the differences between search and text.

To me, this looks like a good suggestion.