Follow up from #4453

Currently, documentation for <b-table> really only discusses and provides examples for the row-selected event:
https://bootstrap-vue.org/docs/components/table/#row-select-support

The only places the row-clicked event is mentioned are:
https://bootstrap-vue.org/docs/components/table/#data-row-accessibility
https://bootstrap-vue.org/docs/components/table/#comp-re

It would be nice to have a "kitchen sink" page with all the components displayed, would make discovering the components easier instead of having to click each link in the navigation one by one.

When applying FormField label styles (see #3998), for examplesize, the prop is being leaked to the DOM while it shouldn't.

Originally posted by @ericsoderberghp in grommet/grommet#3998

Not part of this review per-se, but we shouldn't be leaking `size` into the DOM.

Opening this issue in case anyone wants to help. Recently, we've configured Storybook to import files from __examples__ folders inside Reakit component folders. This is how we're doing it:

https://github.com/reakit/reakit/blob/0b70f435673db13b75f82d69ac2760b485879674/.storybook/preview.js#L7-L22

Thos

The "Who to follow" page seems a little unruly. I think it might be better to change it to a Twitter list maintained by the A11y Project Twitter account or separate Twitter lists for people, companies, and Meetups.

This would have the added benefit of allowing users to follow/unfollow the whole list at

🐛 Bug report

Description

When I run a scan against a very long URL, word wrap breaks in the results.

Environment

• webhint version: 1.2.1
• Browser version: Edge Beta (80)

When using pa11y programatically (I needed to hook into some webpack-dev-server lifecycle hooks) it wasn't clear from the README how to add the CLI reporter.

Thankfully it was consistent with the HTML reporter, which was documented, however it'd have been easier if there was a comment under the reporters section linking to other reporters.

Example

I also see the issue with:

• <label>foo<meter /></label>
• <label>foo<output /></label>
• <label>foo<progress /></label>

Workaround
Add the following to your .eslintrc.js

module.exports = { rules:
    'jsx-a11y/label-has-associated-cont

Hi,

as far as I understand the LICENSE the user needs to add a license disclaimer to every file when serving the files from a server.

Would it the useful to do this in this repository or am I wrong?

Evaluate JSDoc based tools to possibly move the API docs into the source files directly. This would make docs/api/**/*.md irrelevant.

• http://documentation.js.org/
• https://www.npmjs.com/package/doctrine
• https://www.npmjs.com/package/docchi

I understand that a test can be run manually, but I was wondering whether a test could be ran daily or weekly for example.

We started this project not quite long after Next.js became public and we haven't really touched the README 😅

We've just been improving the code section and making it a lot better. I guess it's time to give the README a new structure, basically to pass the right message to new users.

Let's do this! 🚀

Problem

In macOS Safari, clicking links below the fold inside the FocusLock component causes focus to jump to the first link instead of going the destination of the link.

Here's a codesandbox that reproduces the issue: https://codesandbox.io/s/responsive-navigation-safari-bug-6hvj

Is your feature request related to a problem? Please describe.
No tests currently written for components

Describe the solution you'd like
Write tests in jest :)

This current codebase is setup to work with Jest and @vue/test-utils out of the box.

Issue

The pattern at this URL:
https://a11y-style-guide.com/style-guide/section-navigation.html#kssref-navigation-navigation-dropdown

• Puts the menuitem role on the <li>,
• Leaves the <a> with its native role,
• As a result of the previous two items, breaks from the APG ARIA menu pattern,

The guideline code shown at the top of this error message has a predictable pattern. We could grab the G17 part of it and use that to create a link to give the reader of the report more details about the guideline.

Here is a quick sketc

Something must have changed in Chrome because the CSS asterisk is no longer positioned appropriately.

checking firefox, it still is positioned as intended.

Further investigation necessary.

Where does the advice "For logos that are text-based, use <em> element." originate from and what is the purpose of it? Screenreaders don't generally provide support for

I followed the documentation for setting a viewport in the config file, but when I do so I get the following error when pa11y tries to run:

Error: page.setRequestInterception is not a function

Expectation
When setting a viewport in the pa11y config file, the test execution runs as expected against the given viewport.

Actual
I get the following error when setting a viewport in