RWTHjupyter pages should follow accessibility guidelines. The relevant accessibility criteria to be followed are listed below.

Perceivable

• Non-text-content
  • Alternative texts for control elements
  • Alternative texts for graphics and objects
  • Empty alt attributes for layout graphics
  •  Alternatives for CAPTCHAs
• Alternatives for audio files and silent videos
• Recorded videos with subtitles
• Audio description or full text alternative for videos
• Videos (live) with subtitles
• Information and relationships
  • HTML structural elements for headings
  • HTML structural elements for lists
  • HTML structural elements for quotations
  • Content organised
  • Data tables structured correctly
  • Assignment of table cells
  • No structure markup for layout tables
  • Labelling of form elements can be determined programmatically
• Meaningful and sensible sequence
• Can be used without reference to sensory characteristics
• No restriction on screen orientation
• Input fields for user data convey the purpose
• Can be used without colours
• Audio control: sound can be switched off
• Sufficient contrast of texts
• Text size can be changed to 200
• No font graphics
• Use pagination for content
• Sufficient contrast of graphics and control elements 
• Adjustable text spacing
• Displayed content can be operated

Operable

• Keyboard operability: Can be used without a mouse
  • Conclusive sequence for keyboard operation
  • Visible focus: Current position of the focus is clear
  • No keyboard trap
  • Keyboard shortcuts can be switched off or customised
• Time-related limits customisable
• Moving content can be switched off: pause, end, hide
• Photosensitivity and ellipse: maximum of three flashes per second to fall below threshold values
• Element groups and areas can be skipped
• Meaningful web page titles and document titles
• Purpose of a link (in context): Meaningful link texts
• Alternative ways to access content
• Meaningful headings, labelling and descriptions
• Alternatives for complex pointer gestures
• Pointer gesture inputs can be cancelled or revoked
• Symbols in written form for screen readers
• Interface components as alternatives for motion activation

Understandable

• Specify main language, e.g. in HTML
• Words and sections in other languages labelled 
• No unexpected context change in focus
• No unexpected context change on input
• Navigation elements and mechanisms are standardised and consistent
• Uniform and consistent labelling of components with the same functionality
• Labelling of form elements available when user input is required
• Incorrect entries
  • Error detection identifies errors and describes them as text
  • Correction suggestions: Help with errors
  • Error prevention is supported

Robust

• Syntax analysis: Syntax is correct and complete
• Name, role and value are available and can be defined programmatically
• Status messages can be defined programmatically