Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file not shown.
Binary file modified modules/ROOT/attachments/vpat/TinyMCE_VPAT2.5_WCAG.pdf
Binary file not shown.
74 changes: 21 additions & 53 deletions modules/ROOT/pages/accessibility-conformance.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -8,19 +8,10 @@ This page describes the accessibility standards that {productname} is developed

For guidance on operating the editor with a keyboard or a screen reader, see the xref:tinymce-and-screenreaders.adoc[Accessible navigation guide].

== Overview

* xref:conformance-targets[Conformance targets]
* xref:accessibility-conformance-report-vpat[Accessibility Conformance Report (VPAT)]
* xref:known-limitations[Known limitations]
* xref:reporting-an-accessibility-issue[Reporting an accessibility issue]
* xref:recommended-software[Recommended software]
* xref:related-guides[Related guides]

[[conformance-targets]]
== Conformance targets

{productname} is developed and tested against the following accessibility standard.
{productname} 8 is developed and tested against the following accessibility standard. For the standards that apply to an earlier version, see the Accessibility Conformance Report for that version in xref:accessibility-conformance-report-vpat[Accessibility Conformance Report (VPAT)].

[cols="1,1,2",options="header"]
|===
Expand All @@ -31,68 +22,40 @@ For guidance on operating the editor with a keyboard or a screen reader, see the
|The editor user interface
|===

A target describes what {productname} is developed against. It is not a statement of full conformance. The Accessibility Conformance Report records the measured result for each individual success criterion, and the criteria that are not fully met are listed in xref:known-limitations[Known limitations].
A target describes what {productname} is developed against. It is not a statement of full conformance. The Accessibility Conformance Report records the measured result for each individual success criterion, including the criteria that are partially supported and the remarks that explain each result.

{productname} follows the https://www.w3.org/TR/wai-aria/[Web Accessibility Initiative - Accessible Rich Internet Applications (WAI-ARIA)] specification for the editor user interface.

[NOTE]
====
These targets describe the accessibility of the {productname} user interface. They are separate from the accessibility of the content authored in the editor, which is the responsibility of the content author. To check authored content against https://www.w3.org/TR/WCAG21/[WCAG 2.1] and https://www.access-board.gov/ict/[Section 508] rules, see the xref:a11ychecker.adoc[Accessibility Checker plugin].
These targets describe the accessibility of the {productname} user interface. The accessibility of authored content depends on the author, though the editor determines which accessible structures are available to them, for example table headers, heading levels, and image alternative text. To check authored content against https://www.w3.org/TR/WCAG21/[WCAG 2.1] and https://www.access-board.gov/ict/[Section 508] rules, see the xref:a11ychecker.adoc[Accessibility Checker plugin].
====

[[accessibility-conformance-report-vpat]]
== Accessibility Conformance Report (VPAT)

An Accessibility Conformance Report (ACR) records how a product measures against a set of accessibility standards. {companyname} publishes these reports using the https://www.itic.org/policy/accessibility/vpat[Information Technology Industry Council (ITI) Voluntary Product Accessibility Template (VPAT)].

The current report uses the WCAG edition of the template. It covers WCAG 2.0, 2.1, and 2.2 at Level A and Level AA. It does not cover Section 508 or EN 301 549.
Each report uses the WCAG edition of the template and covers Level A and Level AA. The reports do not cover Section 508 or EN 301 549.

[cols="1,1,2",options="header"]
|===
|Version |Published |Report

|{productname} 8.5
|May 2026
|xref:attachment$vpat/TinyMCE_VPAT2.5_WCAG.pdf[Download the Accessibility Conformance Report for {productname} 8.5] (PDF)
|===

The report was produced by expert evaluation through Axess Lab, together with testing across a range of assistive technologies.

Reports are reviewed twice a year and republished alongside a release. When a newer report supersedes an earlier one, the earlier report is retained so that organizations running an earlier release can reference the report that applies to the version they have deployed. For the security and compliance documentation that {companyname} maintains outside of accessibility, see xref:security.adoc#security-assurance-and-compliance[Security assurance and compliance].

[[known-limitations]]
== Known limitations
|Version |WCAG versions covered |Report

The following success criteria are recorded as partially supported in the current Accessibility Conformance Report. Each entry corresponds to a finding in that report.
|{productname} 8
|WCAG 2.0, 2.1, and 2.2
|xref:attachment$vpat/TinyMCE_VPAT2.5_WCAG.pdf[Download the Accessibility Conformance Report for {productname} 8] (PDF)

[cols="1,2,1",options="header"]
|{productname} 6
|WCAG 2.0 and 2.1
|xref:attachment$vpat/TinyMCE_6.7_VPAT2.4Rev_WCAG.pdf[Download the Accessibility Conformance Report for {productname} 6] (PDF)
|===
|Success criterion |Limitation |Affected area

|1.3.1 Info and Relationships (Level A)
|Some relationships within tables are conveyed less clearly than they could be.
|Tables
Each report was produced by expert evaluation, together with testing across a range of assistive technologies. For the {productname} 8 report, the {companyname} accessibility team also evaluated the WCAG 2.2 success criteria and reviewed all previously reported findings.

|3.2.2 On Input (Level A)
|Selecting a character inserts it immediately and closes the dialog, without advance notice that this will happen.
|xref:charmap.adoc[Character Map plugin]
Reports are reviewed twice a year and republished alongside a release. The table lists the latest report for each major version of {productname}. When a newer report is published for a major version, it replaces the earlier report for that version.

|3.3.2 Labels or Instructions (Level A)
|Buttons that insert invisible or control characters are labeled with those characters, which leaves the buttons without a visible label.
|xref:charmap.adoc[Character Map plugin]

|4.1.2 Name, Role, Value (Level A)
|The character buttons in the dialog are not marked up as buttons.
|xref:charmap.adoc[Character Map plugin]

|1.4.11 Non-text Contrast (Level AA)
|The contrast of the outlines drawn around block-level elements is insufficient.
|xref:visualblocks.adoc[Visual Blocks plugin]

|4.1.3 Status Messages (Level AA)
|Changes to the search results are not communicated to assistive technologies.
|xref:charmap.adoc[Character Map plugin]
|===
For the security and compliance documentation that {companyname} maintains outside of accessibility, see xref:security.adoc#security-assurance-and-compliance[Security assurance and compliance].

[[reporting-an-accessibility-issue]]
== Reporting an accessibility issue
Expand All @@ -106,7 +69,7 @@ Include the following information where it is available:
* The steps required to reproduce the issue.
* The expected behavior and the observed behavior.

To request an accommodation, contact link:{supporturl}/[{supportname}].
To ask an accessibility question that is not a bug report, contact link:{supporturl}/[{supportname}]. Support is provided in writing.

[[recommended-software]]
== Recommended software
Expand All @@ -122,9 +85,14 @@ To request an accommodation, contact link:{supporturl}/[{supportname}].

|NVDA
|https://www.nvaccess.org/[NV Access]

|VoiceOver
|https://www.apple.com/accessibility/[Apple]
|===

For the best experience, use https://www.nvaccess.org/[NVDA] together with https://www.mozilla.org/en-US/firefox/products/[Firefox]. Screen reader and browser behavior varies between combinations, so the experience with other combinations can differ, although the editor can be used with a wide variety of combinations.
Other screen readers may work but have not been verified.

Screen reader and browser behavior varies between combinations, so the experience may vary depending on the combination.

[[related-guides]]
== Related guides
Expand Down
Loading