Skip to main content
Glama
nfodor

Chromium ARM64 Browser

by nfodor

run_accessibility_audit

Audit web page accessibility to identify and fix compliance issues for users with disabilities, ensuring inclusive digital experiences.

Instructions

Run an accessibility audit on the current page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function that runs an accessibility audit by injecting JavaScript into the browser to check for images without alt text, inputs without labels, and presence of headings.
    async runAccessibilityAudit() {
      await this.ensureChromium();
      
      const result = await this.sendCDPCommand('Runtime.evaluate', {
        expression: `
          const results = [];
          const imagesWithoutAlt = Array.from(document.querySelectorAll('img:not([alt])')).length;
          if (imagesWithoutAlt > 0) {
            results.push(\`Found \${imagesWithoutAlt} images without alt text\`);
          }
          
          const inputsWithoutLabels = Array.from(document.querySelectorAll('input:not([aria-label]):not([id])')).length;
          if (inputsWithoutLabels > 0) {
            results.push(\`Found \${inputsWithoutLabels} inputs without proper labels\`);
          }
          
          const headings = Array.from(document.querySelectorAll('h1, h2, h3, h4, h5, h6'));
          if (headings.length === 0) {
            results.push('No heading structure found on page');
          }
          
          JSON.stringify(results.length > 0 ? results : ['Basic accessibility checks passed']);
        `,
        returnByValue: true
      });
      
      const auditResults = JSON.parse(result.result?.value || '[]');
      
      return {
        content: [{ type: 'text', text: `Accessibility Audit Results:\\n${auditResults.join('\\n')}` }],
      };
    }
  • index.js:279-286 (registration)
    Tool registration in the ListToolsRequestSchema response, defining the tool name, description, and empty input schema (no parameters required).
    {
      name: 'run_accessibility_audit',
      description: 'Run an accessibility audit on the current page',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for the tool, which accepts an empty object (no required parameters).
    inputSchema: {
      type: 'object',
      properties: {},
    },
  • index.js:379-380 (registration)
    Dispatcher case in the CallToolRequestSchema handler that routes calls to the runAccessibilityAudit method.
    case 'run_accessibility_audit':
      return await this.runAccessibilityAudit();
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't explain what the audit entails (e.g., what standards it checks, if it's destructive, requires specific permissions, or has side effects like page reloads). This leaves significant gaps in understanding the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of an audit tool with no annotations and no output schema, the description is insufficient. It doesn't cover what the audit returns, how results are formatted, or any behavioral traits, leaving the agent with incomplete information for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could optionally mention that no inputs are required. This meets the baseline for zero-parameter tools.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'run' and the resource 'accessibility audit on the current page', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'run_best_practices_audit' or 'run_seo_audit', which would require mentioning what makes an accessibility audit unique.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a page loaded), exclusions, or how it differs from other audit tools in the sibling list, leaving the agent to infer usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nfodor/mcp-chromium-arm64'

If you have feedback or need assistance with the MCP directory API, please join our Discord server