Skip to content

[WIP] Chat history accessibility navigation pattern update#5638

Draft
compulim wants to merge 48 commits intomainfrom
feat-chat-history-accessibility
Draft

[WIP] Chat history accessibility navigation pattern update#5638
compulim wants to merge 48 commits intomainfrom
feat-chat-history-accessibility

Conversation

@compulim
Copy link
Contributor

Fixes #

Changelog Entry

Description

Design

Specific Changes

-

  • I have added tests and executed them locally
  • I have updated CHANGELOG.md
  • I have updated documentation

Review Checklist

This section is for contributors to review your work.

  • Accessibility reviewed (tab order, content readability, alt text, color contrast)
  • Browser and platform compatibilities reviewed
  • CSS styles reviewed (minimal rules, no z-index)
  • Documents reviewed (docs, samples, live demo)
  • Internationalization reviewed (strings, unit formatting)
  • package.json and package-lock.json reviewed
  • Security reviewed (no data URIs, check for nonce leak)
  • Tests reviewed (coverage, legitimacy)

className={cx('chat-message', { 'chat-message__is-active': activeMode === 'active' })}
id={`chat-message__index-${index}`}
>
<h4
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if markdown contains headings? Or this is negotiated by using document role?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can tune the Markdown headings but TBH not sure what is the best <h*> to use.

<h1> is usually reserved for page title, so we could start with <h2> and have Markdown/contents starts with <h3>. What do you think?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm okay. I don't like adjusting authored content like so, but seems we don't have a better way 🤣

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants