DEV Community

Discussion on: Putting Out the Fire: Where Do We Start With Accessibility in JupyterLab?

Collapse
 
isabelapf profile image
Isabela Presedo-Floyd

Thanks for the kind words and advice! I'm surprised I haven't run into ATAG before, but it does look like it can help fill in some of the questions we are having while working on JupyterLab.

I totally agree that there is a huge difference in mindset and effort based on "compliance" to "great experience." I intentionally chose compliance to reflect the state I feel most of the community is currently in, but you make a point that setting the expectations higher may help us aim higher regardless of where we are now!

Collapse
 
grahamthedev profile image
GrahamTheDev • Edited

ATAG doesn't get spoken about often, mainly because building publishing platforms is hard in the first place, adding accessibility on top after you have built it is a nightmare most developers don't want to endure.

Hopefully though while you are reimagining your product it is the ideal time to look into it.

As for the compliance vs great experience bit, if anything it makes life easier and doesn't make the bar any more difficult to reach. It just means that you will focus on the problems that 100 people experience rather than the problem one person may experience but it "ticks another box".

Overall I find it actually makes the job of improving accessibility easier as instead of 100 small things to focus on you can pick 3 or 4 big things and work on them (plus as an added bonus you learn the answers to the 100 small things along the way).

I look forward to hearing more about your progress as I said and if you ever need a little help on something you are all stuck on / unsure about feel free to give me a shout, if I have the time to help I will!