A11y test error because links have no underlines |
|||
Issue descriptionSee example test failure here: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8932942268393419584/+/steps/browser_tests__with_patch_/0/stdout The error states that "Links must be distinguished from surrounding text in a way that does not rely on color". Context: "https://dequeuniversity.com/rules/axe/3.0/link-in-text-block?application=axeAPI", Shiba, can you give us some guidance on this? I'm landing an exception to unblock this test right now, but we should figure out if this is the right thing to do.
,
Oct 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/4cf4ff7aa5b049728149b2a55e6a021301fa6657 commit 4cf4ff7aa5b049728149b2a55e6a021301fa6657 Author: Jeremy Klein <jlklein@google.com> Date: Fri Oct 12 01:29:37 2018 Fix a11y test error for multidevice settings. Adding a temporary exception for one link-in-text-block error. This error comes from the fact that we (intentionally) removed the underline from the learn more links in our settings. I've filed crbug.com/894602 to work with UX on a new strategy and remove this exception. Bug: 894602 Change-Id: I0da37adfee02699415a011939dbfc6d4e1d93f34 Reviewed-on: https://chromium-review.googlesource.com/c/1278131 Commit-Queue: Jeremy Klein <jlklein@chromium.org> Reviewed-by: Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#599059} [modify] https://crrev.com/4cf4ff7aa5b049728149b2a55e6a021301fa6657/chrome/test/data/webui/settings/a11y/multidevice_features_a11y_test.js
,
Oct 31
I thought removing the underlines was WAD. Elizabeth could you confirm?
,
Oct 31
Yeah, it *is* working as shown in the mocks and spec (no underlines). However, the lack of underlines for a link is going against accessibility guidelines and is causing this test to fail. The exact error is: "Links must be distinguished from surrounding text in a way that does not rely on color".
,
Jan 11
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this. |
|||
►
Sign in to add a comment |
|||
Comment 1 by jlklein@chromium.org
, Oct 11