Replies: 1 comment
-
I took a quick look, so I am not positive, but I think this may be a bug. Unless I just overlooked something, since I just quickly tried to throw a reproduction together, it looks like the functions are getting removed before being passed into axe. I can't remember if parameters are one of the objects that get serialized, but if so then that is probably breaking the config. My quickly thrown together code did cause the accessibility panel to display something from my config, but it had no label and just said there was an error. I am busy with something at work, but if I get some time then I will try to confirm what is happening. At the moment I am thinking the channels serializer may be stripping the object functions, if someone wants to take a look. |
Beta Was this translation helpful? Give feedback.
-
Summary
I'm using Storybook with the @storybook/addon-a11y addon to ensure my components meet accessibility standards. I've enabled the object-alt rule and added a custom check for it, but it doesn't seem to fail even when the custom check returns false.
Here is my preview.ts file:
Problem:
Despite the evaluate function returning false, the object-alt rule does not show as failed in my Storybook page. I've added console.log statements to verify that the evaluate function is being called, and it is.
Steps Taken:
Verified that the object-alt rule is enabled.
Added custom evaluation logic that returns false.
3. Checked the browser console to ensure the evaluate function is being executed.
Question:
Why is the object-alt rule not showing as failed in my Storybook page, and how can I ensure it correctly fails when the custom check returns false?
Any help or insights would be greatly appreciated!
Additional information
No response
Create a reproduction
No response
Beta Was this translation helpful? Give feedback.
All reactions