ATAG A.3.5.1 and browser built-in search

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