Aria-practices: Clarify whether disclosure's toggle button should use aria-pressed

Created on 20 Sep 2018  ·  2Comments  ·  Source: w3c/aria-practices

The APG entry for Disclosure mentions that aria-expanded should be set on the toggle button. Should the toggle button also use aria-pressed, as is recommended in the entry for button?

In either case, could it be worth clarifying that in the APG? Thanks!

Feedback question

Most helpful comment

Personally I do not believe aria-pressed is needed for a disclosure show/hide; as aria-expanded is sufficient to indicate the expanded/collapsed state for assistive technology users. I find when testing sites that implement both, it sometimes gets confusing, because of the how browser/ATs’ announce the two attributes when used together. Additionally when viewing JAWS form fields dialog the state of pressed is displayed for the disclosure button which IMO is not necessary and may seem verbose.

In regards to the APG I believe that by not including aria-pressed it is already clarified by omission. 😁

All 2 comments

Personally I do not believe aria-pressed is needed for a disclosure show/hide; as aria-expanded is sufficient to indicate the expanded/collapsed state for assistive technology users. I find when testing sites that implement both, it sometimes gets confusing, because of the how browser/ATs’ announce the two attributes when used together. Additionally when viewing JAWS form fields dialog the state of pressed is displayed for the disclosure button which IMO is not necessary and may seem verbose.

In regards to the APG I believe that by not including aria-pressed it is already clarified by omission. 😁

The ARIA Authoring Practices (APG) Task Force just discussed Issue triage.

The full IRC log of that discussion

<AnnAbbott> Issue #897: https://github.com/w3c/aria-practices/issues/897

<jamesn> Github: https://github.com/w3c/aria-practices/issues/897

<AnnAbbott> jn: close issue based on comment entered by Decrepidos

Was this page helpful?
0 / 5 - 0 ratings