Accessibility
Overview
Accessible website
Accessibility is ... first of all a matter of course, a legal requirement and not always easy to comply with.
In purely formal terms, it is about access to content. This should be available regardless of the output device, motor skills or relevant sensory abilities of the user. However, as one of the most important features of accessible websites is their implementation according to standards, everyone benefits from appropriately optimized sites.
However, accessibility is by no means exclusively a technical task. Rather, editors have to wrestle with it with every new piece of content.
Tips for Typo3 editors: Measures
This information applies to editing by the Typo3 editorial team: What are the requirements and what should you pay attention to?
Simple and clear website structure
- Structure the page with meaningful headings
- Define headings as such
- Meaningful heading hierarchy
- Do not misuse HTML elements (lists, quotations, text paragraphs, headings, tables, buttons, input fields, etc.) and define them with HTML tags.
- Do not use hidden elements, e.g. content elements without content to regulate spacing.
- Use purely aesthetic elements such as frames, lines, etc. carefully
- Do not use any hidden elements (for purposes other than those intended) for design purposes
- Avoid large and complex tables wherever possible
- Only embed accessible documents, files, etc. in the page
- Videos contain subtitles
- Videos contain audio description
- Podcasts require transcripts
- All purely visual content (graphics, diagrams, image tables, photos and images) have meaningful alternative texts
- No text graphics
- Use dynamic and fade-in content (e.g. slider, carousel) with caution.
- For interactive graphics with a function (e.g. linking), specify the target (e.g. "University of Kassel logo, link target: homepage")
- Labeling of links: meaningful link name + contains target, no URL
- Link name contains file format (pdf, jpg, docx, etc. ...)
- Invisible labeling = visible labeling (e.g. form fields)
- If possible, do not use HTML elements in the text editor of the data records, but work with the existing formatting or use a more suitable content element (e.g. do not create tables in the editor via HTML, but use the "Table" data record).
- Important areas of the page should be provided with headings for a better overview.
- Structure the headings H2 and H3 hierarchically, use them consistently (do not mix them or use them for markings or highlighting)
- Always give content elements a title/heading and, if necessary, set to "hidden" if it is not relevant for the arrangement on the page itself.
- Screen reader users can only capture one cell of the table at a time, therefore use only for tabular data
- Avoid large and complex tables wherever possible
- Not only mark table headings in bold, but also mark them out correctly (use the heading of the content element)
- A-Z lists
- Consistent structure even on subpages
- Do not overload pages
- Insert explanatory videos
Pictures, videos, podcasts
for hearing-impaired users:
- YouTube and other applications (such as Facebook, Adobe Premiere Pro, ...) have a function for automatically generating subtitles, which must, however, be edited afterwards. (This can be done on YouTube in the subtitle editor, for example).
for hearing-impaired users.
for blind and visually impaired users:
- Alternative text for graphics, diagrams, image tables, photos and images, in which the visual content is described in an understandable and comprehensible way.
- Buttons and other "functional graphics" (interactive elements) with links require the description of the graphic (e.g. University of Kassel logo) and the target of the link (e.g. link target: homepage) as alternative text
The alternative text for the logo on the university website would then be: "University of Kassel logo, link target: homepage". This means that these buttons and links are also recognizable for blind and visually impaired users. - The destination of a link must also be recognizable without context. (Negative example: "continue reading", "click here" without specifying the destination); no URLS, but the link name should reflect the target content.
- Invisible labels should always contain the text of the visible label
- Avoid text graphics, as screen readers do not recognize this and blind and visually impaired users cannot perceive this content.
What is important for understanding the content? Often not all details are relevant to the content
- No ratings, objective description (bad: a beautiful blue sky, good: a blue sky)
- Short and concise
for blind and visually impaired people
- Clear and comprehensible description of the relevant visual content of the video
- The audio description should not overlap with the existing audio elements of the video.
- Neutral, objective description
- Audio description should be spoken by one person (no change of speaker)
Guidelines and legal requirements
More on the topic (in German language)
- Accessible web design: Easy for everyone - an initiative of Aktion Mensch (opens in a new window)
- Easy for everyone:Introduction to accessibility (opens in a new window)
- BIK - barrier-free information and communication (opens in a new window)
- Web without barriers - Guide to designing an accessible intranet for authors (opens in a new window)
- Barrier-free Information Technology Ordinance (opens in a new window)
- Access for all - Accessible use of technology - Accessibility (opens in a new window)
- Accessibility Checklist 2.0 Download (opens in a new window)
- Accessible content - a quick start (Technical University of Munich) (opens in a new window)
- The right alternative text (accessible web design) (opens in a new window)
- Good for the image:Practical guide to creating text-based alternatives for graphics (opens in a new window)