Platform terms,
plainly explained.

A review of a page for accessibility barriers. The platform's automated audit identifies detectable issues that need to be considered alongside manual testing.

Something in a website that makes a task or information difficult or impossible for a person with a disability to access.

Summarized information that helps teams interpret findings, recurring barriers, and possible next actions.

The ongoing work of assessing barriers, coordinating improvements, supporting visitors, and tracking progress.

An indication of how established an organization's accessibility practices are, used in the strategy assessment rather than as a compliance score.

A preset combination of visitor settings, such as a low-vision or focus profile, that provides a starting point for personal adjustments.

An automated check of a selected page at a particular time. It provides a snapshot of detectable technical barriers.

A maintained description of a website's accessibility position, assessment information, known barriers, and routes for feedback or help.

The guided questionnaire that considers an organization's services, technical environment, practices, and goals to suggest possible next steps.

The visitor-facing panel that offers the accessibility tools and content alternatives enabled for a website.

Other ways to obtain information or complete a task when the original content or process has a known barrier.

Design that considers how people with different abilities perceive, understand, and operate a website.

The name assistive technology uses to identify a control or other element, such as the purpose of a button.

Information about the customer account processed to provide platform services.

The initial steps for registering and preparing access to the platform.

A current paid plan that provides access to its included features and usage allowances.

Websites beyond the number included in a plan that may be added under an agreed scope.

A specific part of a page, such as a button, image, or form field, associated with an audit finding.

The pages on which a particular finding has been detected, helping teams understand its spread across the website.

The plan intended for organizations managing multiple websites, with separate configurations and results for each domain.

Text or other content prepared with automated assistance that still needs human review before use.

Another way of presenting a page's information, such as simplified text or a transcript, alongside the original.

Visitor settings that adjust moving elements to reduce distraction where supported.

The visual presentation of the widget, including its colours and presentation mode.

A version the team has reviewed and accepted for its intended use.

The standard and level used when assessing a website, recorded as part of the statement's assessment information.

The recorded date of the evaluation supporting the statement's assessment information.

The benchmark, method, date, and supporting information describing how a website was evaluated.

The recorded findings or report supporting what a statement says about the website's accessibility position.

How a website was evaluated, for example through automated checks, manual review, or a combination of methods.

Software or equipment people use to interact with digital content, such as a screen reader or alternative input device.

Information presented as sound, which may need a suitable text alternative for people who cannot hear it.

How much of the website's known page inventory has usable audit results. Coverage describes the extent of testing, not the absence of barriers.

How current an audit result is. Older results may need to be refreshed to reflect changes to the page.

An indicator summarizing automated checks for a tested page. It is not a percentage of legal compliance or proof that everyone can use the page.

The state of a page's audit, indicating whether a result is available, pending, or needs attention.

The outcome of software-based page checks, which needs context from coverage, manual review, and real use.

Checks run by software to detect supported technical problems. Results cover only the conditions the checks can evaluate.

Work that continues without keeping the relevant workspace tab open, such as processing a supported video's transcription.

The recurring period used to measure subscription charges and monthly allowances.

An editing approach that reviews each extracted heading, paragraph, or other content unit separately.

The structural role of a content block, such as a heading or paragraph, used when editing a page version.

A visual setting that adjusts how light or dark displayed content appears.

Whether a browser provides the capabilities needed for a particular visitor tool to work.

Text synchronized with media that conveys speech and relevant sounds.

The difference between foreground and background colours that helps make text and other visual information distinguishable.

Visitor adjustments or profiles intended to make colour presentation more suitable for an individual's needs.

The verified process or contact for escalating an accessibility concern where relevant to the statement's context.

Tools or presets that reduce distractions and help a visitor follow the content.

The degree of certainty supported by the available evidence and testing scope, including what has not been checked.

The recorded outcome of an assessment against a stated benchmark. It should reflect available evidence, rather than be inferred from installing a widget.

A website domain associated with its own platform configuration and results.

A statement structure intended to describe accessibility information for a consumer-facing service.

An individual unit of extracted page content, such as a heading, paragraph, or list item, that can be reviewed in context.

How well a reader understands the information and meaning of a page.

Collecting supported text and structure from a page so it can be processed and reviewed.

The availability and processing state of extracted content, simplified versions, plain-language content, and supported transcriptions.

Checking prepared content for accuracy, meaning, tone, structure, and suitability for its audience.

The order of headings and other blocks in a page version, which should support a coherent reading flow.

Different representations of a page's information, such as original, simplified, and plain-language versions.

Moving between websites or page views while keeping each site's configuration and findings separate.

Changes to foreground and background presentation intended to make information easier to distinguish.

The website-specific configuration connection referenced by the platform's widget and management tools.

Information about how successfully website pages are being discovered and processed, providing context for coverage gaps.

Pages considered especially important when prioritizing accessibility work, for example because they support essential visitor tasks.

Comma-separated values: a file format that organizes records into rows and fields for spreadsheet or other data tools.

Report data supplied as rows and columns in a CSV file for review or further analysis in spreadsheet tools.

An interface appearance that uses predominantly dark surfaces and lighter text.

An overview screen that summarizes the selected website's state and provides entry points to its tools.

Operations performed on information, such as collecting, storing, or transforming website content for a selected workflow.

Checks that identified a problem in the tested page state and require investigation or correction.

Messages sent to developers that are counted against the relevant website's monthly allowance.

A structured findings export intended to retain page and issue context for technical review and task planning.

A reading aid that provides explanations of words encountered in content where the feature is available.

URLs identified by the platform and added to the website's known page inventory.

The website address used to distinguish one site's configuration and results from another's.

Changes to the domain associated with a controller, subject to the plan's monthly allowance.

Confirmation that the loaded widget is connected to the domain expected by its configuration.

Alternative letter styles some visitors find easier to read; individual preferences differ.

The team's ability to review, edit, and approve alternative content before making it available to visitors.

The number of page elements associated with a finding, helping indicate how widely the issue appears.

The generated script code copied into a website to connect the configured widget or embedded statement.

A script included in a customer webpage to load an embedded platform feature.

Semantic webpage content inserted within an existing customer page, using the host website's visual styling.

A statement displayed inside the operator's own webpage using the platform's embed, with styling inherited from that website.

Tools or workflows switched on and available for the selected website and plan.

A context-specific procedure or authority named for pursuing an unresolved accessibility concern.

A document recording an accessibility assessment that may be linked as supporting evidence in a statement.

A collection of related report outputs, such as readable documents and machine-readable evidence, provided together.

A concise explanation of a report's main findings, risks, and recommended actions for decision-makers.

Supported text and structure collected from a page and organized for review and alternative-content workflows.

Automated checks whose tested conditions did not pass; several affected elements may relate to one check.

The arrangement for receiving and responding to accessibility questions, reported barriers, or requests for help.

The contact channel visitors can use to report an accessibility barrier or request help, as described in the statement.

A result from an accessibility check that identifies an issue or something requiring review, with context for investigating it.

Supporting information that helps a team understand where an issue occurs and what a suitable correction should address.

Suggested actions and explanations associated with a finding to help a team investigate and correct the underlying problem.

A preset combination of settings intended to support concentration and reduce visual distractions.

The displayed size of text, which visitors may adjust to suit their reading needs.

Interactive parts of a form, such as text fields, checkboxes, and selection lists.

Text that identifies what a form field is for and should be associated with its control.

A statement structure for openly describing accessibility information without automatically assigning a specific regulatory context.

Content produced by automated processing, which should be checked rather than treated as automatically approved.

Files that capture the findings and website data used for a report at generation time.

The current stage of building a report and its outputs, such as queued, processing, or complete.

A website system's shared place for adding code that should load across relevant pages.

Text identifying a page or section and its place in the content hierarchy.

The sequence and levels of headings that communicate how a page's sections fit together.

A presentation option that emphasizes differences between foreground and background colours.

The infrastructure on which a website or platform service runs and stores its information.

HyperText Markup Language: the structure used to identify and organize content in a webpage.

Evaluation by a person to catch mistakes, lost meaning, inappropriate wording, or audience-specific problems.

An embedded browsing frame that displays another page or media player inside the current page.

Visitor options that change how images are presented where the website configuration supports them.

The effect an accessibility barrier may have on people using the page, used as context when planning fixes.

A description of intended work to address known barriers, included where relevant in a statement.

Separate visitor adjustments that can be changed independently, including after choosing a profile.

The colours used for the widget's controls and surfaces, configured for the website's visual context.

A billing record detailing a subscription charge and the associated payment information.

A script loaded as a module; the widget installation uses a generated module to connect the website with its configuration.

JavaScript Object Notation: a structured text format used to exchange data between software tools.

Report data supplied in a structured, machine-readable JSON file for use in other tools or analysis workflows.

The country or region relevant to the statement's context; selecting one does not by itself determine which rules apply.

Visitor tools intended to support keyboard-based interaction. They supplement the website's own keyboard accessibility.

Moving through and operating a website using keyboard commands rather than a mouse.

An identified accessibility problem that can be described in the statement together with available alternatives or planned improvements.

The URLs already recorded in the platform's inventory, which form the basis for coverage comparisons.

Identifiable page regions, such as navigation or main content, that help assistive-technology users move around a page.

An enlarged pointer that can make its position easier to locate on screen.

The law, policy, contract, or other basis recorded for the statement, which the organization must verify for its circumstances.

An interface appearance that uses predominantly light surfaces and darker text.

The automated audit indicator identified in the reports as a technical result, distinct from broader website-level context.

The vertical space allocated to each line of text, affecting how closely lines sit together.

A visitor setting that makes links more visually prominent so they are easier to identify.

An individual entry in an ordered or unordered list that may be represented as a content block.

Accessibility settings retained on the visitor's own device to preserve their chosen experience.

A starting set of visual adjustments intended to support some visitors who have reduced vision.

Targets for making text easier to understand, requiring review for the intended audience rather than relying only on a generated label.

Files structured for processing by software, such as CSV and JSON, rather than only for visual reading.

Enlarging displayed content to make text or visual details easier to inspect.

A visitor tool for enlarging part of the displayed page to make its details easier to inspect.

The saved statement record that the organization updates as facts, assessments, and website conditions change.

A report organized around website status, coverage, risk, and recommended actions for oversight and communication.

A person's inspection of results or content to check accuracy, relevance, and issues that need human judgment.

Accessibility checks performed by people to evaluate behavior and usability that automated checks alone cannot establish.

Identifying supported media on a page so it can enter an available processing workflow.

Repeated review of website accessibility information over time to track changes, new findings, and progress.

The amount of a metered activity available during a subscription month, such as pages, reports, or support tickets.

A recurring reporting arrangement that generates a selected report each month.

Tools that help visitors move between content and controls on a website.

Issues reported in the latest audit that were not present in the comparison result.

A statement status used when an accessibility assessment is not available, keeping the absence of assessment evidence explicit.

An assessment status indicating the website does not meet the recorded benchmark, supported by concrete assessment information.

A PDF statement generated when requested from the currently saved information, rather than a separately maintained document.

Generating a report when needed from the website data currently available.

The organization responsible for the website or service described in the accessibility statement.

The source information from the website, retained for comparison with prepared alternatives.

An audit result that may no longer adequately reflect the current page and needs review or refresh.

The team or role likely to be responsible for investigating and addressing a finding.

The automated technical indicator for a particular tested URL, device type, and point in time.

The process of identifying website URLs so they can be included in the page inventory and relevant workflows.

The collection of known website URLs, with their available processing, audit, and content status.

The summary of a selected page's processing state, audit availability, content versions, and related details.

A complete representation of a page's content, such as its reviewed plain-language version.

The view for an individual URL that brings its overview, audit, content alternatives, and available transcriptions together.

A block of connected text that develops one idea and can be edited as part of a page's structure.

An assessment status indicating that some requirements of the recorded benchmark are not met.

Checks whose tested conditions were satisfied. They do not establish that every aspect of the page is accessible.

The billing and payment details used to manage a subscription.

Portable Document Format: a document file format used for readable reports and statement downloads.

A state indicating that work is waiting to be completed rather than already available for review.

The configured position of the widget interface within the website's visible layout.

A more substantially rewritten page version intended to support easier comprehension. Its meaning and suitability still require human review.

The complete page alternative produced through the plain-language workflow, which can be reviewed and edited as a connected document.

The usage allowances and website counts associated with the selected subscription.

A website-level indicator that includes broader context than the automated technical score alone.

The date a statement was initially prepared, distinct from the date the website was assessed.

Alternative content that has been generated or edited through platform workflows and can be made available when reviewed and enabled.

The way the widget interface is displayed, as selected in the website's configuration.

An indication of which findings deserve attention first, considered alongside their impact, affected elements, and remediation effort.

Labels used to order remediation work according to the relative importance of findings.

The document explaining how personal information is handled, including purposes and relevant data practices.

The plan that adds assisted content and reporting workflows to the core accessibility tools.

Pages for which processing has completed, with the available results shown in their workspace.

The current state of a page-processing task, such as pending, in progress, completed, or requiring attention.

A statement published as a browser-readable webpage with its own URL.

Relating to government or other public bodies; a separate statement structure is available for this context.

The ways a saved statement can be offered, including a public webpage, embedded content, or PDF.

The statement setup option that uses a few initial choices to prepare a neutral starting point, then directs the user to missing information.

A visitor feature that presents supported text as spoken audio to assist with reading and understanding.

An indication of how demanding text may be to understand, used as an editing target rather than a guarantee of comprehension.

Tools and alternative content that help visitors follow, hear, or understand information.

A finding repeated across multiple pages that may point to a shared component, template, or content pattern.

A preference or presentation adjustment that limits moving or animated content where supported.

Request another AI-assisted version of selected content so it can be compared, edited, and reviewed.

Producing a fresh automated suggestion for selected content so the team can compare and refine it.

Creating a platform account so the user can access account and website-management functions.

An accessibility problem that appears again or a result that worsens compared with an earlier audit.

Work to correct the causes of accessibility barriers in a website's design, code, or content.

An estimate of the work needed to investigate and address a finding, rather than a guaranteed completion time.

A report focused on practical fixes, including affected pages and elements, priorities, ownership, effort, and technical evidence.

The platform area for creating reports, managing schedules, and reviewing report history for a selected website.

The record of previous report runs and their generation states and available files.

The website data captured as the basis for a particular report run.

The selected report perspective, such as management oversight or remediation planning.

Creating a statement output from current saved information when it is requested.

Restore visitor adjustments to their starting values when the current combination is no longer useful.

A previously detected issue no longer reported by a later audit. Further review may still be needed to confirm the improvement in practice.

The expected time for responding to feedback or assistance requests, recorded where applicable in the statement.

The lengths of time different information is kept before removal under the applicable data-handling arrangements.

The date associated with checking or updating statement information so it continues to reflect current facts.

The recorded stage of checking content, such as in progress or ready for use.

Findings or conditions that contribute most to the report's indication of accessibility risk.

A signal that helps prioritize attention based on available website evidence and its limitations.

The outcomes of individual automated checks, including passes, failures, and items needing further review.

The intensity of colours in the displayed page, which can be adjusted where a colour tool supports it.

Report generation arranged to run at a recurring time, such as monthly, to support ongoing review.

The website, service, or content covered by the statement or assessment.

Assistive software that presents interface information and content through speech or braille.

Expressions used to identify page elements in technical evidence so developers can locate the relevant markup.

Markup that communicates content roles and structure, such as headings, paragraphs, lists, and sections.

An indication of how serious a detected barrier is, considered together with its context and impact.

The same underlying website information used by management and technical teams when discussing progress and fixes.

A reusable website layout or component structure whose changes can affect multiple pages.

Reworking text to make it easier to read while keeping its meaning and important details.

An easier-to-read version that stays relatively close to the original wording and structure while preserving its meaning.

The platform's broader website-level indicator, considered alongside technical audit results and coverage.

The website-level area that brings discovered pages, audit status, content readiness, and page-level tools together.

Applying across the website rather than only to one individual page.

The platform's named contrast tool for adapting visual presentation to help visitors distinguish content.

The original material used to create or compare an alternative version.

Operating supported website actions through spoken commands, subject to browser support and configuration.

The plan for core accessibility audits, visitor tools, and website-specific configuration for one website.

The selected organization of the statement's content, chosen separately from jurisdiction and legal context.

An editing interface that preserves content roles, such as headings and paragraphs, while allowing individual blocks to be changed.

Issue data organized into consistent fields so it can be reviewed, filtered, or transferred to other workflows.

Service providers that process data on behalf of the platform provider for specified functions.

The recurring date that starts a new monthly allowance cycle, based on when the subscription began.

An account-based request for help that can be followed through a conversation inside the platform.

A video in a format and embedding arrangement the platform can detect and process for transcription.

The suggested team responsible for a finding, such as frontend development, design, or content.

Implementation-level evidence about a finding, such as relevant elements, selectors, or markup examples.

Information associated with a network request, used in delivering or operating a service.

Checking how a website behaves with tools people actually use, such as screen readers and alternative input methods.

Text that conveys information otherwise presented through images or other non-text content.

The visual size of page text, adjustable through available presentation tools.

The distance between letters, words, or lines, which can affect how easily text is followed.

A written representation of spoken content that can be checked alongside the source media.

The current stage of creating a transcript, such as processing or ready for review.

Versions of content in another language, available to visitors when prepared, reviewed, and enabled.

Uniform Resource Locator: the address used to identify and open a webpage or other resource.

The quantities of metered activities available under a plan and renewed with its billing cycle.

Text generated from speech in a supported video. It can be reviewed beside the video in the page workspace.

Problems that make content or controls difficult to perceive, such as inadequate contrast or unclear states.

Making prepared and enabled content alternatives available through the website's visitor interface.

An individual's chosen accessibility settings for using a website.

The configurable tools and content alternatives offered to help people use a website.

How content appears on screen, including typography, colour, spacing, and imagery.

Spoken instructions used to trigger supported actions in speech-navigation tools.

An organization's chosen policy or commitment recorded as the basis for accessibility information where applicable.

Web Content Accessibility Guidelines: a reference used to assess accessibility of web content.

The ability of people with disabilities to perceive, understand, navigate, and interact with websites.

A broader indicator combining context such as page status, severity, coverage, and current findings to help assess the website's position.

The settings that determine which tools, appearance, and prepared content are available on a particular site.

The platform connection that associates a site's widget with its website-specific configuration.

A representation of the website information available at a particular point in time.

The platform area for configuring a website's widget and obtaining its generated embed code.

The connection state shown for the widget on a selected website.

The connected sequence of discovering, auditing, understanding, improving, supporting, monitoring, and reporting on website accessibility.

An archive file format that can package several evidence files together for download.