Open tonyfast opened 2 years ago
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! :hugs:
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! :wave:
Welcome to the Jupyter community! :tada:
Thanks @tonyfast for opening this issue :+1:
i imagine these are jupyterlab changes, but thought this was the place to talk about it.
Indeed, we could implement these changes in JupyterLab. And then update the packages here in RetroLab when a new version is released.
Linking to https://github.com/jupyterlab/retrolab/issues/80 which also has some prior discussions around accessibility.
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