RE: ATAG A.3.5.1 and browser built-in search

How does your proposal using a simple browser search find the alternative content<https://www.w3.org/TR/ATAG20/#def-Alternative-Content>?
I suppose searching the source code will find the alt attribute…

If this is the case, then it should be documented at https://www.w3.org/TR/2015/NOTE-IMPLEMENTING-ATAG20-20150924/#sc_a351


Regards,
Phill Jenkins
Accessibility Executive, IBM Design
@pjenkins Slack: #accessibility-at-ibm<slack://channel/?team=T073LUXEU&id=C036P1CTN>
Equal Access toolkit and accessibility checker at ibm.com/able/<https://www.ibm.com/able/>
linkedin.com/in/philljenkins/<https://www.linkedin.com/in/philljenkins/>

From: Hidde de Vries <hidde@hiddedevries.nl>
Sent: Wednesday, January 25, 2023 2:16 AM
To: w3c-wai-ig@w3.org
Subject: [EXTERNAL] ATAG A.3.5.1 and browser built-in search

Hello, A question regarding ATAG A. 3. 5. 1, which reads: A. 3. 5. 1 Text Search: If the authoring tool provides an editing-view of text-based content, then the editing-view enables text search, such that all of the following are true: (Level AA)(a)
ZjQcmQRYFpfptBannerStart
This Message Is From an Untrusted Sender
You have not previously corresponded with this sender.
ZjQcmQRYFpfptBannerEnd
Hello,

A question regarding ATAG A.3.5.1<https://www.w3.org/TR/ATAG20#sc_a351>, which reads:
A.3.5.1 Text Search:

If the authoring tool provides an editing-view<https://www.w3.org/TR/ATAG20/#def-Editing-View> of text-based content, then the editing-view<https://www.w3.org/TR/ATAG20/#def-Editing-View> enables text search, such that all of the following are true: (Level AA)

  *   (a) All Editable Text: Any text content that is editable by the editing-view is searchable (including alternative content<https://www.w3.org/TR/ATAG20/#def-Alternative-Content>); and
  *   (b) Match: Matching results can be presented to authors and given focus; and
  *   (c) No Match: Authors are informed when no results are found; and
  *   (d) Two-way: The search can be made forwards or backwards.
I am currently reporting on a tool that does not provide text search itself. However, the tool is browser-based and the built-in browser search satisfies (in this case): a, b, c and d. Users are able to do the kind of searching that this SC descrbies, but it’s not because something the tool has built-in.

Am I correct in assuming this tool can be claimed to meet A.3.5.1 by “enabling” text search (as it works in browsers with built-in search and does not actively _break_ that built-in search experience (eg by conditionally hiding editable content etc)).


Best,

Hidde de Vries