core.ui_accessibility.html.twig

Same filename in other branches
  1. 8.9.x core/modules/help_topics/help_topics/core.ui_accessibility.html.twig
  2. 10 core/modules/help/help_topics/core.ui_accessibility.html.twig
  3. 11.x core/modules/help/help_topics/core.ui_accessibility.html.twig
---
label: 'Accessibility of the administrative interface'
related:
  - core.ui_components
---
<h2>{% trans %}Overview of accessibility{% endtrans %}</h2>
<p>{% trans %}The core administrative interface has built-in compliance with many accessibility standards so that most pages are accessible to most users in their default state. However, certain pages become more accessible to some users through the use of a non-default or improved interface. These interfaces include:{% endtrans %}</p>
<dl>
  <dt>{% trans %}Disabling drag-and-drop functionality{% endtrans %}</dt>
  <dd>{% trans %}The default drag-and-drop user interface for ordering tables in the administrative interface presents a challenge for some users, including keyboard-only users and users of screen readers and other assistive technology. The drag-and-drop interface can be disabled in a table by clicking a link labeled <em>Show row weights</em> above the table. The replacement interface allows users to order the table by choosing numerical weights (with increasing numbers) instead of dragging table rows.{% endtrans %}</dd>
  <dt>{% trans %}Enabling inline form errors{% endtrans %}</dt>
  <dd>{% trans %}Errors that occur when you submit a form, such as not filling in a required field, are sometimes difficult for users to understand and locate. In order to make these errors easier to find, the best practice is to put a summary of the errors at the top of the form page. To make them easier to understand, the best practice is to display error messages with the form fields they are related to. Both of these practices are implemented by the core Inline Form Errors module.{% endtrans %}</dd>
</dl>

File

core/modules/help_topics/help_topics/core.ui_accessibility.html.twig

View source
  1. ---
  2. label: 'Accessibility of the administrative interface'
  3. related:
  4. - core.ui_components
  5. ---
  6. <h2>{% trans %}Overview of accessibility{% endtrans %}</h2>
  7. <p>{% trans %}The core administrative interface has built-in compliance with many accessibility standards so that most pages are accessible to most users in their default state. However, certain pages become more accessible to some users through the use of a non-default or improved interface. These interfaces include:{% endtrans %}</p>
  8. <dl>
  9. <dt>{% trans %}Disabling drag-and-drop functionality{% endtrans %}</dt>
  10. <dd>{% trans %}The default drag-and-drop user interface for ordering tables in the administrative interface presents a challenge for some users, including keyboard-only users and users of screen readers and other assistive technology. The drag-and-drop interface can be disabled in a table by clicking a link labeled <em>Show row weights</em> above the table. The replacement interface allows users to order the table by choosing numerical weights (with increasing numbers) instead of dragging table rows.{% endtrans %}</dd>
  11. <dt>{% trans %}Enabling inline form errors{% endtrans %}</dt>
  12. <dd>{% trans %}Errors that occur when you submit a form, such as not filling in a required field, are sometimes difficult for users to understand and locate. In order to make these errors easier to find, the best practice is to put a summary of the errors at the top of the form page. To make them easier to understand, the best practice is to display error messages with the form fields they are related to. Both of these practices are implemented by the core Inline Form Errors module.{% endtrans %}</dd>
  13. </dl>

Buggy or inaccurate documentation? Please file an issue. Need support? Need help programming? Connect with the Drupal community.