You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we do not have an accessible jupyter offering, and retrolab might be an easier to achieve compliance for than allow of jupyterlab. currently, most of the elements in retro/lab are div tags with some aria information appended; the most standards compliant solution for accessibility would be to use semantic html tags instead.
Proposed Solution
being more descriptive about tags will all assistive technologies to naturally navigate the notebook ui. the proposed solutions changes divs to more meaningful semantic tags like main, article, section, ... in the shape of the pseudo code below.
<html><head/>
<body><header>jupyter logo and notebook name</header><navaria-label="toolbar">the file, edit navigation</nav><mainaria-label="notebook"><navaria-label="notebook toolbar"\><articlearia-label="notebook cell">
# for all the cells ....
<sectionaria-label="notebook cell {CellNumber}"><sectionaria-label="notebook cell {CellNumber} input"><asidearia-label="notebook cell {CellNumber} input prompt"/>
cell input
</section><sectionaria-label="notebook cell {CellNumber} output {OutputNumber}"><asidearia-label="notebook cell {CellNumber} output {OutputNumber} prompt"/>
cell output
</section></section></article><footer>status bar?</footer></main></body>
if we can translate some of the primary div tags to their more meaningful semantic tags main, article, section,... then we can provide navigation at the very least for assistive technologies.
Additional context
i imagine these are jupyterlab changes, but thought this was the place to talk about it.
at least at a glance i feel like these changes are not too invasive, but i don't know lab well to appreciate the impacts on style and extensions.
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
jtpio
changed the title
Making retrolab's notebook a more accessible offering with semantic html tags
Making Notebook v7 a more accessible offering with semantic html tags
Apr 27, 2022
Problem
we do not have an accessible jupyter offering, and retrolab might be an easier to achieve compliance for than allow of jupyterlab. currently, most of the elements in retro/lab are div tags with some aria information appended; the most standards compliant solution for accessibility would be to use semantic html tags instead.
Proposed Solution
being more descriptive about tags will all assistive technologies to naturally navigate the notebook ui. the proposed solutions changes divs to more meaningful semantic tags like
main, article, section, ...
in the shape of the pseudo code below.if we can translate some of the primary div tags to their more meaningful semantic tags
main, article, section,...
then we can provide navigation at the very least for assistive technologies.Additional context
jupyterlab
changes, but thought this was the place to talk about it.cc @gabalafou @isabela-pf
The text was updated successfully, but these errors were encountered: