Accessibility Audit for Keyboard Navigation, Screen Reader and High Zoom

Aiming to improve the accessibility of CyberChef, an audit of keyboard navigation, screen reader use and high zoom levels has been conducted.

The following areas for improvement have been identified.
Feedback welcome, with any feedback or suggestions on possible resolutions or additional issues, aim is to resolve these issues and any other accessibility issues identified.

### Keyboard Navigation

- [ ] 1. Poor focus indication: Unclear navigation due to low contrast tab focus highlighting.
- [ ] 2. Keyboard traps: Users get stuck in certain areas (e.g., input field) and cannot escape using keyboard.
- [ ] 3. Inconsistent tabbing: Unclear and inconsistent tab flow, particularly for search, new input tab, and general navigation.
- [ ] 4. Limited keyboard interaction: Inability to use arrow keys for basic navigation, access menus, reach tool tips, adjust input/output status, or explore top banner items.
- [ ] 5. Missing interaction methods: Lack of keyboard alternative for drag-and-drop operations, selecting auto-bake settings, accessing output menu, and viewing output timer tool tips..
- [ ] 6. Inaccessible documentation: Keyboard shortcut list exists but requires mouse access, this hinders discoverability.

### Screen Reader

- [ ] 1. Missing aria labels: Multiple components lack accessible labels, hindering screen reader users.
- [ ] 2. Inconsistent button labels: Some buttons use confusing labels, including underscores for titles. Provide clear and concise descriptions for all buttons.

### High Zoom Levels (400%)

- [ ] 1. Current solution fails to adequately address accessibility needs for low-vision users

No files, tests, or entry points are identified in the issue. Start by locating the keyboard navigation, screen reader, and 400% zoom UI areas, then use the checklist to define and verify completed accessibility improvements.

Written by the indexing model from the issue text.