by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 31 2019 20:13
    jkodu synchronize #1339
  • Jan 31 2019 20:13

    jkodu on core-preload-cssom-updates

    chore: update code owners with … feat(rule): Require unique aria… fix(i18n): Fix Japanese transla… and 6 more (compare)

  • Jan 31 2019 20:08
    jkodu synchronize #1339
  • Jan 31 2019 20:08

    jkodu on core-preload-cssom-updates

    test: update preload related te… (compare)

  • Jan 31 2019 18:54
    stephenmathieson commented #1343
  • Jan 31 2019 18:54
    stephenmathieson synchronize #1343
  • Jan 31 2019 18:54

    stephenmathieson on remove-grunt-lint

    chore: rerun prettier (#1340) Merge branch 'develop' into rem… (compare)

  • Jan 31 2019 16:53
    jkodu edited #1339
  • Jan 31 2019 16:52
    jkodu edited #1339
  • Jan 31 2019 16:50
    jkodu edited #1339
  • Jan 31 2019 16:49
    jkodu synchronize #1339
  • Jan 31 2019 16:49

    jkodu on core-preload-cssom-updates

    fix: update preload cssom to ca… (compare)

  • Jan 31 2019 16:20
    WilcoFiers closed #1342
  • Jan 31 2019 15:27
    tysonwolker starred dequelabs/axe-core
  • Jan 31 2019 10:27

    jkodu on chore-prettier

    (compare)

  • Jan 31 2019 10:27

    jkodu on develop

    chore: rerun prettier (#1340) (compare)

  • Jan 31 2019 10:27
    jkodu closed #1340
  • Jan 31 2019 09:27
    undeadinu starred dequelabs/axe-core
  • Jan 30 2019 19:05
    AdnoC review_requested #1344
  • Jan 30 2019 19:05
    AdnoC opened #1344
Steven Lambert
@straker
@Arrow66 hello Arjun, i'm not familiar with that app but you could direct your question to helpdesk@deque.com for further help
Anu
@anuvenkatesh1
Hello, is it possible to integrate axe-core rule sets into sonarqube?
Aaron Sanders
@SandersAaronD
@straker I opened an issue for the documentation issue I found a bit ago: dequelabs/axe-core#2449
Arjun Biju
@Arrow66
@straker i asked them they said they were using different toolset
getting this error
Invalid ARIA attribute value: aria-controls="76120b61-3eb9-44df-b428-0d35ce1d5372"
using atd
*antd
Steven Lambert
@straker
i believe ids can't start with a number and must start with a letter
mistercoffee66
@mistercoffee66

Hello folks, I have what I think is a false-positive using the Axe Chrome extension. I have markup generated by the Slick js carousel. The segment in question rendering in the DOM like this

"<div data-index=""-2"" tabindex=""-1"" class=""slick-slide slick-cloned"" aria-hidden=""true"" style=""width: 365px;"">"

Axe reports this:

Focusable content should have tabindex='-1' or be removed from the DOM",Ensures aria-hidden elements do not contain focusable elements,serious,aria-hidden-focus,"[""div[data-index=\""-\\32 \""]""]","<div data-index=""-2"" tabindex=""-1"" class=""slick-slide slick-cloned"" aria-hidden=""true"" style=""width: 365px;"">"

Can anyone confirm that this is an error in the Axe extension? Thanks.

(The double quotes in my first snippet above happened when pasting into this chat)
allie
@afalco2_gitlab

hi new axe user here, trying to get the experimental rules to run against some test html without much luck. i've tried enabling (one of) them like so

axe.configure({
    rules: [{id: 'p-as-heading', enabled: true}],
    disableOtherRules: true
});

and am using the test html

            '<p style="font-size:30px;font-style: italic;">Not a heading</p>' +
            '<div id="working">' +
              '<label for="has-label">Label for this text field.</label>' +
              '<input type="text" id="has-label">' +
            '</div>' +
            '<div id="broken">' +
              '<p>Not a label</p><input type="text" id="no-label">' +
            '</div>'

i tried dumping the results in a callback but i dont even see any mention of the 'p-as-heading' rule in the violations/passed/inapplicable/incomplete arrays, even though it shows up in the getRules() metadata. fwiw i can get the 'label' rule to fail against this html when i swap out 'p-as-heading' for 'label'

axe-core version 4.0.1 installed

Steven Lambert
@straker
@mistercoffee66 are you able to provide an example page with the failure? I ran axe on the slick slide page (https://kenwheeler.github.io/slick/) and it didn't log any aria-focus-hidden failure on any of the .slick-slide divs, only the buttons used for navigation underneath the slides
Steven Lambert
@straker
@afalco2_gitlab turning on experimental rules is actually a bit of a "hidden" feature. You'll have to pass an undocumented tagExclude: [] property to the configure call as we auto-exclude experimental rules by default
axe.configure({
    rules: [{id: 'p-as-heading', enabled: true}],
    disableOtherRules: true,
    tagExclude: []
});
mistercoffee66
@mistercoffee66
@straker The site in question is under NDA, will see if I can recreate and post a link. Thanks!
mistercoffee66
@mistercoffee66
@straker Here's a codepen project in which a duplicated the error: https://codepen.io/mistercoffee/project/editor/DNvrjb#
Steven Lambert
@straker
@mistercoffee66 Ok, looking at the code it's actually correct. The true issue is in the relatedNodes property of the error which points to an anchor element <a class="app-sbr__spotlight-section__story-link" href="https://www.google.com">Click me</a> that is a child of that div
that is focusable even though the parent div is hidden
mistercoffee66
@mistercoffee66
@straker I see it now, I'm grateful for your help. Thank you sir!
Kristina Hager
@khager1_gitlab
hi there, i noticed that axe-core 4.0 is out. however, i don't think the chrome extension has been updated with this yet. Do you have any idea when this might be done? (also not sure what version axe monitor is using..)
Steven Lambert
@straker
@khager1_gitlab we're working on updating all the different extensions and products to use 4.0. We are planning on releasing those soon
Kristina Hager
@khager1_gitlab
thanks!
Kristina Hager
@khager1_gitlab
@straker - is 'soon' approximately days, weeks or months?
Steven Lambert
@straker
We just finsihed up the development, so I'd say within a week(ish)
Kristina Hager
@khager1_gitlab
great thanks!
Cara Clarke
@caraclarke

Hi, I am running into a strange issue with my axe core unit tests and hoping someone can help. When I switch some values in my component from

id = uuid.v4().slice(0, 8);
buttonId = uuid.v4().slice(0, 8);

to

 id = uuid.v4().slice(0, 8);
  panelId = `panel-${this.id}`;
  buttonId = `panelTriggerButton-${this.id}`;

my unit tests start failing with this error "ARIA attributes must conform to valid values (aria-valid-attr-value)", but in the browser everything seems fine. I am using these values for ids for aria-labelledby and aria-owns. Any suggestions?

Steven Lambert
@straker
my guess is that maybe those ids aren't being referenced/added to the DOM correctly? maybe another componen is still referenceing an id as uuid.v4().slice(0,8) instead of the new format?
Cara Clarke
@caraclarke
It was a prop name issue that I didn't notice in the browser because the id did get rendered, just on the wrong element
Kristina Hager
@khager1_gitlab
@straker - is axe-webdriverjs going to get a 4.0 update? Here it's at 3.4.. and we know from experience that 3.4 misses things that even 3.5 catches. I'm assuming 4.0 will catch more as well:https://github.com/dequelabs/axe-webdriverjs/blob/develop/package.json#L93
Steven Lambert
@straker
@khager1_gitlab it should be getting a 4.0 update in the next week(ish)
bala krishnan
@balakrishnankgm_twitter
Hi, I am using axe selenium 3.0 as maven dependency. While I am trying to find the violations inline spacing violations is not captured. Is there anything I need to use updated version?
Adam Cutler
@AdnoC
@balakrishnankgm_twitter You can use whatever version of axe-core you want, just give a URL to the file to the AXE.Builder class
Sai Avinash Duddupudi
@saiavinashiitr
Hi all, I am currently using the following snippet in my code which gives accessibility issues for the entire webpage.
I want to know if there is a way where I can run axe only on a specific div/section in a HTML page. For example, In the following image, I want to run axe on elements withclass="parent_class" and its child with class="child_class"
axe.run(document, {
runOnly: {
    type: "tag",
    values: ["wcag2a", "wcag2aa"]
},
"rules": {
    "skip-link": { enabled: false }
}
}
image.png
Sai Avinash Duddupudi
@saiavinashiitr
axe version used:- 3.5.5
Steven Lambert
@straker
@saiavinashiitr the first argument for axe.run is the element/css selector to run on axe.run('.parent_class')
skamineni
@skamineni
has anybody validated the blue ring or css style after keyboard focus ?
mistercoffee66
@mistercoffee66
Screen Shot 2020-09-14 at 3.56.25 PM.png
Question about Axe and how WCAG defines a "toggle." The following code snippet is from a carousel, specifically the buttons to advance to a specific "page" of slides (see screenshot above)
Axe Chrome extension is reporting that the buttons should have the aria-pressed attr, but that is only for toggles as far as I know. Are these considered toggles? I think of toggles as binary, turning something on or off.
<li class="active"><button>1</button></li>
<li><button>2</button></li>
<li><button>3</button></li>
mistercoffee66
@mistercoffee66
Steven Lambert
@straker
@mistercoffee66 which rule exactly is failing that is reporting needing aria-pressed? usually that happens only when certain roles are used that require certain aria attributes
mistercoffee66
@mistercoffee66
@straker 4.1.2 (name, role, value)
mistercoffee66
@mistercoffee66
@straker If I am understanding you correctly, the use case I posted shouldn't require aria-pressed, correct? At least based on the code I provided. There's nothing in the containing code with an assigned role. See this other screenshot for the DOM hierarchy:
Screen Shot 2020-09-15 at 2.50.21 PM.png
Steven Lambert
@straker
@mistercoffee66 i mean which axe rule is the giving the report? is it aria-required-attr?
Steven Lambert
@straker
better yet, is the page a public URL that I could take a look at?
mistercoffee66
@mistercoffee66
@straker Yes, I will DM you. Thank you!
Kranthi93
@Kranthi93
What are the reasons on why we should not add axe-core tests to check a11y violations to the pipeline? I read they are time consuming ? the difference it is gonna add to the time for running tests is significant?