mirror of
https://github.com/hanzoai/team.git
synced 2026-09-30 01:57:35 +00:00
b5f007d35e
* docs: resolve cross-file anchor mismatches from RST-to-MDX migration
The Sphinx-to-Docusaurus migration converted `:ref:`/`{ref}` links using
naive text-slugification, so anchors that pointed to headings in a
different file (e.g. release-summary tables linking into their
respective changelog pages) were emitted as same-page fragments and
silently resolved to nothing.
Built a label registry from the original Sphinx `.. _label:` / `(label)=`
targets to recover the true source file for each cross-reference, then
rewrote the affected links to point at the correct file + heading
anchor. Fixes 282 broken cross-file anchors, primarily in the mobile/
desktop/server release-summary pages, plus assorted same-page anchor
mismatches caught by re-auditing after the prior admonition/anchor fix.
* docs: manually resolve remaining anchor mismatches after cross-file audit
Hand-verified fixes for anchors that fuzzy-matching alone couldn't
safely resolve (confirmed against actual heading text/context, and in a
few cases against the original RST source, before applying):
- Typos and dropped words carried over from the original Sphinx docs
(e.g. "bot-acocunts", "auto-follow-all-new-channel-threads" ->
"follow-all-new-channel-threads").
- Sphinx auto-generated duplicate-heading IDs (#id1/#id3/#id4) resolved
to their real target headings.
- Numbered-step TOC links in enterprise-roll-out-checklist.mdx that
dropped the leading "N. " used in the actual heading slugs.
- Push-notification docs pointing at the wrong file entirely
(environment-configuration-settings instead of
push-notification-server-configuration-settings).
- SAML "saml-enterprise" label resolved to its true cross-file target
(authentication-configuration-settings#saml-2-0), recovered from the
original RST label definition that the automated registry missed
because it sat after an RST transition marker.
- sso-saml-technical references converted from broken same-page/
malformed-path anchors to correct page links.
* docs: fix SAML 2.0 anchor slug (saml-2-0 -> saml-20)
github-slugger strips periods rather than hyphenating them, so "SAML
2.0" slugifies to saml-20, not saml-2-0 as previously fixed.
* docs: fix broken path links found during docs/main migration cleanup
* docs: convert div.tab blocks to Docusaurus Tabs/TabItem components
* docs: restore missing Kubernetes deployment architecture diagrams
The RST-to-MDX migration never copied over the AWS/Azure/Oracle
architecture diagrams referenced by the deployment-architecture-at-scale
page, leaving broken images in each Tabs/TabItem.
* docs: fix 7 anchor mismatches from the fragment/heading audit
Covers three root causes from the anchor mismatch breakdown:
- Fragment repeated the target page's own title instead of a real
heading, so the link is simplified to point at the bare page.
- Heading exists verbatim but lives on a sibling settings page
(experimental-configuration-settings, push-notification-server-
configuration-settings) rather than environment-configuration-settings.
- A page path was mistakenly pasted into a same-page #fragment instead
of being used as a real cross-page link.
* docs: fix 8 anchor slugs that were close but didn't match the real heading
Repoints links whose fragment was a plausible guess (typo, reworded
heading, or wrong section) at the actual auto-generated slug of the
target heading, confirmed by inspecting each target page directly.
* docs: merge split Tabs blocks so tabs render horizontally
The div.tab conversion script split some sibling tab groups into
separate single-item Tabs blocks whenever a stray blockquote marker
sat between them, causing them to render stacked instead of as one
horizontal tab bar. Merges the MySQL/PostgreSQL and Team/Enterprise
Edition tab groups back into single Tabs blocks.
* docs: remove Azure tab and restore Kubernetes deploy content
The Mattermost Operator, Azure, and Oracle platform tabs on the
Kubernetes deployment guide were split across two separate Tabs
blocks (rendering stacked instead of as one tab bar) and all three
tab bodies were empty because the migration never flattened the
original RST include directives. Removes the unsupported Azure tab
and restores the Mattermost Operator and Oracle content from the
pre-migration RST sources as a single merged Tabs block.
* addresscoderabbitreview
* docs: unify Linux/Kubernetes/Containers deploy pages and fix FIPS/STIG placement
Kubernetes and Containers duplicated full install content across a top-level
page (Tabs) and orphaned sidebar subpages that nothing linked to. Reworked
both to follow the Linux page's pattern: shared content on the landing page,
platform-specific instructions live once in their own subpage.
Also removed configure-fips-at-install-time.mdx, which claimed FIPS is
available for native Linux installs — FIPS/STIG in Mattermost is a container
image property (Chainguard-based build), not available outside Docker/
Kubernetes. Consolidated all FIPS/STIG references onto
containers/fips-stig.mdx and pointed the Mattermost Operator subpage (not
Oracle OKE, which doesn't expose image selection) at it.
* docs: fix review findings — image alt text, Important callout markup, typo
- Replace generic alt="image" on scaling diagrams with descriptive text
identifying cloud provider and user scale.
- Convert raw div.important markup in deploy-containers.mdx to the
repo's <Important> component, matching usage elsewhere in the file.
- Fix "Matermost" typo in manage-your-display-options.mdx.
---------
Co-authored-by: Hanzo Dev <[email protected]>
76 lines
3.6 KiB
Plaintext
76 lines
3.6 KiB
Plaintext
---
|
|
title: "Keyboard accessibility"
|
|
---
|
|
<PlanAvailability slug="all-commercial" />
|
|
|
|
Navigational keyboard shortcuts help you use Mattermost in a web browser or the desktop app without needing a mouse. Below is a list of supported accessibility shortcuts.
|
|
|
|
<table>
|
|
<colgroup>
|
|
<col style={{width: '100%'}} />
|
|
</colgroup>
|
|
<tbody>
|
|
<tr>
|
|
<td><blockquote><p>Keyboard shortcut | Description |</p></blockquote><p>==============================================+==================================================================================+ | Desktop App: <a href="mm-kbd:">F6</a> || Move focus to the next section | | Browser: <a href="mm-kbd:">Ctrl</a> <a href="mm-kbd:">F6</a> || |</p></td>
|
|
</tr>
|
|
<tr>
|
|
<td><div class="line-block">Desktop App: <a href="mm-kbd:">Shift</a> <a href="mm-kbd:">F6</a> || Move focus to the previous section |<br />Browser: <a href="mm-kbd:">Ctrl</a> <a href="mm-kbd:">Shift</a> <a href="mm-kbd:">F6</a> |</div></td>
|
|
</tr>
|
|
<tr>
|
|
<td><a href="mm-kbd:">Tab</a> | Move focus to the next element |</td>
|
|
</tr>
|
|
<tr>
|
|
<td><a href="mm-kbd:">Shift</a> <a href="mm-kbd:">Tab</a> | Move focus to the previous element |</td>
|
|
</tr>
|
|
<tr>
|
|
<td><a href="mm-kbd:">↑</a> or <a href="mm-kbd:">↓</a> | Move focus between messages in the post list or sections in the channel sidebar |</td>
|
|
</tr>
|
|
<tr>
|
|
<td><a href="mm-kbd:">Enter</a> | Take action on the focused element |</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
|
|
## Region navigation
|
|
|
|
Mattermost has eight regions that can be focused for navigation. Use <kbd>F6</kbd> in the desktop app, or use <kbd>Ctrl</kbd> <kbd>F6</kbd> in a browser repeatedly to move focus and loop through the regions in this order:
|
|
|
|
1. Message list region
|
|
2. Message input region
|
|
3. Right-hand side message list region
|
|
4. Right-hand side message input region
|
|
5. Team menu region
|
|
6. Channel sidebar region
|
|
7. Channel header region
|
|
8. Search
|
|
|
|
|
|
|
|
## Message navigation
|
|
|
|
When the message list region is focused, use the <kbd>↑</kbd> or <kbd>↓</kbd> arrow keys to navigate through messages and reply threads. Press <kbd>Tab</kbd> to navigate through message actions.
|
|
|
|
|
|
|
|
### Message composition
|
|
|
|
Mattermost is compatible with most popular screen readers, such as [Apple VoiceOver](https://www.apple.com/ca/accessibility/vision/) or [JAWS for Windows](https://www.freedomscientific.com/products/software/jaws/). A custom readout is composed for each message by combining the message elements and reading them together in full sentences. Message elements will read in the following order:
|
|
|
|
1. Header: Author, timestamp, message type (i.e. parent post or reply)
|
|
2. Main Content: The message content typed by the author
|
|
3. Attachments: The number of attachments (if applicable)
|
|
4. Emoji Reactions: The number of unique emoji reactions (if applicable)
|
|
5. Saves/Pins: If a message is saved or pinned (if applicable)
|
|
|
|
For example, a message read by a screen reader may sound like the following:
|
|
|
|
``` text
|
|
Eric Sethna at 12:57pm Thursday June 13th wrote a reply "Thanks for the review", 3 attachments, 2 reactions, message is saved and pinned.
|
|
```
|
|
|
|
## Channel sidebar navigation
|
|
|
|
When the channel sidebar region is focused, use the <kbd>↑</kbd> or <kbd>↓</kbd> arrow keys to focus individual sidebar sections, such as Insights, Threads, Favorites, custom categories, public channels, private channels, and direct messages. Press <kbd>Tab</kbd> to navigate through channels or other buttons within a sidebar section.
|
|
|
|
|