Rgaa Mandatory Elements logo

Rgaa Mandatory Elements

Community
MTeelokee
rgaa-mandatory-elements

Audit a web page for RGAA v4.1.2 Theme 8 – Mandatory HTML elements accessibility compliance. Checks for valid doctype, valid generated source code, default page language, valid language codes, page title presence and relevance, language change indicators, proper use of HTML tags (not for presentation only), and reading direction changes. Use this skill when someone asks to check HTML validity, page language, page title, RGAA Theme 8, or basic HTML accessibility requirements.

Overview

PublisherMTeelokee
Repositoryrgaa-accessibility-audit
Skill namergaa-mandatory-elements
Stars
6
Forks
1
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by MTeelokee on GitHub. Read the source before you install it.

Installation

Install the Rgaa Mandatory Elements AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/MTeelokee/rgaa-accessibility-audit/tree/main/skills/rgaa-mandatory-elements
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/MTeelokee/rgaa-accessibility-audit.git /tmp/rgaa-accessibility-audit
mkdir -p .claude/skills
cp -r /tmp/rgaa-accessibility-audit/skills/rgaa-mandatory-elements .claude/skills/rgaa-mandatory-elements
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Rgaa Mandatory Elements in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Rgaa Mandatory Elements on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Rgaa Mandatory Elements is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

RGAA Mandatory Elements Accessibility Audit (Theme 8)

Audits a web page against the 10 criteria of RGAA v4.1.2 Theme 8: Mandatory Elements.

Audit procedure

Step 1: Gather page metadata

javascript
(() => {
  const html = document.documentElement;
  const results = {
    doctype: document.doctype ? `<!DOCTYPE ${document.doctype.name}>` : null,
    htmlLang: html.getAttribute('lang'),
    htmlXmlLang: html.getAttribute('xml:lang'),
    htmlDir: html.getAttribute('dir'),
    title: document.title,
    charset: document.characterSet,
    metaCharset: document.querySelector('meta[charset]')?.getAttribute('charset'),

    // Language changes
    langChanges: [],

    // Tags used for presentation only
    presentationTags: {
      hasInlineStyles: document.querySelectorAll('[style]').length,
      bTags: document.querySelectorAll('b').length,
      iTags: document.querySelectorAll('i').length,
      sTags: document.querySelectorAll('s').length,
      uTags: document.querySelectorAll('u').length,
      fontTags: document.querySelectorAll('font').length,
      centerTags: document.querySelectorAll('center').length,
      bigTags: document.querySelectorAll('big').length,
      smallUsedForStyle: 0,
      brSequences: 0
    },

    // Direction changes
    dirChanges: []
  };

  // Language changes in content
  document.querySelectorAll('[lang], [xml\\:lang]').forEach(el => {
    if (el !== html) {
      results.langChanges.push({
        tag: el.tagName.toLowerCase(),
        lang: el.getAttribute('lang'),
        xmlLang: el.getAttribute('xml:lang'),
        text: el.textContent.trim().substring(0, 60)
      });
    }
  });

  // Check for consecutive <br> (presentational use)
  const walker = document.createTreeWalker(document.body, NodeFilter.SHOW_ELEMENT);
  let node;
  while (node = walker.nextNode()) {
    if (node.tagName === 'BR' && node.nextElementSibling?.tagName === 'BR') {
      results.presentationTags.brSequences++;
    }
  }

  // Direction changes
  document.querySelectorAll('[dir]').forEach(el => {
    if (el !== html) {
      results.dirChanges.push({
        tag: el.tagName.toLowerCase(),
        dir: el.getAttribute('dir'),
        text: el.textContent.trim().substring(0, 60)
      });
    }
  });

  return JSON.stringify(results, null, 2);
})()

Step 2: Evaluate criteria

Criterion 8.1 – Page has a doctype. The page must start with <!DOCTYPE html> (HTML5) or a valid DTD reference.

Criterion 8.2 – Generated source code is valid. Check for critical validity issues:

  • No duplicate id attributes
  • Tags are properly opened and closed
  • Tags are properly nested
  • Attributes are not duplicated on the same element
javascript
// Quick duplicate ID check
(() => {
  const ids = {};
  const duplicates = [];
  document.querySelectorAll('[id]').forEach(el => {
    const id = el.id;
    if (ids[id]) duplicates.push(id);
    ids[id] = (ids[id] || 0) + 1;
  });
  return JSON.stringify({ duplicateIds: duplicates, totalIds: Object.keys(ids).length });
})()

Criterion 8.3 – Default language is present. <html> must have a lang attribute (and/or xml:lang for XHTML).

Criterion 8.4 – Language code is valid and relevant. The lang value must be a valid ISO 639-1/639-2 code and match the actual language of the page content. Common codes: fr, en, de, es, it, pt, nl, ar, zh, ja.

Criterion 8.5 – Page has a title. <title> element must exist and not be empty.

Criterion 8.6 – Page title is relevant. The title should identify the page content and ideally include the site name. It should be unique across the site. Check that it is not generic like "Home" or "Untitled".

Criterion 8.7 – Language changes are indicated in the code. Any passage of text in a different language than the page default must have a lang attribute on a surrounding element. This requires visual/content inspection.

Criterion 8.8 – Language change codes are valid. Each lang attribute on sub-elements must be a valid ISO language code.

Criterion 8.9 – Tags are not used for presentation only. HTML tags must be used according to their semantic meaning:

  • No <h1>-<h6> used just for visual styling
  • No <blockquote> used just for indentation
  • No <table> used just for layout without role="presentation"
  • No consecutive <br> used for spacing
  • No deprecated presentational elements (<font>, <center>, <big>, etc.)

Criterion 8.10 – Reading direction changes are signaled. Content in right-to-left scripts (Arabic, Hebrew) must use dir="rtl". Content in left-to-right scripts within an RTL context must use dir="ltr".

Step 3: Generate report

For each criterion, report the status and any issues found. Language-related criteria (8.7, 8.8) and semantic misuse (8.9) may require content analysis beyond pure code inspection.

WCAG references: 9.1.3.1 (A), 9.2.4.2 (A), 9.3.1.1 (A), 9.3.1.2 (AA), 9.4.1.1 (A), 9.4.1.2 (A)

Frequently asked questions

What does the Rgaa Mandatory Elements AI skill do?

Audit a web page for RGAA v4.1.2 Theme 8 – Mandatory HTML elements accessibility compliance. Checks for valid doctype, valid generated source code, default page language, valid language codes, page title presence and relevance, language change indicators, proper use of HTML tags (not for presentation only), and reading direction changes. Use this skill when someone asks to check HTML validity, page language, page title, RGAA Theme 8, or basic HTML accessibility requirements.

Why use Rgaa Mandatory Elements on TypingMind?

Because you install it once and use it with any model. Rgaa Mandatory Elements is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Rgaa Mandatory Elements in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/MTeelokee/rgaa-accessibility-audit/tree/main/skills/rgaa-mandatory-elements. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Rgaa Mandatory Elements?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Rgaa Mandatory Elements?

As many as you like. As long as a model supports skills, you can use Rgaa Mandatory Elements with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Rgaa Mandatory Elements AI skill free?

Yes. It is published on GitHub by MTeelokee under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇