RE: May 31 agenda

Francis, thanks for catching that!
Indeed, that bit of the conversation was about placeholder text (among other issues) having low precedence in the Accessible Name calculation.
I have corrected that sentence in the minutes.


From: Storr, Francis <francis.storr@intel.com>
Sent: Friday, May 31, 2024 7:37 PM
To: Bruce Bailey <Bailey@Access-Board.gov>; WCAG2 Backlog <public-wcag2-issues@w3.org>
Subject: Re: May 31 agenda

Hey

I’m not sure that’s correct about the placeholder attribute not usually being part of the accessible name unless the author adds an ARIA attribute. Should that have said something else?

The HTML AAM document says that the placeholder attribute is the last possible option to be used for an accessible name: https://www.w3.org/TR/html-aam-1.0/#input-type-text-input-type-password-input-type-number-input-type-search-input-type-tel-input-type-email-input-type-url-and-textarea-element-accessible-name-computation


Recent WPT tests from the ARIA WG show that Chrome, Firefox, and Safari all use the placeholder attribute to generate an accessible name:
https://wpt.fyi/results/html-aam/accname-computation-by-element/inputs-with-placeholders.html?label=pr_head&max-count=1&pr=44965


Thanks

Francis

From: Bruce Bailey <Bailey@Access-Board.gov<mailto:Bailey@Access-Board.gov>>
Date: Friday, May 31, 2024 at 12:59
To: WCAG2 Backlog <public-wcag2-issues@w3.org<mailto:public-wcag2-issues@w3.org>>
Subject: RE: May 31 agenda
Minutes available at 2024‐05‐31 · w3c/wcag Wiki (github.com)<https://github.com/w3c/wcag/wiki/2024%E2%80%9005%E2%80%9031>.