| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000711 | YaCy | [All Projects] General | public | 2016-11-29 00:41 | 2017-11-25 12:05 |
|
| Reporter | luc | |
| Assigned To | administrator | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | |
| ETA | none | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Target Version | | Fixed in Version | | |
|
| Summary | 0000711: Unusable tab key in search results |
| Description | On YaCy search results page, "Tab" and "Shif+Tab" standard keys can not be used to tab between UI components : instead it triggers the next results page loading.
This is a concern to disabled users or people who simply want to use their keyboard and standard keys to interact with the page. |
| Steps To Reproduce | - Search something
- The results page opens
- Press the "Tab" key
- Instead of tabbing to the search button or any UI component, the next results page is loaded |
| Additional Information | "Tab" and "Next page" keyboard events are explicitely designed on this page to trigger the next page loading : see https://github.com/yacy/yacy_search_server/blob/master/htroot/yacysearch.html#L20 [^]
At least, for improved accessibility the Tab key should keep its standard behavior.
But this behavior has been in YaCy since 2011 (https://github.com/yacy/yacy_search_server/commit/ef72fdac795dca8e73885e81f7b7f254f93df72c [^]), so it may be confusing for early users if we set "Tab" key again to its standard behavior.
Any feedback and comments would be welcome! |
| Tags | crawler, mom and son incest |
|
| Attached Files | |
|
Relationships 
Relationships 