[code-inclusion] Remove "whitelisted" from ax_object.cc

As above - there should be no behaviour change.

Bug: 842296
No-try: true
Change-Id: If5e0dba3217bb3cee88b4994e5c3ac3a00e207a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2260948Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#781563}

third_party/blink/renderer/modules/accessibility/ax_object.cc

@@ -4110,9 +4110,9 @@ bool AXObject::NameFromContents(bool recursive) const {
         //   would cause them to be double-announced.
         // 2.Containers with aria-activedescendant, where the focus is being
         //   forwarded somewhere else.
-        // TODO(accessibility) Scrollables are currently whitelisted here in
-        // order to keep the current behavior. In the future, this can be
-        // removed because this code will be handled in IsFocusable(), once
+        // TODO(accessibility) Scrollables are currently allowed here in order
+        // to keep the current behavior. In the future, this can be removed
+        // because this code will be handled in IsFocusable(), once
         // KeyboardFocusableScrollersEnabled is permanently enabled.
         // Note: this uses the same scrollable check that element.cc uses.
         bool is_focusable_scrollable =