Problem/Motivation

The module, which is generally great, makes every question an H3. This can cause accessibility issues when in situations where the page does not have an H1, or where the FAQ is being placed inside an H3, H4, H5 or H6. In most of our uses of FAQ fields, they are the only thing on the page and so fall directly below an H1, but there are occasional times when it is in a different hierarchy location.

Proposed resolution

Allow choosing the tag to use for the question. Ideally this would be a setting on a per field instance basis, second best at a per node/per paragraph basis, third best (and bare minimum) on a sitewide basis.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork faqfield-3373259

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

kwfinken created an issue. See original summary.

kwfinken’s picture

Issue tags: -access +Accessibility
oleksandr p.’s picture

Version: 8.x-7.1 » 8.0.x-dev
oleksandr p.’s picture

Assigned: Unassigned » oleksandr p.

oleksandr p. changed the visibility of the branch 3373259-accessibility-allow-changing to hidden.

oleksandr p. changed the visibility of the branch 3373259-accessibility-allow-changing to active.

oleksandr p.’s picture

Assigned: oleksandr p. » Unassigned
Status: Active » Needs review
StatusFileSize
new14.2 KB

I added the basic functionality to handle this issue for all main field formats (see the attached screenshot). I hope these changes cover the main scope of the accessibility questions mentioned.

  • heddn committed ed1c0b6b on 8.0.x authored by oleksandr p.
    feat: #3373259 Accessibility: Allow changing of question tag
    
    By:...
heddn’s picture

Status: Needs review » Fixed

Thanks for the contributions.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.