Yusuke Hirao

Results 110 issues of Yusuke Hirao

Wrong color evaluation when used custom properties I tested "https://yusukehirao.github.io/" through the online tool ( https://visi.dev/ ). Results: > Contrast > The color contrast ratio of foreground `rgb(51, 51, 51)`...

bug

## Motivation The new option `checkingRequiredOwnedElements` added to `wai-aria` rule in v3. The option checks the conformance of whether a role owns the required descendant role. But in an actual...

Features: Proposal
Core API
v5.0

- Fix the **transparent** content model computation. - Make it possible to specify the attribute selector to the not-allowed descendants. (Ex: The `a` element must not include the element that...

rule
v3.0

## Sample Code ### Incorrect ```html Label Label ``` ### Correct ```html Label Label ``` ## Ruleset Idea ```json { "selector": "label:not([for]:has(@formcontrol-element))", "rules": { "disallowed-element": true } } ```

rule

![markuplint logo](https://cdn.rawgit.com/YusukeHirao/markuplint/HEAD/media/logo-v.svg) The current logo was made just quick by me. I want a designer to improve it properly. Want: - Accessible. - Compatible with dark mode. - Usable for...

pull request wanted

Currently, Both `` and `` are decided the flag `isCustomElement` in JSX parser and Vue parser and more. Add the new flag `isSpecificComponent`, then resolve mainly the problem that it...

core
plugin
v3.0

This is an idea that selects an element that matches its spec. The selector imitates the `aria/` selector of Puppeteer to start with `spec/`. ```js element.matches("spec/[disabled]"); ``` A selector follows...

Features: Proposal
Core API
v3.x

In React, Svelte, and more, It cannot evaluate custom components as HTML elements. The `pretenders` option resolves that. It evaluates components as HTML elements on each rule if you specify...

proposal features
core
v3.0

- [x] Add `overrides` option - [x] Add `excludeFiles` option - [ ] Support `.markuplintignore` file

required features
core
pull request wanted