Accessibility

[Fancy11111]

Overview

Too guarantee that every person can use the tools we should try to make everything as accessible as possible.
As a reference/guide/goal we could use the WCAG Guidelines that are provided by W3C.

Focus

I'll list some rough points from there, leaving out a few that don't really make sense for us:

• Keyboard Accessible
• Navigable
• Readable
• Input Assistance

These are just the 4 main points that really stuck out for me, but this is open for discussion.

Planning

I am not really sure what the correct way to tackle this issue is.
Some points that I'm unsure about.

1. Is going through each tool and page one-by-one the correct way?
2. Should we build some kind of small component lib which try to place stuff like aria-labels correctly?
3. How do we make sure that pages/tools/functionalities implemented at a later date meet all of the goals described above.

I think 2 could positively benefit 3.

Pages

• binary-calculator #63
• binary-coding #64
• hamming-code #65
• hamming-distance #66
• truth-table #67
• micro16-decompiler #68
• stack-simulator #69
• interleaving-graph #70
• main #71

[stefnotch]

Oh lol, I just found out that LaTeX isn't exactly accessible
https://tex.stackexchange.com/questions/261537/a-guide-on-how-to-produce-accessible-pdf-files

(The usual way of noticing that is when you try to copy paste something and end up realizing that the spacing is just broken)

[Fancy11111]

Readable is not a top priority as of now