npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

vue-visually-hidden

v2.0.0-alpha.1

Published

Vue.js visually hidden component

Downloads

19

Readme

vue-visually-hidden

npm

Vue.js visually hidden component (Vue 3 Only)

What is visually-hidden component ?

In the case of visual content, users using assistive technologies (e.g. screen readers) may not always know what the content means.

In most cases, accessible content can be provided by semantic markup, but there is currently no markup that can provide content that is not visually visible but can be read out loud.

For example, when a button is displayed with only pictograms, the description of the button may be visually discernible, but the screen reader may not know what it means.

<button type="submit">
  <span>
    📧
  </span>
</button>

In such cases, <VisuallyHidden> is a good choice.

<button type="submit">
  <span aria-hidden="true">
    📧
  </span>
  <VisuallyHidden>
    Send email
  </VisuallyHidden>
</button>

Use aria-hidden="true" to prevent screen readers from emoji.

It used to be used in Bootstrap in the form of sr-only.

Reference

WebAIM: CSS in Action - Invisible Content Just for Screen Reader Users

Demo

https://vue-visually-hidden.vercel.app/

Installation

npm install -D vue-visually-hidden
yarn add -D vue-visually-hidden

Usage

<template>
  <div>
    <VisuallyHidden>
      Visually Hidden Text
    </VisuallyHidden>
    <VisuallyHidden :isFocusable="true">
      <a href="http://example.com">example</a>
    </VisuallyHidden>
  </div>
</template>

<script setup>
  import { VisuallyHidden } from 'vue-visually-hidden'
</script>

style setting (vue-cli)

import 'vue-visually-hidden/dist/style.css'

style setting (vite)

import 'vue-visually-hidden/style'

isFocusable

prop | type | default ----------- | --------- | --------- isFocusable | Boolean | false

Inspired by Bootstrap visually-hidden helper

.visually-hidden-focusable can be show by any child element of the container receives focus.

<template>
  <VisuallyHidden :isFocusable="true">
    <a href="http://example.com">example</a>
  </VisuallyHidden>
</template>

This can be used primarily for a feature called skip link. A skip link is link that allow keyboard users to quickly access the main content, and the links are visible upon focus.

Reference

Resolve Setting

If you get the error Invalid VNode type: Symbol(Fragment) (symbol), try setting resolve in the configuration file as follows.

See: https://github.com/vuejs/vue-next/issues/2064

vue.config.js

const path = require('path')

module.exports = {
  configureWebpack: {
    resolve: {
      symlinks: false,
      alias: {
        vue: path.resolve('./node_modules/vue')
      }
    }
  }
}

vite.config.js

import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'

export default defineConfig({
  plugins: [vue()],
  resolve: {
    dedupe: ['vue']
  }
})