Barrierearme Courseinhalte

guidelines for clear, barrierearme Inhalte: Kontrast, Alternativtexte, Structure and Medien.

Moodle AFANDI standard Handover-ready documentation reviewed on a regular cycle

Quick overview

This page describes the working standard for Barrierearme Courseinhalte – with a focus on concrete decisions rather than general guidance.

The main focus here is approval path by access type and separatelyion of owner, reviewer, and execution so that teams apply the same standard.

The standard only becomes traceable through linked evidence such as request tickets with justification and through documented edge cases/exceptions.

Practical focusTopic-specificVerifiable

When this page helps

Typical situations in which this page adds value as a working document, and where another document is more appropriate.

Typical use cases

when Barrierearme Courseinhalte as a reusable Moodle standard with clear requirements for role profiles and permission groups should serve
when authors or trainers work inconsistently on approval path by access type
when Quality assurance and approvals with request tickets with justification should be documented in a traceable way
when Support- or course feedback points to a typical pitfall (e.g. sammelrollen wachsen without owner weiter)

Less suitable when

when Barrierearme Courseinhalte only about a one-off individual case without need for standardization applies
when a detailed project ticket or a technical step-by-step guide is the better fit

Recommended process

A pragmatic sequence that works in practice, from scope to review.

Briefly describe the use case and target audience for Barrierearme Courseinhalte briefly describe; from that scope and expected learning outcome derive the scope and expected learning outcome.
standard setup/configuration define, especially approval path by access type and separatelyion of owner, reviewer, and execution.
Use test users or a reference course to check whether role profiles and permission groups work in practice.
Quality assurance/approval carry out and link evidence such as request tickets with justification link.
After Livegang feedback auswerten and error patterns such as „Sammelrollen wachsen without Owner weiter“ as pitfall add.

Decision rules

Note: Central standards remain ausgelagert. Here be only the for Barrierearme Courseinhalte relevant decisions, Evidence and Exceptions maintained. Central guideline.

Barrierearme Courseinhalte is well documented, when rules, Edge cases and Evidence so clearly are, dass teams so that without additional coordination work can.

scope

For Barrierearme Courseinhalte first define the scope clearly: role profiles and permission groups.

Priorities

decisions about approval path by access type and separatelyion of owner, reviewer, and execution not implizit lassen, sondern roles and approvals explicitly benennen.

Exceptions

Allow exceptions only if they do not dilute the standard; especially relevant here are privileged accounts and admin rights.

Evidence logic

Verifiable is the rule only, when request tickets with justification and approval logs / genehmigungen cleanly verlinkt are.

What should be documented

Here only the spezifischen Inhalte about Barrierearme Courseinhalte maintain; general documentation rules remain in the centraln guideline. Central guideline.

The page is good when a substitute can apply or review the standard without first collecting tribal knowledge.

scope & terms

terms, scope and boundaries about Barrierearme Courseinhalte specify in concrete terms, including role profiles and permission groups.

Binding rules

Den standard so record, dass approval path by access type and rezertifizierungsintervall je systemklasse eindeutig entschieden are.

Evidence & filing

Name and link evidence directly: request tickets with justification, approval logs, recertification reports, and evidence of access removal.

Exceptions & Historie

Aktive Exceptions, the latest change and the next review belong on the page—especially for topics with privileged accounts and admin rights.

Common pitfalls

This section captures real-world pitfalls from Barrierearme Courseinhalte; general guidance belongs in the central guideline. Central guideline.

scope driftet: Sammelrollen wachsen without Owner weiter.
the rule is too abstract: temporary Zugriffe laufen without Enddatum weiter.
evidence is missing: admin rights be in the Ticket only informell abgestimmt.
the exception gets out of control: course becomes aus Altbestand kopiert without Bereinigung.

Tip: It is better to document three concrete observations from real cases than to keep a long generic list.

Moodle reference (official docs 5.1)

Kurze Verweise on the offizielle Moodle documentation for Barrierearme Courseinhalte. So remains this Page AFANDI-spezifisch and vermeidet doppelte Grundlagen.

Official references

Documentation focus

Medien- and Dateiformate so document, dass Alternativen/Transkripte/Lesbarkeit checked be can.
UI path, role and test case record explicitly (not only the desired target state).
Mark deviations from AFANDI standards separatelyely so that updates remain easier to review.

Note: Moodle interfaces, paths, and options can vary depending on the version, theme, and enabled plugins. Therefore always include the version, role, and test context on the page.

Review & maintenance

Check this Page gegen reale processes about Barrierearme Courseinhalte – not only gegen the Wortlaut. Entscheidend is, ob standard, Exceptions and Evidence in the Alltag contribute.

Stimmen role profiles still with the Realität match?
Were temporary approvals fristgerecht beendet?
Are Rezertifizierungen pro Systemklasse afterweisbar?
Passt the Structure to the learning objective?

Review focus for „Barrierearme Courseinhalte“: Course design; check especially role profiles and permission groups.

Useful metrics

A few metrics are enough – what matters is that they trigger decisions or improvements.

For „Barrierearme Courseinhalte“ Kennzahlen directly an approval path by access type and the most frequent Praxisrisiken koppeln.

approvaldauer

Median from Antrag to erteilter or abgelehnter approval

Interval: monthly

Offene exceptionzugriffe

Anzahl befristeter Zugriffe without fristgerechtes Ende

Interval: monthly

Rezertifizierungsquote

Anteil termingerecht abgeschlossener Access-Reviews

Interval: quarterly

Next steps

Add jetzt the concrete Entscheidung about approval path by access type incl. Verantwortlichen, Datum and Verweis on request tickets with justification.

On „Barrierearme Courseinhalte“ make especially clear as the next step: which role profiles and permission groups apply in the standard case and which exceptions are time-limited.