Skip to content

Conversation

@Ovgodd
Copy link
Collaborator

@Ovgodd Ovgodd commented Dec 17, 2025

Purpose

Ensure that the HTML export is accessible to screen reader users by improving
its semantic structure and navigability.

Proposal

Refactor the HTML export output to follow accessibility best practices:
proper use of landmarks, headings, and roles to provide clear structure and
context for assistive technologies.

  • Improved heading hierarchy in exported HTML
  • Added landmarks and roles for better screen reader support

@Ovgodd Ovgodd requested a review from AntoLC December 17, 2025 12:29
@Ovgodd Ovgodd self-assigned this Dec 17, 2025
@github-actions
Copy link

github-actions bot commented Dec 17, 2025

Size Change: -4 B (0%)

Total Size: 4.16 MB

Filename Size Change
apps/impress/out/_next/static/dd93e9db/_buildManifest.js 889 B +889 B (new file) 🆕
apps/impress/out/_next/static/ffad9104/_buildManifest.js 0 B -890 B (removed) 🏆

compressed-size-action

@Ovgodd Ovgodd marked this pull request as ready for review December 17, 2025 12:46
* - We work directly on the parsed Document so modifications are reflected before we zip files.
* - We keep the editor inner structure but upgrade the key block types to native elements.
*/
export const improveHtmlAccessibility = (
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think we should unit test this function, I can see there is some unexpected behavior around the li tag:

Image

Here you can get a pre-made template with lot of blocks: https://www.blocknotejs.org/examples/interoperability/converting-blocks-to-pdf

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

This was tricky, but it’s now fixed.

image

CHANGELOG.md Outdated
- 🌐(backend) internationalize demo #1644
- ♿(frontend) improve accessibility:
- ♿️Improve keyboard accessibility for the document tree #1681
- ♿(frontend) make html export accessible to screen reader users #1743
Copy link
Collaborator

Choose a reason for hiding this comment

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

When rebase, it will have to go under "Unreleased".

@Ovgodd Ovgodd requested a review from AntoLC January 5, 2026 08:16
Copy link
Collaborator

@AntoLC AntoLC left a comment

Choose a reason for hiding this comment

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

Like seen together, see for the ul ol.

@Ovgodd Ovgodd force-pushed the fix/a11y-html branch 3 times, most recently from ed22550 to 43122b1 Compare January 6, 2026 12:12
@Ovgodd Ovgodd requested a review from AntoLC January 6, 2026 12:12
Copy link
Collaborator

@AntoLC AntoLC left a comment

Choose a reason for hiding this comment

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

Good job ✅

@AntoLC AntoLC self-requested a review January 8, 2026 10:02
@Ovgodd Ovgodd force-pushed the fix/a11y-html branch 6 times, most recently from e1f1384 to f2ccb52 Compare January 8, 2026 12:44
adjusted structure and semantics to ensure proper sr interpretation

Signed-off-by: Cyril <[email protected]>
@Ovgodd Ovgodd merged commit b56ebf1 into main Jan 9, 2026
28 of 29 checks passed
@Ovgodd Ovgodd deleted the fix/a11y-html branch January 9, 2026 08:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants