Project

General

Profile

Actions

Bug #92688

closed

Epic #89595: Improve accessibility of backend

Search result list is missing correct HTML markup and additional search information

Added by Martin Binder about 4 years ago. Updated 5 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend JavaScript
Target version:
-
Start date:
2020-10-23
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
Tags:
accessibility
Complexity:
Is Regression:
Sprint Focus:

Description

When you type text in the search input field and the search modal dialog appears with a list of search results. There are several accessibility issues with the search result.
If a visual presentation looks like a list, it should also have have HTML markup for a list <ul>. At the moment the different types of the search results (Page, Backend user, ..) are capsuled with <h3> and the search result row is capsuled with <div class="autocomplete-suggestion">.

<div class="t3js-toolbar-item-search" style="">
<h3 class="dropdown-headline">Backend user</h3>
<div class="autocomplete-suggestion" data-index="0">
..
</div>
<div>
The search result modal shows a maximum of 5 search results, more results can be viewed with the button "Show all". Information about the total search result count is missing.

The search result gets updated automatically when a user types text into the search input field. A screenreader user doesn't receive any information about the automatically updated search result list.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #92695: Search modal dialog cannot be used with a keyboardClosedGabe Troyan2020-10-23

Actions
Actions #1

Updated by Gabe Troyan about 4 years ago

  • Related to Bug #92695: Search modal dialog cannot be used with a keyboard added
Actions #2

Updated by Riccardo De Contardi about 4 years ago

  • Parent task set to #89595
Actions #3

Updated by Riccardo De Contardi about 4 years ago

  • Category set to Backend JavaScript
Actions #4

Updated by Georg Ringer 5 months ago

  • Status changed from New to Closed

closing issue as the livesearch has been refactored with v12

Actions

Also available in: Atom PDF